Skip to main content
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 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.
The installed skill names are integrate-egma and write-egma-tests. You also need Node.js 22 or newer and the Egma CLI:
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.

​
Connect your agent

Ask your coding agent to use integrate-egma:
Egma supports LiveKit and 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 or 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:
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 for the setup and failure behavior.

​
Run the tests

Ask your coding agent to run the suite against the agent and connection you selected:
Run creation returns a results URL. Grading continues after the CLI command finishes. Use Start and follow a run to inspect its progress and result.

​
Update the skills

Update your installed skills:
Keep your repository’s skill lock file with the rest of your development setup so your team can see which source it uses.