> ## Documentation Index > Fetch the complete documentation index at: https://docs.revyl.com/llms.txt > Use this file to discover all available pages before exploring further. # Agent skills > Install skills that teach your coding agent to run the dev loop, read Atlas, write tests, and set up auth bypass. Skills are embedded playbooks that teach your AI coding agent how to use Revyl effectively. The first-class public skills cover the customer workflows agents run most often: dev loops, visual Atlas understanding, test creation, and test-only auth bypass. Optional by-name skills cover narrower implementation jobs. Prompt for your coding agent: ```text Install the Revyl agent skills for this coding agent. Read https://docs.revyl.com/agents/skills.md and follow it. It's the current Revyl guide for this, so prefer it over anything you remember about Revyl. Run `revyl skill install --yes` with this agent's flag (`--cursor`, `--claude`, or `--codex`) to install the recommended CLI skills in this project. Skip the `revyl-mcp-*` skills unless this agent already uses the Revyl MCP server. You're done when you've told me which skills you installed and where. Ask me before anything that needs my login or approval. ``` ## Choose the right skill family | Setup | Skill behavior | |-------|----------------| | Revyl Cursor Marketplace plugin | Installs the CLI and signs you in. Bundles `revyl-cloud-agent`, `revyl-cli-dev-loop`, `revyl-ci-sync`, `revyl-proof-ci`, `revyl-proof-automation`, and `revyl-cli-auth-bypass`; do not install a second copy | | CLI-backed MCP with the focused `dev` profile | Install `revyl-mcp-dev-loop` for the selected client | | CLI-only workflows | Select the `revyl-cli-*` skills matching your workflow | The `revyl-mcp-*` family expects MCP tools. The `revyl-cli-*` family runs terminal commands as an explicit fallback. Do not run both families against the same active dev loop. ## Install CLI skills Interactive `revyl init` and `revyl skill install` open a skill picker with the recommended skills preselected. Press Enter to install them, or clear the selection to skip installation. Scripts, `--yes`, and `--json` install the recommended skills without a picker: ```bash revyl skill list revyl skill list --all revyl skill install ``` For client-specific installation, `npx skills add`, optional MCP, shared package locations, global scope, and `--copy` compatibility, follow [MCP Setup](/agents/mcp#skill-selection-storage-and-updates). ### Install by intent Select only the workflows you want the agent to use: | Intent | Skill | Command | |--------|-------|---------| | Run a Revyl dev loop, interact with the device, and verify app behavior | `revyl-cli-dev-loop` | `revyl skill install --name revyl-cli-dev-loop` | | Understand an app by traversing its Atlas graph, inspecting media, and reviewing originating reports | `revyl-cli-atlas` | `revyl skill install --name revyl-cli-atlas` | | Author or refine stable Revyl YAML tests, then validate, push, run, and inspect reports | `revyl-cli-create` | `revyl skill install --name revyl-cli-create` | | Set up test-only auth bypass across a mobile app stack | `revyl-cli-auth-bypass` | `revyl skill install --name revyl-cli-auth-bypass` | Repeat `--name` to select several skills. Without `--name`, noninteractive runs, `--yes`, and `--json` install the recommended skills in this table and name them on stderr. Installation copies the complete package, including agent metadata and optional references, scripts, and assets. Auth-bypass loads only the reference matching the detected stack. Auth-bypass and Atlas review require an explicit user request; ordinary workflows permit implicit invocation. ### Native agent behavior The shipped skills direct agents to use the browser, image, and MCP tools actually exposed by their client. Installation does not modify `AGENTS.md` or inject Cursor rules. For Atlas, receiving a screenshot URL or local path is not visual verification; the agent must open and read the image. Without native video ingestion, the Atlas skill directs agents to extract and inspect bounded clip frames with `ffmpeg`. It also traces misunderstood evidence into the exact originating report. For device workflows agents can verify through `revyl device screenshot`, `revyl device report`, or `revyl test report`. ### Refresh skills after CLI update `revyl upgrade` updates the binary and leaves skill packages unchanged. Inspect installed project and global skills, then update the scope you want: ```bash revyl skill list --installed --json revyl skill update revyl skill update --global ``` `skill update` refreshes only already-installed, unmodified Revyl-managed packages from the current CLI. Local edits and unmanaged packages are preserved and reported; no new skills are installed. Updates default to the project; `--global` selects only the home-directory scope. Use installation's `--force` only when you deliberately want to replace a selected package and discard its local edits, not as a routine refresh command. If you customize installed skills, for example by merging several into one package to save context, CLI updates leave them alone; there is no automatic skill update to disable. `skill update` never changes an edited package. It reports an edited Revyl package as `preserved` and exits non-zero, so pass only the skill names you want refreshed. See [Updating the CLI](/install#updating-the-cli) for the post-upgrade reminder and older CLI versions. --- ## First-Class Skills Use these names directly in prompts when you want the agent to follow the right workflow. | Skill | Description | |-------|-------------| | `revyl-cli-dev-loop` | Use when the agent should run a generic Revyl CLI dev loop: initialize or attach, start the right hot-reload or rebuild loop for the app stack, keep the session running, interact with the device, and verify with screenshots or reports. | | `revyl-cli-atlas` | Use when the agent should explore an app bottom-up from graph anchors, inspect screenshots or extracted clip frames, and reconcile misunderstood evidence through its originating report. | | `revyl-cli-create` | Use when the agent should author or refine a stable Revyl YAML test from evidence, keep steps intent-level, use sparse user-visible validations, then validate YAML, push, run, and iterate from reports. | | `revyl-cli-auth-bypass` | Use when the user explicitly requests test-only auth bypass across a mobile app stack, with a handler for the detected stack, launch-var gates, and device verification of valid and rejected links. | ### Optional skills Use `revyl skill list --all` to include narrower workflows and compatibility skills. These are not installed implicitly: | Skill | Description | |-------|-------------| | `revyl-cli-atlas-review` | Manage grounded Atlas annotation feedback only when the user explicitly requests it. | | `revyl-cli-figma-review` | Guide frame or component comparisons between Figma and Atlas, with findings in chat, a private visual report, or explicitly requested Atlas comments and attachments. | | `revyl-cli-cross-platform-review` | Find meaningful differences within confirmed matching iOS and Android states. Does not infer missing screens or feature coverage from incomplete Atlas graphs. | | `revyl-cli-optimize-tests` | Use when the agent should optimize an existing Revyl YAML test using best practices and intent-driven instructions. | Retired platform recipe names (`revyl-cli-auth-bypass-expo` and the other stack suffixes) still select the parent skill. Existing legacy copies are preserved, not pruned; [MCP Setup](/agents/mcp#skill-selection-storage-and-updates) explains how installation proceeds when they conflict with shared storage. ## Manage Skills ```bash revyl skill list revyl skill list --all revyl skill list --installed --json revyl skill show --name revyl-cli-dev-loop revyl skill show --name revyl-cli-atlas revyl skill export --name revyl-cli-create -o SKILL.md revyl skill install --name revyl-cli-dev-loop --name revyl-cli-create revyl skill install --name revyl-cli-optimize-tests revyl skill update revyl-cli-dev-loop ``` `show` and `export` return only the root `SKILL.md`; use `install` for the complete package. See the [command reference](/reference/cli) for the full CLI management options. --- ## Prompt Examples ### CLI dev-loop ```text Use the revyl-cli-dev-loop skill. Detect the app stack, start or attach to the Revyl dev loop, keep it running after Dev loop ready, and verify with revyl device screenshot before changing strategy. ``` ### CLI create ```text Use the revyl-cli-create skill. Create a checkout smoke test from this flow, validate it, push it, and run it once. ``` ### Atlas understanding ```text Use the revyl-cli-atlas skill. Start from the app's graph anchors, visually inspect each relevant screen, traverse observed edges in both directions, and investigate misunderstood evidence through its clips and originating reports before answering. ``` ### Optimize tests ```text Use the revyl-cli-optimize-tests skill. Optimize the test . ``` ### Auth bypass ```text Use the revyl-cli-auth-bypass skill. Set up test-only auth bypass for this app, implement the handler in the detected stack, and verify valid and rejected links on a Revyl device. ``` ### Set up Cursor proof Automation ```text Use the revyl-proof-automation skill. Add the CI upload step and give me the Cursor Automation prompt and checklist for device proof on every PR. ``` ### Prove a CI-uploaded PR build The Cursor plugin also ships `revyl-proof-ci` (guidance only — agents still prove via the CLI). For the scheduled Automation path, see [Cursor proof (BYO-CI)](/integrations/cursor/proof) or use `revyl-proof-automation` to set it up.