Revyl Cli

Organization

RevylAI

revyl-cli

Base CLI skill for Revyl command-driven workflows. Use when users want shell-command setup, Atlas understanding, execution, test authoring, or run triage without MCP tool calls.

Overview

Publisher	RevylAI
Repository	`revyl-cli`
Skill name	`revyl-cli`
Stars	522
Forks	25
Bundled files	1
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by RevylAI on GitHub. Read the source before you install it.

Installation

Install the Revyl Cli AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/RevylAI/revyl-cli/tree/main/skills/revyl-cli
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/RevylAI/revyl-cli.git /tmp/revyl-cli
mkdir -p .claude/skills
cp -r /tmp/revyl-cli/skills/revyl-cli .claude/skills/revyl-cli

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Revyl Cli in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Revyl Cli on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Revyl Cli is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 compatibility links plus WebFetch/WebSearch or configured MCP/browser tools; Cursor .cursor/skills when using --copy, otherwise shared .agents/skills, plus available MCP/browser tools. Codex also discovers shared .agents/skills directly.
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.
A screenshot URL or local image path is not visual verification. Open and read the image before making claims about visible UI.
Confirm before entering sensitive data, submitting forms, uploading files, accepting browser permissions, changing sharing/access, or deleting data.
When a revyl command prints that a newer Revyl CLI is available or that this version will soon stop working, run the upgrade command it names once before continuing, unless the CLI version is deliberately pinned (for example in CI); if the upgrade fails, report it and keep working on the current version.

Route to Specific CLI Skills

Use revyl-cli-dev-loop for local dev loop workflows and exploratory path capture.
Use revyl-cli-atlas for media-grounded questions about an app's screens, graph relationships, journeys, or coverage, including reconciling unexpected evidence through clips, extracted frames, and originating reports.
Use revyl-cli-atlas-review only when the user explicitly requests an Atlas feedback mutation.
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

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

Baseline Checks

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

When revyl auth status reports no credential:

bash
# Headless agent with REVYL_API_KEY in the environment. Preferred: the key
# never reaches argv or the process list.
revyl auth persist-cloud-env

# A human is available: prints an approval URL to open in any browser.
revyl auth login

revyl auth login --api-key=$REVYL_API_KEY also works, but the value must use the = form; a space-separated value is ignored and the CLI prompts instead.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Revyl Cli AI skill do?

Base CLI skill for Revyl command-driven workflows. Use when users want shell-command setup, Atlas understanding, execution, test authoring, or run triage without MCP tool calls.

Why use Revyl Cli on TypingMind?

Because you install it once and use it with any model. Revyl Cli is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Revyl Cli in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RevylAI/revyl-cli/tree/main/skills/revyl-cli. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Revyl Cli?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Revyl Cli?

As many as you like. As long as a model supports skills, you can use Revyl Cli with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Revyl Cli AI skill free?

It is published on GitHub by RevylAI. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Context And Decisions

affaan-m

CommunityPopular

Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require…

Docs Governance

Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks…

Ecc Conventions

Development conventions and patterns for ECC. JavaScript project with conventional commits.

Mcp Dependency Review

affaan-m

CommunityPopular

Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Revyl CLI Skill

Native Agent Behavior

Route to Specific CLI Skills

Operating Rules

Baseline Checks

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now