tech-spec:review SKILL.md skillA
tech-spec:review from bendrucker/claude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bendrucker/claude/tech-spec:review@git:20260827.12933ddPins git:20260827.12933dd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bendrucker/claude
- Path
plugins/tech-spec/skills/review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260827.12933dd, committed Aug 27, 2026
- First version recorded
- Jan 30, 2026
- Size
- 1,842 bytes
- Repository stars
- 18
- License
- MIT
Review an existing technical specification for gaps, risks, and missing considerations.
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
# Review Technical Specification ## Inputs Ask the user to provide: - **Tech spec**: Path to the specification file, or pasted content - **Focus areas** (optional): Specific concerns to prioritize (e.g., "security", "API design") - **Repositories** (optional): Codebases to consult when verifying spec claims ## Code Exploration When repositories are provided, consult code to verify: - Proposed patterns match existing conventions - Referenced files and structures exist - Implementation assumptions are accurate Explore on demand during review, not upfront. ## Review Process ### Identify Expert Perspectives Select relevant personas from [references/experts.md](references/experts.md): - Always include standard personas (security, API, database, etc.) - Add dynamic personas based on spec content (integrations, analytics, etc.) - User-specified focus areas get priority ### Conduct Review For each persona: 1. Scan the spec for areas within their expertise 2. Identify findings: gaps, risks, unclear decisions, missing considerations 3. Rate severity: blocking, important, or nice-to-have ### Present Findings Group related findings into batches and present via `AskUserQuestion`: …
Read the whole file at its exact version.
How to install
mdr add bendrucker/claude/tech-spec:review@sha256:3aee90276fa905bdThe line at the top of this page pins the label git:20260827.12933dd, 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_gegekomouopcvk2m)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jan 30, 2026 and Aug 27, 2026, about one every 52 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260827.12933dd latest | 2026-08-27 | 12933dd | 1,842 B | A | view · diff |
| git:20260615.1ec44ee | 2026-06-15 | 1ec44ee | 1,992 B | A | view · diff |
| git:20260605.8751e32 | 2026-06-05 | 8751e32 | 2,017 B | A | view · diff |
| git:20260208.23371e3 | 2026-02-08 | 23371e3 | 1,986 B | A | view · diff |
| git:20260130.dcbe199 | 2026-01-30 | dcbe199 | 1,976 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 (1842 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
bendrucker/claude · 18 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gegekomouopcvk2m GET https://markdownregistry.com/api/v1/resolve?ref=bendrucker/claude/tech-spec:review GET https://markdownregistry.com/api/v1/blob/3aee90276fa905bd8b89de2f071c7d7ee39fc4e36dcc378f331b724bd761a71b
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.