feature-verify SKILL.md skillA
Removed from GitHub on 2026-11-09. The file no longer exists in its repository, and every version below is still saved here. mdr add no longer finds it by name, but a lockfile that pins one of these versions still installs it from its recorded commit, for as long as GitHub keeps that commit.
feature-verify from arcasilesgroup/ai-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add arcasilesgroup/ai-engineering/feature-verify@sha256:22bc92109ce286d0Pins the contents saved here, the only way to install this file now it is gone from GitHub. What a pinned install does.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arcasilesgroup/ai-engineering
- Path
skills/ai-verify/tiers/2-embedded/feature-verify/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260911.eccaa3a, committed Sep 11, 2026
- First version recorded
- Sep 1, 2026
- Size
- 16,412 bytes
- Repository stars
- 65
- License
- Apache-2.0
Cross-verify a just-finished feature with throwaway browser tests driven by chrome-headless-shell — proves the feature actually does what it was supposed to do, and proves the change didn't break the routes and components that depend on it. Reports a verdict with evidence and never edits app code. Use this whenever a feature, fix, refactor, or UI change has just been completed — including when the user says "done", "that's implemented", "verify this", "does it work?…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Feature Verification
You are the independent check on work that was just finished — often work you did yourself. That framing matters: the failure mode here is not "couldn't write a test", it's **writing a test that mirrors the implementation instead of the intent**, so it passes no matter what the code does. Everything below is built to keep those two things apart.
Two questions get answered every run:
1. **Does the feature do what it was meant to do?** Judged against intent stated before you re-read the implementation.
2. **Did building it break anything else?** Judged against the parts of the app that actually consume the changed code.
You report. You do not fix. The user chose report-only deliberately — an agent that grades its own work and then patches it will quietly weaken the test instead of fixing the bug. Diagnose precisely, hand it back.
## Step 1 — Pin down intent, before re-reading the implementation
Write down the acceptance criteria first, from sources that describe what was *wanted*:
- The user's own words in this conversation ("add a filter that persists across reloads")
- A ticket, issue, or spec if one was referenced
…Read the whole file at its exact version.
How to install
The line at the top of this page is already the fingerprint pin, because a file GitHub no longer serves cannot be found by its label. With it the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_izkog7k4plzwbtsn)
7 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 1, 2026 and Sep 11, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260911.eccaa3a latest | 2026-09-11 | eccaa3a | 16,412 B | A | view · diff |
| git:20260901.dca22e5 | 2026-09-01 | dca22e5 | 16,416 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16412 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
arcasilesgroup/ai-engineering · 65 stars · license Apache-2.0 · pushed 2026-11-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_izkog7k4plzwbtsn GET https://markdownregistry.com/api/v1/resolve?ref=arcasilesgroup/ai-engineering/feature-verify GET https://markdownregistry.com/api/v1/blob/22bc92109ce286d097e94a07df7b4e4cdbe80a2846440631f8c1b4974d5cadaf
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.