Back to Skills

meticulous-cli

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.

7stars2forksUpdated 7/6/2026

Security Assessment

Low Risk(70/100)

Detected risks:

Secret Exposure([references/download.md] Token=, [references/project.md] Token=)
Security Score70/100

About meticulous-cli

An overview of the Meticulous command-line tool, which records real user sessions and replays them against a running application to catch visual regressions. Distributed as part of the @alwaysmeticulous/cli npm package, it is aimed at teams who want an automated way to detect unintended UI changes without hand-writing assertions. The skill serves as the general entry point for questions about the CLI as a whole, its command groups, and the global flags shared by every command.

Commands are invoked as meticulous <command> [options]. The tool is organized into groups: auth for authentication such as whoami and logout, debug for AI-ready workspaces to investigate replay diffs and replays, download for pulling sessions, replays, and test runs locally, local for finding sessions relevant to the current branch's code changes, project for inspecting the authenticated project, simulate/replay for replaying a recorded session against a URL, and schema for emitting the CLI command schema as JSON for programmatic or agent use. Each group has its own reference document for full option details.

Four global options apply to every command: --logLevel to control verbosity, --dataDir to set where sessions and replays are stored, --rawJson to pass all options as a JSON string, and --dryRun to preview what a command would do without making changes. Authentication is via OAuth, with a login token stored on disk and reused across sessions; interactive commands open a browser sign-in automatically when needed. For non-interactive contexts such as CI, an API token can be supplied through --apiToken or the METICULOUS_API_TOKEN environment variable. A companion update skill installs or refreshes the CLI so it is current before other skills run.

FAQ

What is the Meticulous CLI used for?

It records user sessions and replays them against a URL to catch visual regressions, providing an automated way to detect unintended UI changes.

How is it installed or kept up to date?

The companion meticulous-cli-update skill installs it globally via npm install --global @alwaysmeticulous/cli@latest if missing. It can also be run as npx @alwaysmeticulous/cli when installed locally per project.

How do you authenticate in a non-interactive context like CI?

Use an API token supplied through the --apiToken flag or the METICULOUS_API_TOKEN environment variable, scoped to a specific organization or project. Interactive use relies on an OAuth browser sign-in whose token is stored on disk.

Which options apply to every command?

The global options are --logLevel, --dataDir, --rawJson, and --dryRun, accepted by all commands.

Can an agent retrieve the command schema programmatically?

Yes. The schema command outputs the full CLI command schema as JSON, and --rawJson lets you pass all options as a JSON string, both intended for programmatic or agent invocation.

All Files

8 files
references/local.md3.8 KB
View
SKILL.md3.0 KB
View
references/debug.md4.2 KB
View
references/schema.md1.9 KB
View
references/download.md3.9 KB
View
references/simulate.md5.7 KB
View
references/auth.md1.3 KB
View
references/project.md0.9 KB
View

Install meticulous-cli

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill