verify-feature SKILL.md skillA
verify-feature 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/verify-feature@git:20260901.dca22e5Pins git:20260901.dca22e5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arcasilesgroup/ai-engineering
- Path
skills/ai-verify/tiers/1-standalone/verify-feature/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260901.dca22e5, committed Sep 1, 2026
- Size
- 12,194 bytes
- Repository stars
- 62
- License
- Apache-2.0
Verify that a feature as built actually matches what was asked for — catching requirements that were quietly dropped, built differently than specified, or built without being asked for. Use this whenever you are partway through or wrapping up a feature and about to call it done, and whenever the user says "does this match the PRD/spec", "did we drift", "is this what I asked for", "check this against the requirements", "verify the feature", "did you build everything", or reviews work before a…
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
# Verify feature against requirements Code review asks "is this code correct and safe?" This asks a different question that review reliably misses: **is this the thing we agreed to build?** A dropped requirement compiles. A near-miss substitution passes lint. An unasked-for feature has no failing test. Nothing in the normal toolchain notices, which is why drift is usually found by a human weeks later. Your output is a verdict per requirement, backed by evidence, plus a list of gaps. You do not fix anything until the user picks what to fix. ## 1. Establish the contract, and write it down before reading the code First settle **which** feature you're verifying, since the answer scopes everything else. Usually it's obvious from the conversation. When invoked cold, infer it from the branch name and the diff against the base branch — a branch called `feat/mobile-channel-ui` touching the channel views names its own subject. If the diff spans two unrelated features, say so and ask which one rather than blending them into one confusing report. You cannot measure drift without a fixed thing to measure against. Find the contract in this order: …
Read the whole file at its exact version.
How to install
mdr add arcasilesgroup/ai-engineering/verify-feature@sha256:ddd7e5ca0c86c207The line at the top of this page pins the label git:20260901.dca22e5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way 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_mhwjszzfmapn77kj)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 1, 2026.
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 (12194 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 · 62 stars · license Apache-2.0 · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mhwjszzfmapn77kj GET https://markdownregistry.com/api/v1/resolve?ref=arcasilesgroup/ai-engineering/verify-feature GET https://markdownregistry.com/api/v1/blob/ddd7e5ca0c86c207d479c720caebd12be5927207191b5c6df9ecf566a3136abc
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.