principles SKILL.md skillA
principles from umararshad4/honey-stack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add umararshad4/honey-stack/principles@git:20261017.c52b424Pins git:20261017.c52b424 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- umararshad4/honey-stack
- Path
skills/principles/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261017.c52b424, committed Oct 17, 2026
- First version recorded
- Oct 17, 2026
- Size
- 4,658 bytes
- Repository stars
- 4
- License
- MIT
Engineering principles index; read the leaf file before citing a principle.
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
# Principles
Each row is one engineering principle. The gist is a pointer, not the principle: the leaf file holds the rule, its limits and its tells.
Cite a principle only if you read its file this session. A citation from the gist alone borrows the name without the content, and the leaf's caveats ("skip it when…", "distinct from…") are usually what decides the case.
## Use
1. Match the situation to a row by its gist. Done when: you have one to three candidate rows, or none fits.
2. Read each candidate's file in `references/`. Done when: every principle you will cite has been read this session.
3. Apply it, and when you cite it, name the file and the line that decided the call, e.g. "per `references/fix-root-causes.md`: a guard is a fix only when the state it handles is legitimate".
## Index
| Principle | Gist | File |
|---|---|---|
| Attack the premise | Two fixes on one premise failed the same gate: test the premise before a third fix | `references/attack-the-premise.md` |
| Boundary discipline | Validate at system edges (CLI, config, network, APIs); trust internal types; keep logic pure | `references/boundary-discipline.md` |
…Read the whole file at its exact version.
How to install
mdr add umararshad4/honey-stack/principles@sha256:c27b3ee6b76b6ad9The line at the top of this page pins the label git:20261017.c52b424, 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_5nxaa2sskprofz2t)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 17, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.c52b424 latest | 2026-10-17 | c52b424 | 4,658 B | A | view · diff |
| git:20261017.6c6369a | 2026-10-17 | 6c6369a | 4,633 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 (4658 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
umararshad4/honey-stack · 4 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5nxaa2sskprofz2t GET https://markdownregistry.com/api/v1/resolve?ref=umararshad4/honey-stack/principles GET https://markdownregistry.com/api/v1/blob/c27b3ee6b76b6ad99802f9b296647b2e4e40d8fe1f4d81b097c0c3bb39d2691e
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 umararshad4/honey-stack
Every file in umararshad4/honey-stack