> ## Documentation Index
> Fetch the complete documentation index at: https://docs.egma.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Skills

Egma skills give your coding agent instructions for working in your repository. The agent reads your prompts, tools, and startup code, then uses the [CLI](/tools/cli) to make changes in Egma.

## Install the skills

Run these commands in your voice agent's repository. Select your coding agent when the installer asks where to install them.

```bash theme={null}
npx --yes skills add egma-ai/egma --skill integrate-egma
npx --yes skills add egma-ai/egma --skill write-egma-tests
```

The installed skill names are `integrate-egma` and `write-egma-tests`.

You also need Node.js 22 or newer and the Egma CLI:

```bash theme={null}
npm install --global egma-cli
egma login
```

Approve the login in your browser and select the project to use. For your own Egma instance, use `egma login --url` with its URL. See [CLI setup](/tools/cli#sign-in-and-initialize).

## Connect your agent

Ask your coding agent to use `integrate-egma`:

```text theme={null}
Use integrate-egma to set up simulation testing for the voice agent in this
repository. Read its startup code, prompts, and tools. Connect it to my Egma
project and show me the agent and connection to use for a test run.
```

Egma supports [LiveKit](/guides/livekit) and [Retell](/guides/retell). Have the provider credentials available in your terminal or deployment secret store. Keep secret values out of prompts and test files.

For LiveKit, follow the [Python SDK](/tools/livekit-python-sdk) or [JavaScript SDK](/tools/livekit-javascript-sdk) instructions. Every simulation needs `await simulation(agent, ctx, session)` in the worker, including tests without mocks. Set the worker's `EGMA_URL` and project-scoped `EGMA_API_KEY`. For production monitoring, also call `monitor(ctx)` at the start of the job entrypoint and deploy the worker before checking for conversations in Egma.

## Write tests from your code

After the repository is connected, ask your coding agent to use `write-egma-tests`:

```text theme={null}
Use write-egma-tests to create tests for this agent's appointment booking flow.
Read the prompt, tools, and startup data first. Cover a successful booking,
no available appointments, and a booking tool error. Use mock responses for
tools that write to our backend. Push the tests to Egma and summarize them.
```

The skill finds or creates a test suite, selects personas from your project, and writes Markdown tests under `egma/tests/`. Each test describes one situation and the behaviors you expect. It can also include tool responses and the data your agent needs at startup.

Review the scenarios, expected behaviors, tool names, and mock responses before running them. A tool that has no mock uses its real implementation. See [Mock tool responses](/guides/mock-tool-responses) for the setup and failure behavior.

## Run the tests

Ask your coding agent to run the suite against the agent and connection you selected:

```text theme={null}
Start an Egma run for the appointment booking suite. Use the agent and
connection configured for this repository. Open the result and explain any
failed expected behaviors using the transcript and tool calls.
```

Run creation returns a results URL. Grading continues after the CLI command finishes. Use [Start and follow a run](/guides/start-and-follow-a-run) to inspect its progress and result.

## Update the skills

Update your installed skills:

```bash theme={null}
npx skills update
```

Keep your repository's skill lock file with the rest of your development setup so your team can see which source it uses.