principle-attack-the-premise SKILL.md skillA
principle-attack-the-premise from creedants/pstack-t3 is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add creedants/pstack-t3/principle-attack-the-premise@git:20261015.883ca2fPins git:20261015.883ca2f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- creedants/pstack-t3
- Path
skills/principle-attack-the-premise/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261015.883ca2f, committed Oct 15, 2026
- First version recorded
- Oct 3, 2026
- Size
- 1,885 bytes
- Repository stars
- 15
- License
- MIT
Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.
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
# Attack the Premise When two or more fixes that share one premise have failed the same gate, suspect the premise, not the fixes. **Why:** Each failed fix is evidence against the belief it assumed. A third fix on the same premise spends effort where the evidence already says the cause is not. **Pattern:** - **Write the premise down.** The premise is the one sentence that every failed fix assumed. - **Test the premise before the next fix.** Find an observation that would come out differently if the premise were false, and make it. Look at how the failures are distributed, not only at how large they are. Make the check rerunnable per [Build the Lever](../principle-build-the-lever/SKILL.md). - **Follow the evidence.** If it contradicts the premise, the cause is elsewhere. Look for what the failures have in common that the premise did not predict. If it confirms the premise, ask the next "why" per [Fix Root Causes](../principle-fix-root-causes/SKILL.md). The earlier fixes may have treated a consequence instead of the cause. …
Read the whole file at its exact version.
How to install
mdr add creedants/pstack-t3/principle-attack-the-premise@sha256:43ca6835f1678ab5The line at the top of this page pins the label git:20261015.883ca2f, 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_ryvmfab4t3hq6i6l)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 3, 2026 and Oct 15, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261015.883ca2f latest | 2026-10-15 | 883ca2f | 1,885 B | A | view · diff |
| git:20261003.a632f62 | 2026-10-03 | a632f62 | 1,910 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 (1885 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
creedants/pstack-t3 · 15 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ryvmfab4t3hq6i6l GET https://markdownregistry.com/api/v1/resolve?ref=creedants/pstack-t3/principle-attack-the-premise GET https://markdownregistry.com/api/v1/blob/43ca6835f1678ab55016ab101e5b47413e9fdfaaedfb77e42dac702b510df9f4
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 creedants/pstack-t3
Every file in creedants/pstack-t3