engineering-playbook SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
engineering-playbook from logandoo/vibeweaver is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add logandoo/vibeweaver/engineering-playbook@git:20260914.0701929Pins git:20260914.0701929 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- logandoo/vibeweaver
- Path
vibeweaver-eval/configs/w6d_placebo/opencode/skills/engineering-playbook/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260914.0701929, committed Sep 14, 2026
- Size
- 39,375 bytes
- Repository stars
- 6
- License
- MIT
A generic senior-engineer operating playbook. MANDATORY for every coding task — plan before you type, test before you claim, debug from evidence, review your own diff.
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
# The Engineering Playbook — How a Senior Engineer Works **This playbook is mandatory.** It is not advice, not a style guide, and not a suggestion you may quietly skip when the task feels small. Every rule below has survived contact with production systems and with the failure modes that make junior work expensive: the fix that broke something else, the test that passed for the wrong reason, the "done" that wasn't. Follow it in order, every task, and say so when you deviate and why. The playbook is organized the way work actually happens: 1. Understand the request 2. Explore before you change 3. Plan the change 4. Implement in small steps 5. Test like you mean it 6. Debug from evidence 7. Verify before you report 8. Review your own diff 9. Communicate like a professional 10. Security hygiene 11. Data and migrations 12. Performance awareness 13. Dependencies and the supply chain 14. Documentation 15. Working with a team 16. Common failure modes and how to catch yourself 17. Checklists and templates 18. Worked examples Read the whole thing once. Then use the checklists at the end as your working memory — they are the compressed form of everything above. --- …
Read the whole file at its exact version.
How to install
mdr add logandoo/vibeweaver/engineering-playbook@sha256:559ddb7d5c4ae214The line at the top of this page pins the label git:20260914.0701929, 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_oamr3xovcbwho6z4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 14, 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 (39375 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
logandoo/vibeweaver · 6 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oamr3xovcbwho6z4 GET https://markdownregistry.com/api/v1/resolve?ref=logandoo/vibeweaver/engineering-playbook GET https://markdownregistry.com/api/v1/blob/559ddb7d5c4ae2146bf372679e7b0d77e61c41d26be246a02b7d264cc04e5432
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.
More from logandoo/vibeweaver
Every file in logandoo/vibeweaver