Meticulous CLI skill: the meticulous commands for your agent
Teaches Claude the meticulous command line tool, which records user sessions and replays them to catch visual regressions.
- Installs
- 8.8K
- on skills.sh
- Stars
- 10
- on GitHub
- Files
- 8
- besides SKILL.md
- Updated
- Oct 2026
- last repo commit
meticulous-cli is the command reference for the Meticulous CLI. SKILL.md lists 8 command groups (agent, auth, debug, download, local, project, simulate or replay, and schema), 3 global options, and how sign-in works. It links to 8 reference files, one per group.
It loads when you ask about the CLI in general, its commands or global flags. SKILL.md says to run meticulous-cli-update first. The agent commands are also exposed as tools on a hosted MCP server, and the skill explains the mapping.
Good for
- Developers using Meticulous visual regression tests who want their agent to run the CLI
- Anyone asking what the Meticulous CLI can do or which global flags exist
Install meticulous-cli
Claude Code
- 1
Copy this prompt.
Install the meticulous-cli skill in Claude Code. Run this command: /plugin marketplace add alwaysmeticulous/skills /plugin install meticulous@meticulous Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
The skills call the meticulous command (CLI) or the matching tools on the hosted MCP server at app.meticulous.ai. Each skill starts by running meticulous-cli-update, so install the whole set. You need a Meticulous project. The Claude directory lists Meticulous as a connector for the Claude app, but that adds the MCP tools only and not these skills, so we store no Claude app upload tab.
From the project README. Source.
What's in the skill
When it loads
Overview of the Meticulous CLI tool and its global options. Use when asking about the meticulous CLI in general, available commands, or global flags that apply to all commands.
Sections in SKILL.md
- Invocation
- Command Groups
- Global Options
- Authentication
- MCP server
- Example
Key facts
- Installs on skills.sh
- 8,786 as of 2026-11-02
- skills.sh audits
- Gen Agent Trust Hub pass, Socket pass, Snyk warn
- Last repo commit
- 2026-10-29
What it includes
Read, analyse and trigger test runs
The agent-facing commands, also exposed on the MCP server. They include approve, reject and ignore for diffs, comments, uploading a build and triggering a test run.
Try: “Show the diffs on the test run for my current commit.”
Runs code ·
agentLog in, whoami, logout, project selection
OAuth token stored on disk. An API token via --apiToken or METICULOUS_API_TOKEN works for CI.
Runs code ·
authSet up debug workspaces for replays and diffs
Creates workspaces for investigating replay diffs. debug clean deletes workspaces: with --all it deletes them without the interactive menu.
Delete ·
debugDownload sessions, replays and test runs
Saves data under ~/.meticulous by default (set with --dataDir).
Runs code ·
downloadFind sessions relevant to your branch changes
local relevant-sessions picks sessions that touch the code you changed.
Runs code ·
localShow the project you are signed in to
project show prints the project details.
Runs code ·
projectReplay a recorded session against a URL
Replays in Chromium with recorded network responses, optionally diffing screenshots against a base replay.
Try: “Replay session abc against http://localhost:3000.”
Runs code ·
simulate / replayPrints the CLI command schema as JSON
Meant for agents that need exact options.
Runs code ·
schema--logLevel, --dataDir, --jsonArgs
--logLevel sets log detail, --dataDir sets where data lives (default ~/.meticulous), --jsonArgs passes all options as JSON.
Read ·
Global options
From the official docs
Permissions
Medium risk
Claude runs the Meticulous CLI, and some of its commands upload builds, trigger runs and record decisions on your diffs. Approve those commands one by one.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
Some commands change your Meticulous project
SKILL.md says the agent commands include uploading a build and triggering a test run, and the reference lists approve, reject and ignore for diffs. Approve those commands one by one. github.com
debug clean can delete workspaces
The debug reference says meticulous debug clean --all deletes debug workspaces without the interactive menu. Check which workspaces exist before approving it. github.com
Replays run a browser against a URL
The simulate command replays recorded sessions in Chromium against the URL you give it, using recorded network responses. Point it at your own dev server. github.com
Data is saved under ~/.meticulous
Downloads and replays go to ~/.meticulous unless you set --dataDir. They can include recorded user sessions from your project. github.com
The plugin route also connects a hosted MCP server
The repo's .mcp.json adds the Meticulous server at app.meticulous.ai/api/mcp. The README says the plugin connects it automatically and you authenticate in your browser. github.com
The plugin route installs all 11 skills
Counted from the repo's file tree. The plugin manifest lists no hooks, and the repo has no agent definition files. Use the skills CLI route if you want to pick skills. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | SKILL.md defines no read-only mode. Some commands only read, but the agent group includes mutating ones. |
|---|---|
| Talks to | app.meticulous.ai |
| Sign-in and keys | An OAuth login token is stored on disk and reused. An API token via METICULOUS_API_TOKEN or --apiToken is also supported. |
| Scopes |
|
Questions
What does the Meticulous CLI skill do?
It tells Claude what the meticulous command can do and how to call it: review test runs, replay sessions, download data, sign in and print the command schema.
How do I install it?
Use the install box at the top of the page. It installs the whole Meticulous set, because the skills call each other. You also need the CLI itself from npm. We store no Claude app upload because the skills drive a local CLI.
Is this the official Meticulous skill?
It is in Meticulous's own repo, and the plugin manifest names Meticulous as the author.
Can I use the MCP server instead of the CLI?
For the agent commands, yes in part. SKILL.md says they are also exposed as tools on the hosted MCP server at app.meticulous.ai/api/mcp, so an MCP client can call them instead of shelling out. It names only those plus download session as having MCP tools. It adds that MCP tools never infer git context, so you pass the commit details yourself.
How does it sign in?
With a browser OAuth login whose token is stored on disk. Without a terminal, commands fail and tell you to run meticulous auth login. A project API token also works for CI.
Is it safe?
It bundles no scripts, but the commands it teaches can change things: upload a build, trigger a test run, and approve, reject or ignore diffs in your Meticulous project. Claude runs these in your shell, so approve them one by one.
Does it need an account?
Yes, a Meticulous account with a project.
Information
updated Nov 2, 2026
- Repository
- alwaysmeticulous/skills
- Folder
skills/meticulous-cli
Sources
Docs, issue trackers and discussions this page is built from.
Show all 9Hide
- README · github.com
- Meticulous docs: setting up for agents · app.meticulous.ai
- Cursor docs: Plugins · cursor.com
- meticulous-cli SKILL.md · github.com
- agent.md · github.com
- simulate.md · github.com
- .mcp.json · github.com
- marketplace.json · github.com
- debug reference · github.com