Agent skill

Meticulous Test

Run a Meticulous test run after implementing a frontend change, then hand off to the meticulous-review skill to classify each visual change as intended or unintended.

MITAuto-check passedDevOps & Cloud

Install Meticulous Test

skills CLI

$ npx skills add FlintSH/Flare --skill meticulous-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install FlintSH/Flare meticulous-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/FlintSH/Flare.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/meticulous-test .claude/skills/meticulous-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "meticulous-test" agent skill from https://github.com/FlintSH/Flare/tree/main/.agents/skills/meticulous-test into .claude/skills/meticulous-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meticulous-test", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/FlintSH/Flare/tree/main/.agents/skills/meticulous-test

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add FlintSH/Flare --skill meticulous-test -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install FlintSH/Flare meticulous-test --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FlintSH/Flare.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/meticulous-test .agents/skills/meticulous-test && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "meticulous-test" agent skill from https://github.com/FlintSH/Flare/tree/main/.agents/skills/meticulous-test into .agents/skills/meticulous-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meticulous-test", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add FlintSH/Flare --skill meticulous-test -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install FlintSH/Flare meticulous-test --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FlintSH/Flare.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/meticulous-test .cursor/skills/meticulous-test && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "meticulous-test" agent skill from https://github.com/FlintSH/Flare/tree/main/.agents/skills/meticulous-test into .cursor/skills/meticulous-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meticulous-test", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/FlintSH/Flare.git --path .agents/skills/meticulous-test

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add FlintSH/Flare --skill meticulous-test -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install FlintSH/Flare meticulous-test --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FlintSH/Flare.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/meticulous-test .gemini/skills/meticulous-test && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "meticulous-test" agent skill from https://github.com/FlintSH/Flare/tree/main/.agents/skills/meticulous-test into .gemini/skills/meticulous-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meticulous-test", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install FlintSH/Flare meticulous-test

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add FlintSH/Flare --skill meticulous-test -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/FlintSH/Flare.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/meticulous-test .github/skills/meticulous-test && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "meticulous-test" agent skill from https://github.com/FlintSH/Flare/tree/main/.agents/skills/meticulous-test into .github/skills/meticulous-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meticulous-test", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add FlintSH/Flare --skill meticulous-test -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install FlintSH/Flare meticulous-test --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FlintSH/Flare.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/meticulous-test .opencode/skills/meticulous-test && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "meticulous-test" agent skill from https://github.com/FlintSH/Flare/tree/main/.agents/skills/meticulous-test into .opencode/skills/meticulous-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meticulous-test", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: meticulous-test
GitHub stars: 135
Token cost: ~1.2k tokens
SKILL.md length: 520 words
Files: 1
Skills in repo: 10
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Run a Meticulous test run after implementing a frontend change, then hand off to the meticulous-review skill to classify each visual change as intended or unintended.

Works in 4 steps: Build the frontend → Upload the build → Trigger a test run → …
Implementing a feature autonomously end-to-end before creating a PR
SKILL.md covers Step 1 -- Build the frontend, Step 2 -- Upload the build, Step 3 -- Trigger a test run and Step 4 -- Review the visual…
Calls npx and git

What it does

Meticulous Test is an agent skill from FlintSH/Flare. Run a Meticulous test run after implementing a frontend change, then hand off to the meticulous-review skill to classify each visual change as intended or unintended. Uploads the build once — the same build can be re-triggered against different bases without rebuilding — and it works with uncommitted changes. Use when implementing a feature autonomously end-to-end before creating a PR.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. It works with Docker, GitLab and Git. The repository describes itself as: A modern, lightning-fast file sharing platform built for self-hosting. Created with support for ShareX, KDE Spectacle, Flameshot, and easy to set up. The licence is MIT.

When your agent uses it

Implementing a feature autonomously end-to-end before creating a PR

Example prompts

“/meticulous-test”

Requirements

Node.js
Docker

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Build the frontend
Upload the build
Trigger a test run
Review the visual changes

What it can do on your machine

Read from SKILL.md and the folder at commit c910523. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npx
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Meticulous Test loads about 1.2k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 520 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~102
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FlintSH/Flare at commit c910523, republished under its MIT licence (© FlintSH). 520 words, ~1,228 tokens.

