Coding agent skills - Momentic

Documentation Index

Fetch the complete documentation index at: /docs/llms.txt

Use this file to discover all available pages before exploring further.

The Momentic skills are SKILL.md files that teach a coding agent how to work with Momentic: the test file format, the MCP tools, the CLI, failure triage, and Mo. Each Momentic CLI ships the shared skills plus the skills for its own product. Install them once per repository and commit the files. Skills are text the agent reads. The MCP server is the process the agent calls to act on a live browser or device when working on repository tests. Install both for test authoring and maintenance. Mo sessions use the qa CLI and mo-qa skill without an MCP installation. See Building with AI for how they compare.

Install

Run the command for each CLI you use. Each command adds its own skills and leaves the skills installed by other CLIs in place.

momentic momentic-mobile mo

npx momentic skills
    ```

npx momentic-mobile skills ```

qa skills
    ```

The command asks which coding agents you use, preselects the ones it detects in
the repository, and writes the skills into each agent’s directory:

| Agent | Skills directory | Always-on pointer |
| --- | --- | --- |
| Claude Code | `.claude/skills` | `CLAUDE.md` |
| Cursor | `.cursor/skills` | `.cursor/rules/momentic-skills.mdc` |
| Codex, Devin, Jules, and other AGENTS.md tools | `.agents/skills` | `AGENTS.md` |
| VS Code and GitHub Copilot | `.github/skills` | `.github/copilot-instructions.md` |
| OpenCode | `.opencode/skills` | `AGENTS.md` |

The pointer is a short block inside the agent’s instructions file. It lists the
installed skills and tells the agent to read the matching `SKILL.md` before it
touches Momentic tests. The block sits between `<!-- MOMENTIC SKILLS START -->`
and `<!-- MOMENTIC SKILLS END -->` markers; the installer rewrites only that
block, so your own instructions stay as they are.

### Skip the prompts

Pass `--target` to choose agents without a prompt, or `--yes` to install for the
agents detected in the repository:

npx momentic skills --target claude-code cursor npx momentic skills --yes ```

Both flags work in CI and in agent shells.

Installed skills

Every CLI installs the shared skills:

Each CLI adds the skill for its product:

Use the skills

Some agents load installed skills on their own. Others load a skill only when you name it in the prompt. Invoke skills with a slash prefix, as the examples below show. For agents without slash commands, ask for the skill by name.

Authorship

Use momentic-test to create or extend Momentic tests:

/momentic-test write a test for the checkout flow
    ```

Use `momentic-mobile-test` for Android and iOS. Naming the skill keeps the agent
on Momentic’s test format and MCP tools instead of writing framework-specific
code.

### Maintenance

Use `momentic-maintain` to understand failures on a branch or main, review and
challenge saved classifications, deflake quarantined or recovered tests, reduce
retries, and repair stale test steps while preserving the intended behavior:

/momentic-maintain investigate and repair run ```

Use momentic-triage-quarantined-tests to work through the quarantine backlog and produce a PR or report for the tests it repairs.

Request visual evidence

Web and mobile MCP tools return screenshots from live sessions and saved step results. Ask the agent to display them in the conversation when you want to see the evidence it used:

/momentic-maintain show the before and after screenshots for the first failing step in run <run-id>, then explain where behavior diverged
    ```

The web MCP can also record a live browser session. Ask the agent to enable
video when it starts the reproduction and return the video output path after it
terminates the session:

/momentic-maintain reproduce run in a web session with video enabled, then return the screenshots and video output path ```

Mobile MCP sessions return screenshots and have no live session video option. The agent can still inspect the video attached to a completed mobile run when that artifact exists.

Spec-driven development

In the simplified format, Momentic tests read as product specs. Invoke momentic-spec when implementing a feature so the agent creates or updates the smallest set of affected Momentic tests before changing product code:

/momentic-spec add a confirmation message after a file is attached
    ```

To make this the default behavior for your repository, also add a spec-driven
section to your `AGENTS.md` (or `.cursor/rules`, etc.):

Momentic spec-driven development

Use the momentic-spec skill before implementing user-visible product changes. It captures the intended behavior in the smallest affected set of Momentic tests, then validates the implementation at durable UI checkpoints. Follow the skill's steps for test data, disabled specifications, and verification. ```

Mo

Use mo-qa to start and control Mo sessions from a coding agent. If the qa CLI is installed, qa skills writes mo-qa and the shared skills into the directory of each agent you pick:

qa skills
    ```

Without the CLI, install the skill on its own:

npx skills add https://github.com/momentic-ai/skills --skill mo-qa ```

Claude Code and Cursor can also install the momentic plugin from the Momentic skills repository; it contains the same skills.

/mo-qa bug bash my new feature on <branch>
    ```

The skill installs and authenticates the CLI, asks you for the parts of the
brief you left out, starts the session, and follows it. It does not invent
scope, credentials, or acceptance criteria. See [write a good brief](/content/docs/mo/brief/index.html)
and [use the CLI](/content/docs/mo/cli/index.html).

## Keep skills current

The skills ship inside the CLI package, so a CLI upgrade can carry new skill
content. The first time you run `momentic run`, `momentic app`,
`momentic-mobile run`, or `qa start` in a terminal after an upgrade with newer
skills, the CLI asks once whether to update the installed files. Answer `y` to rewrite them for the agents you chose before. Answer `n` and it
does not ask again for that skill version. Each CLI tracks its own skills, so an
update from `momentic` leaves the files `qa` installed as they are. The prompt appears only in an interactive terminal. It does not run in CI, in
non-TTY shells, or when `MOMENTIC_SKIP_SKILLS_PROMPT` is set. To update without
the prompt, run the install command again:

npx momentic skills --yes ```

Install state lives in ~/.momentic/skills.json. Delete the file to see the first-run prompt again. Each installed SKILL.md ends with a footer such as Generated for momentic 3.53.0 (skills 1788291203). Read it to see which CLI version wrote the file, and compare it with npx momentic --version in a code review to spot a stale skill.