revylai/revyl-cli

Revyl CLI Skill

Use this as the default Revyl skill when workflows should be expressed as revyl commands.

Native Agent Behavior

• Ask at most 1-3 concise clarification questions only when the target app, platform, session, URL, or sensitive action cannot be inferred from the repo or Revyl CLI.
• Prefer safe defaults and keep moving when revyl init --detect, revyl dev list, revyl app list, screenshots, or reports can answer the question.
• When Revyl prints a viewer, editor, report, or local app URL, open it in the native browser/tool surface when available: Codex Browser/in-app browser for local URLs, Revyl URLs, screenshots, and page checks; Claude Code .claude/skills slash-command discovery plus WebFetch/WebSearch or configured MCP/browser tools; Cursor .cursor/skills plus .cursor/rules/revyl-skills.mdc and available MCP/browser tools.
• If no browser tool is exposed, report the URL and verify through revyl device screenshot, revyl device report, or revyl test report instead of claiming browser access.
• Confirm before entering sensitive data, submitting forms, uploading files, accepting browser permissions, changing sharing/access, or deleting data.

Route to Specific CLI Skills

• Use revyl-cli-dev-loop for local dev loop workflows and exploratory path capture.
• Use revyl-cli-create for authoring robust YAML tests.
• Use revyl-cli-auth-bypass for test-only authenticated app state setup.
• Use revyl-cli-analyze for failed run triage.

Operating Rules

1. Prefer explicit command sequences.
2. Keep secrets in env vars or test variables.
3. Keep steps deterministic and avoid hidden assumptions.

Baseline Checks

export PATH="$HOME/.revyl/bin:$HOME/.local/bin:$PATH"
revyl auth status
revyl version
revyl test list

For headless agents, set REVYL_API_KEY and run:

revyl auth login --api-key "$REVYL_API_KEY"