ai-spec-coverage-mapper SKILL.md skillA
ai-spec-coverage-mapper from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/ai-spec-coverage-mapper@git:20260813.83125c6Pins git:20260813.83125c6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-ai-assisted/skills/ai-spec-coverage-mapper/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260813.83125c6, committed Aug 13, 2026
- First version recorded
- Jul 20, 2026
- Size
- 7,556 bytes
- Repository stars
- 11
- License
- MIT
Build-an-X workflow that uses an LLM to map existing tests to spec sections - given a spec doc + the test suite, the LLM identifies which tests cover which sections, surfaces uncovered sections (gap), and recommends specific tests to add. Output is a coverage matrix per spec ID. Scope is mapping tests that already exist and naming the gaps, not authoring tests for new acceptance criteria. Use when a spec doc and a test suite both exist but nobody can say which requirements are actually covered…
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
# ai-spec-coverage-mapper ## Overview Coverage tools (per `lcov-analysis` in the qa-test-reporting plugin) report which **lines** are tested. They don't report which **spec sections** are tested. A spec section like "AC-1.4: Already-applied promo shows 'Already applied'" might be: - Covered by a test (good). - Partially covered (the AC says "Already applied"; the test asserts "Already used" - semantic drift). - Not covered. This skill uses an LLM to map tests to spec sections semantically - the mapping human coverage tools cannot produce. ## When to use - The team has a spec doc + a test suite and wants spec-coverage visibility. - Before a release sign-off - to answer "which requirements are actually covered?" - An audit / compliance review needs spec-test traceability. - After AC drift - tests written months ago for ACs that have since changed. Scope is mapping tests that **already exist** and naming the gaps - not authoring tests for the gaps (that is `ai-test-generator`). ## How to use 1. Point the mapper at the spec doc + the test globs, and set the AC-ID extraction pattern. 2. Run the LLM mapper - it reads the spec and the tests and emits, per …
Read the whole file at its exact version.
How to install
mdr add testland/qa/ai-spec-coverage-mapper@sha256:848732d87698c9e8The line at the top of this page pins the label git:20260813.83125c6, 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_7kei3fufkbvcicr5)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 20, 2026 and Aug 13, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260813.83125c6 latest | 2026-08-13 | 83125c6 | 7,556 B | A | view · diff |
| git:20260813.8891296 | 2026-08-13 | 8891296 | 7,554 B | A | view · diff |
| git:20260725.b4ad92d | 2026-07-25 | b4ad92d | 7,527 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 6,932 B | A | view · diff |
| git:20260720.22d020c | 2026-07-20 | 22d020c | 6,998 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 (7556 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
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7kei3fufkbvcicr5 GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/ai-spec-coverage-mapper GET https://markdownregistry.com/api/v1/blob/848732d87698c9e8b53013be0f86841540294f703048ca8647dd08987fdd6596
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.