Vibe BuildSAFE
Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
Overview
Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
844e6869035fOBSERVED · 2026-10-08What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: vibe-build description: "Implement a new-project slice through the relevant checks and working user journey." allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion --- # Build a new-project slice Establish the requested outcome and acceptance criteria from the user's brief and relevant project decisions. Read applicable repository instructions and only the documents needed for this slice. An absent or stale MEMORY.md does not require rebuilding the whole planning workflow. Implement the intended behavior using the chosen stack. Preserve unrelated work and make a recovery checkpoint when the change warrants it. Add accounts, databases, infrastructure, paid services, and AI only when requirements justify them. Continue until the requested slice works, not merely until files exist. Use the project's affected checks and exercise the relevant user journey when runtime access permits it. Fix failures caused by the change, distinguish pre-existing failures, and reuse results that remain valid. A setup validator or passing build alone is not evidence of interactive behavior. Update project progress when the repository maintains it. Report the outcome, actual checks, unverified behavior, and any concrete blocker or recovery note. External sends, production changes, store submission, and deployment remain subject to authorization for their specific effect and target.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
844e6869035ffull audit observations/trust-audit/skill/khazp__vibe-build.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 844e6869035f | SAFE | B | 89 | first audit |
Questions
What does the Vibe Build skill do?
Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
Is Vibe Build safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Vibe Build access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (844e6869035f), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.