← Search

Meticulous visual testing run for frontend changes
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit deb5e45
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Meticulous account…

Meticulous visual testing run for frontend changes

Upload a frontend build once, trigger visual test runs against different bases, then hand off to meticulous-review to classify changes as intended or unintended

At a glance
What
Upload a frontend build once, trigger visual test runs against different bases, then hand off to meticulous-review to classify changes as intended or unintended
Cost
Free
Needs
a Meticulous account, the Meticulous CLI (or MCP server) installed and configured, and a frontend build that matches what your CI uploads to Meticulous
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @alwaysmeticulous

Quick answer

Meticulous visual testing run for frontend changes is a free Muse skill that uploads a frontend build once, triggers visual test runs against different bases, then hands off to meticulous-review to classify changes as intended or unintended, so a visual regression is caught as a classified change, not a vague screenshot difference.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit deb5e45

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Meticulous account, the Meticulous CLI (or MCP server) installed and configured, and a frontend build that matches what your CI uploads to Meticulous Install "Meticulous visual testing run for frontend changes" for me. It teaches my agent @alwaysmeticulous's visual-testing workflow: find the expected build artifact in the CI config, upload the build once as a reusable deployment (works with uncommitted changes), trigger visual test runs against a base (same deploymentId can be re-triggered against different bases without rebuilding), then hand off to the meticulous-review skill to classify each visual change as intended or unintended. CLI and MCP variants included. ISC-licensed. Repository: https://raw.githubusercontent.com/alwaysmeticulous/skills/deb5e45e6e5666d6e6e8f554b71b69d8d5f62647/skills/meticulous-test/SKILL.md Pinned version: install the code at commit deb5e45e6e5666d6e6e8f554b71b69d8d5f62647 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "meticulous-test". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. run the meticulous-cli-update skill first if the CLI is stale; also install the meticulous-review skill — the review step is not bundled here). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit deb5e45 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
deb5e45 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.