vibe-requirements-validator SKILL.md skillA
vibe-requirements-validator from ash1794/vibe-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ash1794/vibe-engineering/vibe-requirements-validator@git:20260925.f6554ffPins git:20260925.f6554ff in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ash1794/vibe-engineering
- Path
plugins/vibe-engineering/skills/vibe-requirements-validator/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260925.f6554ff, committed Sep 25, 2026
- Size
- 2,255 bytes
- Repository stars
- 165
- License
- MIT
Validates PRD, user stories, or feature requirements against SMART criteria. Use when reviewing requirements to catch vagueness before it causes expensive rework.
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
# vibe-requirements-validator Vague requirements cause expensive rework. Catch them early. ## When to Use This Skill - Reviewing a PRD or feature spec before implementation - Writing acceptance criteria for user stories - When you notice requirements like "make it fast" or "improve UX" - Before estimating effort for a feature ## When NOT to Use This Skill - Internal technical tasks with clear scope - Bug fixes (the bug IS the requirement) - When requirements are already validated and approved ## SMART Criteria Score each requirement 1-5 on: - **S**pecific — Is it clear what exactly needs to be built? (Not "improve performance" but "reduce P95 latency to <200ms") - **M**easurable — Can you objectively verify it's done? (Not "users like it" but "NPS score >40") - **A**chievable — Can it be built with available resources and constraints? - **R**elevant — Does it align with project goals and user needs? - **T**ime-bound — Is there a clear scope boundary? (Not "eventually" but "in v1.0") ## Steps 1. **List all requirements** from the document 2. **Score each** on SMART (1-5 per dimension) 3. **Flag issues**: - Score < 3 on any dimension → needs revision …
Read the whole file at its exact version.
How to install
mdr add ash1794/vibe-engineering/vibe-requirements-validator@sha256:e4b0925468a22549The line at the top of this page pins the label git:20260925.f6554ff, 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_m5iqxl36yewsrllv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 25, 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 (2255 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
ash1794/vibe-engineering · 165 stars · license MIT · pushed 2026-10-07 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_m5iqxl36yewsrllv GET https://markdownregistry.com/api/v1/resolve?ref=ash1794/vibe-engineering/vibe-requirements-validator GET https://markdownregistry.com/api/v1/blob/e4b0925468a22549766ada40a9495c06ab9f80b74fdc6e5adf0f3bc80f0bab30
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.