Skip to content
Back to search

revyl-cli

CLI

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/RevylAI/revyl-cli with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/RevylAI/revyl-cli'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/revylai--revyl-cli/badge.svg)](/listings/revylai--revyl-cli)

HTML

<a href="/listings/revylai--revyl-cli"><img src="/api/listings/revylai--revyl-cli/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

sh

curl -fsSL https://revyl.com/install.sh | sh

Windows PowerShell

irm https://raw.githubusercontent.com/RevylAI/revyl-cli/main/scripts/install.ps1 | iex

Homebrew (macOS)

brew install RevylAI/tap/revyl

pipx (cross-platform)

pipx install revyl

uv

uv tool install revyl

The PyPI package is CLI-only and contains the native binary for your platform, so `uv`, `pipx`, and `pip` do not download executable code at first run.

See [Local runtime files](docs/local-runtime-files.md) for managed storage paths, permissions, and directory-symlink restrictions.

For a restricted or headless runner, see [Sandboxed environments](docs/sandboxed-environments.md). It covers a writable home and runtime state directory, non-interactive `PATH`, proxy and CA trust, minimum egress, and the boundary between local inspection and authorized cloud actions.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "revyl",
  3. "description": "Revyl's local Claude Code plugin: a pinned Revyl CLI launcher and dev-loop skills for running and verifying mobile apps on cloud devices.",
  4. "owner": {
  5. "name": "Revyl",
  6. "email": "support@revyl.ai"
  7. },
  8. "plugins": [
  9. {
  10. "name": "revyl-cli",
  11. "source": "./plugins/revyl",
  12. "description": "Run mobile changes on Revyl cloud devices and verify them with screenshots and semantic validation through the Revyl CLI.",
  13. "category": "development"
  14. }
  15. ]
  16. }
