Choose the right skill family
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
Interactiverevyl 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:
npx skills add, optional MCP, shared
package locations, global scope, and --copy compatibility, follow
MCP Setup.
Install by intent
Select only the workflows you want the agent to use:
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 modifyAGENTS.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:
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 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.Optional skills
Userevyl skill list --all to include narrower workflows and compatibility
skills. These are not installed implicitly:
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
explains how installation proceeds when they conflict with shared storage.
Manage Skills
show and export return only the root SKILL.md; use install for the
complete package. See the command reference
for the full CLI management options.
Prompt Examples
CLI dev-loop
CLI create
Atlas understanding
Optimize tests
Auth bypass
Set up Cursor proof Automation
Prove a CI-uploaded PR build
The Cursor plugin also shipsrevyl-proof-ci (guidance only — agents still prove
via the CLI). For the scheduled Automation path, see
Cursor proof (BYO-CI) or use
revyl-proof-automation to set it up.