Download SKILL.mdSave it as .claude/skills/meticulous-test/SKILL.md (or your agent's skills folder).

name: meticulous-test
description: Run a Meticulous test run after implementing a frontend change, then hand off to the `meticulous-review` skill to classify each visual change as intended or unintended. Uploads the build once — the same build can be re-triggered against different bases without rebuilding — and it works with uncommitted changes. Use when implementing a feature autonomously end-to-end before creating a PR.
user-invocable: true

To test a frontend change using Meticulous, follow the workflow below step by step, using the CLI or MCP commands as described.

Before starting, run the meticulous-cli-update skill to ensure the Meticulous CLI and skills are up to date — unless it has already run earlier in this conversation, in which case skip it.

If you are already given a test run id, skip to Step 4.

Step 1 -- Build the frontend

Find out what build artefact Meticulous expects by checking your CI config for the corresponding step:
- GitHub: .github/workflows/*.yml for uses: alwaysmeticulous/report-diffs-action/upload-assets@v1 (build assets) or upload-container@v1 (docker image)
- GitLab: .gitlab-ci.yml (or an included .gitlab/ci/*.yml) for npx @alwaysmeticulous/cli ci upload-assets (build assets) or ci upload-container (docker image)
- Bitbucket: bitbucket-pipelines.yml for the same npx @alwaysmeticulous/cli ci upload-assets / ci upload-container step
Build the frontend following the same instructions as used in that CI config.

Step 2 -- Upload the build

Register the build as a reusable deployment with agent upload-build. This uploads the artefact and prints a deploymentId to stdout — it does not trigger a run yet.

bash

# CLI
meticulous agent upload-build --appDirectory <path-to-build>     # assets
meticulous agent upload-build --localImageTag <image-tag>        # container

# MCP (not 1:1 — request an upload URL, upload the artifact yourself, then register it)
request_asset_upload(size=<zipByteSize>)      # or request_container_upload() — no required args
# ... upload the zip/image to the returned URL/registry yourself ...
register_asset_build(uploadId="<id>", commitSha="<sha>")      # or register_container_build(uploadId="<id>", commitSha="<sha>")

--appDirectory points to the build output directory (e.g. a dist/ subfolder); --localImageTag is the local Docker image tag. The build mode is auto-detected.
The build's commit defaults to the local git HEAD. If the working tree is dirty, it is captured as an ephemeral commit (printed as commitSha (local, ephemeral due to dirty working tree): …) — see the uncommitted-changes note below.
Untracked files are rejected (they can't be captured) — git add them first.
Capture the deploymentId from stdout (pass --verbose to also see progress on stderr).

Show full SKILL.md (260 more words)Show less

Step 3 -- Trigger a test run

Trigger a run for the deployment, comparing against a base. Run it from the repo directory to infer both the base (merge-base with the origin default branch) and the git diff automatically:

bash

# CLI
meticulous agent trigger-test-run --deploymentId <deploymentId>

# MCP (never infers `baseSha`/`gitDiffOutput` — pass them explicitly — and always returns immediately without waiting for the run to finish)
trigger_test_run(deploymentId="<deploymentId>", baseSha="<sha>")

A base is required. It's auto-inferred from the current directory, or pass --baseSha <sha> (and optionally --gitDiffOutput) to set it explicitly.
Omit --deploymentId to use the most recent deployment already uploaded for the local HEAD commit instead — this requires a clean working tree (no uncommitted changes).
The command blocks until the run finishes by default and prints the testRunId to stdout; the final status is Failure when visual differences were detected (a normal completed verdict, not an error). Pass --dontWaitForTestRunToComplete to return as soon as the run is triggered.
One build, many bases: the same deploymentId can be re-triggered against different bases — just run agent trigger-test-run again with a different --baseSha. No rebuild or re-upload needed.

Note the testRunId from the output.

Step 4 -- Review the visual changes

Follow the meticulous-review skill, passing the testRunId from Step 3. It fetches the diff summary, inspects representative screenshots / DOM diffs / timelines, and produces a final report classifying each visual change as intended or unintended.

Uncommitted changes: if you built/tested with a dirty working tree, the run is recorded against an ephemeral commit that is not your HEAD (and isn't pushed). Commands that resolve a run from the local checkout — meticulous-review / agent test-run-diffs run with no --testRunId — won't find it by commit, so always pass the explicit --testRunId to the review step in that case.

Files

Just SKILL.md in .agents/skills/meticulous-test of FlintSH/Flare.

Open the folder on GitHubat commit c910523

Compare with similar skills

Meticulous Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Meticulous Test compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Meticulous Test this skillFlintSH/Flare	135	—	~1.2k	Automated safety check: Pass	MIT	4 days ago
Modern Web GuidanceJetBrains/skills	366	3 repos	~1.4k	Automated safety check: Pass	Apache-2.0	3 mo ago
Ssh Skillbadseal/ssh-skill	538	—	~2.4k	Automated safety check: Notes	None	1 mo ago
Setup Osworldxlang-ai/OSWorld-V2	359	1 repos	~2.6k	Automated safety check: Notes	Apache-2.0	9 days ago
Crabbox Quickstartopenclaw/crabbox	1.5k	—	~1.6k	Automated safety check: Notes	MIT	today
Reviewwerf/werf	4.7k	—	~2k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Modern Web Guidance
JetBrains/skills
Official
Search tool for modern web development best practices. An agent skill from JetBrains/skills.
366 GitHub starsUsed in 3 repos~1.4k tokens
DevOps & CloudAuto-check passed
Ssh Skill
badseal/ssh-skill
A skill your agent uses when a task requires SSH or SCP/SFTP behavior, a remote server, server alias/IP/hostname/user@host, bastion or jump-host access, remote command execution, upload/download…
538 GitHub stars~2.4k tokensUpdated 1 mo ago
DevOps & CloudAuto-check: notes
Setup Osworld
xlang-ai/OSWorld-V2
Provision and verify an OSWorld-V2 checkout after clone. An agent skill from xlang-ai/OSWorld-V2.
359 GitHub starsUsed in 1 repo~2.6k tokens
DevOps & CloudAuto-check: notes
Crabbox Quickstart
openclaw/crabbox
Gets you running your repository's tests in a disposable Docker or Podman container on your own machine with Crabbox, with no account and no cloud spend.
1.5k GitHub stars~1.6k tokensUpdated today
DevOps & CloudAuto-check: notes
Review
werf/werf
Code review of a pull request, branch, or diff. An agent skill from werf/werf.
4.7k GitHub stars~2k tokensUpdated yesterday
DevOps & CloudAuto-check passed
Megalinter Check
nvuillam/npm-groovy-lint
Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.
248 GitHub starsUsed in 1 repo~3.9k tokens
DevOps & CloudAuto-check: notes

More from FlintSH/Flare

All 10 skills in this repo

Meticulous CLI
FlintSH/Flare
Overview of the Meticulous CLI tool and its global options. An agent skill from FlintSH/Flare.
135 GitHub stars~1.4k tokensUpdated 4 days ago
Auto-check passed
Meticulous Fix
FlintSH/Flare
Fix the visual diffs that have been reviewed and rejected on a Meticulous test run, following their review comments if given.
135 GitHub stars~2.3k tokensUpdated 4 days ago
Auto-check passed
Meticulous Increase Coverage
FlintSH/Flare
Increase coverage for a Meticulous project by tracing specific under-covered files back to a real UI action in the codebase, driving that action with a real recorded browser session, and validating…
135 GitHub stars~7k tokensUpdated 4 days ago
Auto-check passed
Meticulous Iterative Dev
FlintSH/Flare
Iterative frontend development loop using Meticulous for per-step visual validation.
135 GitHub stars~1.3k tokensUpdated 4 days ago
Auto-check passed
Meticulous Review
FlintSH/Flare
Analyze a completed Meticulous test run — compare the diffs against the PR description to see what's expected, then focus on finding and flagging potential regressions.
135 GitHub stars~2.3k tokensUpdated 4 days ago
Auto-check passed
Meticulous Simulate And Diff
FlintSH/Flare
Run a Meticulous session simulation against a live URL and analyze the visual output — either by inspecting screenshots directly (quick-check mode) or by comparing pixel and HTML diffs against a…
135 GitHub stars~1.8k tokensUpdated 4 days ago
Auto-check passed

Works with

Questions about Meticulous Test

What does Meticulous Test do?

Run a Meticulous test run after implementing a frontend change, then hand off to the meticulous-review skill to classify each visual change as intended or unintended. Meticulous Test is an agent skill from FlintSH/Flare. Run a Meticulous test run after implementing a frontend change, then hand off to the meticulous-review skill to classify each visual change as intended or unintended.

When should I use Meticulous Test?

Meticulous Test fits situations like: implementing a feature autonomously end-to-end before creating a PR.

How do I install Meticulous Test in Claude Code?

Run `npx skills add FlintSH/Flare --skill meticulous-test -a claude-code`. Or copy the skill folder (.agents/skills/meticulous-test in FlintSH/Flare) into .claude/skills/meticulous-test in your project. Claude Code loads it when a task matches its description.

How do I install Meticulous Test in Codex?

Run `npx skills add FlintSH/Flare --skill meticulous-test -a codex`. Or copy the skill folder (.agents/skills/meticulous-test in FlintSH/Flare) into .agents/skills/meticulous-test in your project. Codex loads it when a task matches its description.

Can I use Meticulous Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FlintSH/Flare --skill meticulous-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meticulous-test, .gemini/skills/meticulous-test, .github/skills/meticulous-test and .opencode/skills/meticulous-test in your project.

What does Meticulous Test need to run?

Going by SKILL.md and its folder, Meticulous Test needs the command-line tools its instructions call (npx and git). Our summary lists: Node.js; Docker.

Does Meticulous Test access the network?

SKILL.md contains no URLs. Its commands use npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Meticulous Test safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Meticulous Test use?

Meticulous Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Meticulous Test use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Meticulous Test?

Skills that share tags, products or a category with Meticulous Test: Modern Web Guidance (JetBrains/skills, 366 stars), Ssh Skill (badseal/ssh-skill, 538 stars), Setup Osworld (xlang-ai/OSWorld-V2, 359 stars) and Crabbox Quickstart (openclaw/crabbox, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Meticulous Test?

FlintSH (a GitHub user) maintains it in FlintSH/Flare, which has 135 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.

Source: FlintSH/Flare on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Meticulous Test

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Step 1 -- Build the frontend

Step 2 -- Upload the build

Step 3 -- Trigger a test run

Step 4 -- Review the visual changes

Files

Compare with similar skills

Similar skills

More from FlintSH/Flare

Related

Questions about Meticulous Test