README.md · README · 398 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <img src="docs/assets/hero.gif" alt="Revyl" width="600" />
  3. </p>
  4. <h1 align="center">Revyl</h1>
  5. <p align="center">
  6. <em>Proactive Reliability for Your Apps</em>
  7. </p>
  8. <p align="center">
  9. <a href="https://github.com/RevylAI/revyl-cli/releases"><img src="https://img.shields.io/badge/version-0.2.24-9D61FF" alt="Version" /></a>
  10. <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="License: MIT" /></a>
  11. <a href="https://github.com/RevylAI/homebrew-tap"><img src="https://img.shields.io/badge/brew-RevylAI/tap/revyl-orange" alt="Homebrew" /></a>
  12. <a href="https://pypi.org/project/revyl/"><img src="https://img.shields.io/pypi/v/revyl" alt="PyPI" /></a>
  13. </p>
  14. ---
  15. Revyl is an AI-powered testing platform for your apps. Define tests in natural language, run them on cloud devices and computers, and catch bugs before your users do. It works with iOS, Android, web and Mac, supports Expo / React Native / Flutter / native builds, and integrates with your CI pipeline and AI coding tools.
  16. ## For coding agents
  17. To set up Revyl for a user, run these from the app's directory:
  18. ```bash
  19. curl -fsSL https://revyl.com/install.sh | sh && export PATH="$HOME/.revyl/bin:$PATH"
  20. revyl auth status --json # sign in first if "authenticated" is false
  21. revyl skill install --yes # recommended skills for this project
  22. revyl skill show --name revyl-cli # read the main skill and follow it
  23. ```
  24. To sign in, run `revyl auth login` and post the approval URL it prints as a
  25. link; the user can approve it from any browser. A hosted agent with
  26. `REVYL_API_KEY` in its environment is already signed in; it also runs
  27. `revyl auth persist-cloud-env` so an MCP server that does not inherit the
  28. variable can use it. Then follow the `revyl-cli-dev-loop` skill to start a
  29. cloud device with `revyl dev --remote --detach --json`, and share the
  30. `viewer_url` it returns.
  31. In a project that already uses Revyl, the open [skills](https://skills.sh)
  32. installer adds the same recommended skills:
  33. ```bash
  34. npx skills add RevylAI/revyl-cli#stable -y
  35. ```
  36. `#stable` matches the latest CLI release; `main` can be ahead of it. Name an
  37. optional skill from `revyl skill list --all` with `--skill <name>`, and refresh
  38. with `npx skills update`. For MCP and editor setup, see
  39. [MCP Setup](https://docs.revyl.com/cli/mcp-setup).
  40. ## Install
  41. ### sh
  42. ```bash
  43. curl -fsSL https://revyl.com/install.sh | sh
  44. ```
  45. ### Windows PowerShell
  46. ```powershell
  47. irm https://raw.githubusercontent.com/RevylAI/revyl-cli/main/scripts/install.ps1 | iex
  48. ```
  49. ### Homebrew (macOS)
  50. ```bash
  51. brew install RevylAI/tap/revyl
  52. ```
  53. ### pipx (cross-platform)
  54. ```bash
  55. pipx install revyl
  56. ```
  57. ### uv
  58. ```bash
  59. uv tool install revyl
  60. ```
  61. The PyPI package is CLI-only and contains the native binary for your platform,
  62. so `uv`, `pipx`, and `pip` do not download executable code at first run.
  63. See [Local runtime files](docs/local-runtime-files.md) for managed storage paths,
  64. permissions, and directory-symlink restrictions.
  65. For a restricted or headless runner, see [Sandboxed environments](docs/sandboxed-environments.md). It covers a writable home and runtime state directory, non-interactive `PATH`, proxy and CA trust, minimum egress, and the boundary between local inspection and authorized cloud actions.
  66. ## Authenticate
  67. Create a free account at [app.revyl.com](https://app.revyl.com), then log in via the CLI:
  68. ```bash
  69. revyl auth login # Approve in a browser, then credentials are stored locally
  70. ```
  71. The CLI prints an approval URL and a short code and waits. Open the URL wherever
  72. you are signed in — it does not have to be this machine, so the same command
  73. works over SSH, in a container, and in a cloud agent.
  74. For an unattended machine, use an API key from your dashboard instead:
  75. ```bash
  76. revyl auth login --api-key # Prompts for the key and stores it
  77. export REVYL_API_KEY=your-api-key # Or pass it through the environment
  78. ```
  79. ## Quick Start
  80. ```bash
  81. cd your-app
  82. revyl doctor # Check CLI, auth, connectivity
  83. revyl auth login # Approve in a browser (if not already authed)
  84. revyl init # Detect and write the local project config
  85. revyl skill install # Install recommended agent skills (picker preselects them)
  86. revyl build --profile development --platform ios # Build one recipe in the cloud
  87. revyl dev --profile development --platform ios # Launch TUI: live-device development loop
  88. ```
  89. `revyl init` always writes a stable `project.id` in `.revyl/config.yaml`. When
  90. detection succeeds, it also writes `build.framework` and named profiles for the
  91. detected iOS and/or Android platforms before any optional interactive onboarding.
  92. Supplying a project ID writes it locally but does not validate, attach, or publish
  93. it; use `-y` to stop after local config creation. Authenticated interactive setup
  94. can continue into `revyl github setup` after the project config has been written.
  95. GitLab automation is configured separately with `revyl gitlab setup`.
  96. When the connected provider
  97. can access the repository, committing that valid config to the repository's default branch
  98. reconciles a matching server project or creates a new Git-managed project when
  99. its `project.id`, project root, and config path are unclaimed and its references
  100. are valid. Pull requests validate new configs as unpublished bootstrap candidates;
  101. creation occurs only from the actual merged default-branch commit. `revyl config
  102. push` remains the explicit manual publication and recovery path.
  103. For GitLab automation tokens, terminal connection, and manual webhooks, see
  104. [Connect GitLab](https://docs.revyl.com/integrations/gitlab).
  105. For an existing legacy file, preview or perform the local conversion explicitly:
  106. ```bash
  107. revyl config migrate --check # Summarize the migration; do not write
  108. revyl config migrate # Confirm, back up, and replace atomically
  109. revyl config migrate --write # Back up and replace without confirmation
  110. ```
  111. A successfully prepared legacy migration uses one concise human-readable
  112. summary of whether fields will be dropped or defaulted; a write creates an
  113. exact-byte backup. JSON `--check` output contains the complete migration
  114. proposal and migration ledger. Migration
  115. externalizes legacy top-level test aliases to conflict-checked
  116. `.revyl/tests/<alias>.yaml` files, preserves an existing matching mapping
  117. byte-for-byte, and stops on destination conflicts because those are unsafe to
  118. write. The retired top-level workflow alias cache is reported and removed.
  119. The conversion exists only in your checkout until you commit it. After
  120. migrating, commit the converted `.revyl/config.yaml` and any new
  121. `.revyl/tests/` files with your change, but not the backup; otherwise every
  122. fresh checkout fails with the legacy-format error again. A write lists those
  123. files, and `--write --json` reports them in
  124. `uncommitted_config_migration.repository_relative_paths_to_commit`. Until the
  125. commit lands, commands that read the project config print a one-line stderr
  126. reminder at most once every 24 hours per machine, never with `--json` or
  127. `--quiet`. If you can't commit, tell the repository owner.
  128. When authenticated, migration may make read-only verified lookups to reuse or
  129. interactively select a project from the verified repository, resolve enabled
  130. legacy PR-build app names to exact platform app IDs, and resolve legacy PR
  131. workflow names to exact organization workflow IDs.
  132. Missing, duplicate, or inaccessible workflow names are omitted and reported,
  133. including the implicit `smoke` workflow from the legacy `smoke_every_pr`
  134. preset. An enabled PR build is never silently omitted: app or framework meaning
  135. that still cannot be resolved is reported as lossy and omitted from the best-effort
  136. proposal. Inspect JSON `--check` before writing; afterward, compare the reported
  137. backup or ask a coding agent to reconcile omissions. Migration
  138. never creates or attaches a server project, pulls or publishes configuration,
  139. or otherwise mutates server state. Edit the project YAML directly when you
  140. need to change project settings, then run `revyl config validate`.
  141. You can also create and edit manual-authority projects from the GitHub integration in
  142. the Revyl web app. After creating a project there, run `revyl config pull` from that
  143. project root (or a directory beneath it). If no local config exists, the CLI verifies
  144. the connected repository and writes the nearest matching project's configuration to
  145. its exact `.revyl/config.yaml` path; it never imports legacy or invalid remote state.
  146. When an existing config differs, pull creates an exact-byte backup, atomically
  147. replaces the file, and reports the backup path without prompting. If the local
  148. project was deleted and exactly one active replacement owns that same root, pull
  149. performs the same backup and replacement without trusting the stale ID.
  150. Project roots are immutable. Correct a mistaken root by deleting the manual project
  151. in the web app, creating its replacement at the intended root, then running
  152. `revyl -C <replacement-root> config pull`. A Git-managed project must first return to manual
  153. authority by removing its designated config file from the repository's default branch; that file
  154. removal alone preserves the project and its automation. Project deletion remains a
  155. web operation—there is no CLI project-delete command—and preserves the repository
  156. connection, GitHub installation, report destination, historical results, and work
  157. that already started.
  158. Build profiles are customer-named recipes, not active modes. A profile can
  159. contain an iOS recipe, an Android recipe, or both. Select the profile and
  160. platform per invocation. `revyl build` executes the recipe on a Revyl cloud
  161. runner by default, with its remote image and caches:
  162. ```bash
  163. revyl build --profile development --platform ios
  164. ```
  165. When omitted values have exactly one eligible choice, the CLI resolves them.
  166. Otherwise it prompts interactively or fails non-interactively with the valid
  167. choices. No profile is stored as active or default.
  168. See [Build with Revyl](docs/builds.md) for prerequisites, source uploads,
  169. billing, and migration guidance for existing scripts. Builds land on `--branch`
  170. when supplied. Otherwise they use your Git branch when automatic Git branch
  171. detection is enabled in the app's Build branches settings, or the app's default
  172. branch when detection is disabled or no Git branch is available. See
  173. [Build branches from the CLI](docs/build-branches.md).
  174. When you're ready to run outside the dev loop:
  175. ```bash
  176. revyl test run login-flow --build # Build, upload, and run in one step
  177. revyl test run login-flow --no-open # Suppress default report opening for a blocking terminal run
  178. revyl workflow create smoke-tests --tests login-flow,checkout
  179. revyl workflow run smoke-tests # Run the full workflow
  180. revyl explore run --platform ios # Explore the app and build its Atlas map
  181. ```
  182. Blocking human-terminal test and workflow runs open their completed report by
  183. default. Use `--no-open` to suppress it. No-wait, JSON, GitHub Actions, CI,
  184. SSH, and other headless executions never open a browser.
  185. YAML-first creation requires the selected project to already have a
  186. `.revyl/config.yaml`. Pull an existing registered project, initialize a new
  187. local project, or migrate a legacy file before creating the test:
  188. ```bash
  189. revyl config pull # Existing project already registered with Revyl
  190. # or: revyl init -y # New local project
  191. # legacy only: revyl config migrate --check && revyl config migrate, then commit .revyl/config.yaml and new .revyl/tests/ files
  192. revyl test create login-flow --from-file ./login-flow.yaml
  193. revyl test create --from-session <session-id> login-flow --app <app-id>
  194. ```
  195. `test create --from-file` validates and copies the YAML into the selected
  196. project; it never creates or migrates project configuration.
  197. See the [Revyl Docs](https://docs.revyl.com/) for the full authoring workflow, YAML examples, module imports, and troubleshooting.
  198. > `revyl dev` starts a live-device development loop and installs a build from one
  199. > named profile/platform recipe. Pass `--profile` and
  200. > `--platform` explicitly, or let Revyl resolve a unique development-like or
  201. > sole eligible choice. Ambiguous interactive runs prompt; non-interactive runs
  202. > fail with the valid choices. No profile or platform is stored as active or
  203. > default.
  204. ## Agent Skills
  205. For guided comparisons of Figma frames or components with Atlas screenshots,
  206. see the [Figma review handoff](docs/figma-review.md), including a shareable setup
  207. prompt and private report or annotation options.
  208. For iOS/Android comparisons without Figma, use the
  209. [cross-platform review handoff](docs/cross-platform-review.md). It compares
  210. confirmed matching states without treating unmatched screens as missing features.
  211. Interactive `revyl init` offers optional agent skill setup. Choose your tool
  212. and the skills you want; the recommended skills are preselected, and an empty
  213. selection skips installation. The standalone `revyl skill install` command uses
  214. the same preselected skill picker:
  215. ```bash
  216. revyl skill list # First-class workflows
  217. revyl skill list --all # Include optional and compatibility skills
  218. revyl skill install # Select skills interactively
  219. revyl skill install --cursor --yes # Install the recommended skills without prompting
  220. revyl skill install --name revyl-cli-dev-loop --name revyl-cli-create --agent codex --yes
  221. revyl skill list --installed --json # Inspect installed project and global skills
  222. revyl skill update # Update installed, unmodified project skills
  223. revyl skill update --global # Update installed, unmodified global skills
  224. revyl skill show --name revyl-cli-dev-loop
  225. revyl skill export --name revyl-cli-create -o SKILL.md
  226. ```
  227. Without `--name`, noninteractive installs, `--yes`, and `--json` install the
  228. recommended skills from `revyl skill list` and name them on stderr; `--json`
  229. output adds `"selection": "default"`. Repeat `--name` to choose specific
  230. skills, and use `--all` only when you deliberately want the entire catalog.
  231. Packages live in `.agents/skills/`, which Cursor and Codex discover directly.
  232. Claude Code uses per-skill relative links under `.claude/skills/`. Other agents
  233. that read the shared directory can also discover these skills. `--global`
  234. selects the equivalent directories under your home directory; `--copy` keeps
  235. independent packages in each selected tool's legacy skill directory instead.
  236. Conflicting legacy packages in any agent directory block shared storage, even
  237. when you selected another agent. This includes retired auth-bypass platform
  238. aliases; Revyl preserves rather than prunes them. Noninteractive installs then
  239. continue as if `--copy` were given; move conflicting copies aside to switch to
  240. shared storage. In `init`, choose **Claude Code (copy mode)** when Claude
  241. compatibility links are unavailable.
  242. A symlinked shared directory must resolve inside the selected project or home
  243. directory. Installation does not modify
  244. `AGENTS.md` or inject Cursor rules. For client-specific setup and optional MCP,
  245. see [MCP Setup](https://docs.revyl.com/cli/mcp-setup).
  246. Installation copies the complete skill package, including source-authored
  247. agent metadata and any references, scripts, or assets. `show` and `export`
  248. return only the root `SKILL.md`, not an installable package. Auth-bypass loads
  249. only the reference for the detected stack. Auth-bypass and Atlas review require
  250. an explicit user request; ordinary workflows allow implicit invocation.
  251. Existing packages are unchanged unless you explicitly use `--force`, which
  252. replaces the selected package and discards local edits. Prefer
  253. `revyl skill update` to refresh already-installed, Revyl-managed packages from
  254. your CLI version: it preserves local edits and unmanaged packages, reports conflicts,
  255. and never adds skills. `revyl upgrade` updates only the binary and may remind
  256. you to run `revyl skill update`; it does not install or refresh skills.
  257. A customized package is reported as `preserved` and makes `skill update` exit
  258. non-zero, so name only the skills you want refreshed. See
  259. [Agent skills](docs/upgrade.md#agent-skills) for the reminder and older CLIs.
  260. Use `revyl-cli-dev-loop` when you want the agent to start or attach to a generic
  261. Revyl dev loop, interact with the device, and verify with screenshots or
  262. reports. Use `revyl-cli-atlas` when the agent should explore an app bottom-up as
  263. a graph, opening relevant screenshots at each node and tracing misunderstood
  264. connections backward through edge clips and their originating reports. Use
  265. `revyl-cli-atlas-review` when the user explicitly asks the agent to create or
  266. manage grounded Atlas annotations. Use
  267. `revyl-cli-create` when you want the agent to author or refine a
  268. stable Revyl YAML test, validate it, push it, run it, and iterate from reports.
  269. Use `revyl-cli-auth-bypass` when the agent should set up test-only auth bypass
  270. after inspecting the app. Implement the handler in the detected stack; do not
  271. install a separate platform skill.
  272. Example prompts:
  273. ```text
  274. 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.
  275. ```
  276. ```text
  277. 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.
  278. ```
  279. ```text
  280. Use the revyl-cli-create skill. Create a checkout smoke test from this flow, validate it, push it, and run it once.
  281. ```
  282. ```text
  283. Use the revyl-cli-auth-bypass skill. Set up test-only auth bypass for this app and verify valid and rejected links on a Revyl device.
  284. ```
  285. ## Documentation
  286. For full documentation of the CLI see the [Revyl Docs](https://docs.revyl.com/).
  287. ## Troubleshooting
  288. <details>
  289. <summary>Xcode / Command Line Tools errors during <code>brew upgrade revyl</code></summary>
  290. ```bash
  291. softwareupdate --all --install --force
  292. sudo xcode-select -s /Library/Developer/CommandLineTools
  293. brew upgrade revyl
  294. ```
  295. If `softwareupdate` does not install Command Line Tools, reinstall them:
  296. ```bash
  297. sudo rm -rf /Library/Developer/CommandLineTools
  298. sudo xcode-select --install
  299. ```
  300. If you use full Xcode builds, install the latest Xcode version from the App Store and then run:
  301. ```bash
  302. sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
  303. ```
  304. </details>
  305. <details>
  306. <summary>Homebrew directory ownership errors</summary>
  307. ```bash
  308. sudo chown -R "$(whoami)" /opt/homebrew /Users/"$(whoami)"/Library/Caches/Homebrew /Users/"$(whoami)"/Library/Logs/Homebrew
  309. chmod -R u+w /opt/homebrew /Users/"$(whoami)"/Library/Caches/Homebrew /Users/"$(whoami)"/Library/Logs/Homebrew
  310. ```
  311. </details>
  312. ## License
  313. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.