Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
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
# Show me your work
Keep one canonical log.
## The format
A single TSV file, one row per decision. Cells stay single-line. Evidence is a pointer, not prose.
Copy `references/decision-log-template.tsv` (the header row) to start a clean log. Columns:
- **ts.** ISO8601 timestamp.
- **phase.** The phase or workstream.
- **decision.** What was chosen or done, one line.
- **why.** The reason in plain words. If a principle drove it, say it plainly, not as a jargon tag.
- **evidence.** A link or path that proves it: commit SHA, PR number, `file:line`, or an artifact, trace, or screenshot path. Never a paragraph.
- **result.** The outcome or predicate state: `tests green`, `reverted`, `pixel-diff 0`, `INCONCLUSIVE`, `open`.
An example, plain-spoken so a reviewer reads it at a glance.
```
ts phase decision why evidence result
2026-05-24T09:02:00Z frame counted the work first, about 100 components and roughly 75 hours wanted to know the size before starting a long run commit 3a9f1c2 found 5 things to sort out before starting
…
The line at the top of this page pins the label git:20261031.336cc57, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6357 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
GitHub
iap/pstack-hermes · 32 stars · license a license file GitHub does not identify · pushed 2026-11-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_l5daa6cio3vm7irr
GET https://markdownregistry.com/api/v1/resolve?ref=iap/pstack-hermes/show-me-your-work
GET https://markdownregistry.com/api/v1/blob/f4b11f1bfd1100f5f02567a3f6d002ffdfa597014db405ade23b33e8f9dc65d7
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.
iap/pstack-hermes · skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
iap/pstack-hermes · skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
iap/pstack-hermes · skills/automate-me/SKILL.md · Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a…
iap/pstack-hermes · skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
iap/pstack-hermes · skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
iap/pstack-hermes · skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
iap/pstack-hermes · skills/hermesbot/SKILL.md · Use when building a control surface (page, dashboard, buttons) that wakes a hermes bot over a webhook subscription…
iap/pstack-hermes · skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
iap/pstack-hermes · skills/interrogate/SKILL.md · Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find…
cursor/plugins · pstack/skills/show-me-your-work/SKILL.md · Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why…
cursor/plugins · harness/pstack/claude-code/skills/show-me-your-work/SKILL.md · Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why…
nightly-labs/openbot · marketplace/production-catalog/bundles/pstack/skills/show-me-your-work/SKILL.md · Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why…
michael-denyer/pstack-claude · plugins/pstack/skills/show-me-your-work/SKILL.md · Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why…
backnotprop/pstack · skills/show-me-your-work/SKILL.md · Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why…
timharris707/skills · plugins/clickai-codex/skills/run/show-me-your-work/SKILL.md · For autonomous multi-phase or unattended work, a reviewer needing an evidence trail, or an explicit…
timharris707/skills · skills/run/show-me-your-work/SKILL.md · Keep a reviewable decision trail for long-running or unattended work: one append-only TSV log, one row per decision…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/code-intelligence/show-me-your-work/SKILL.md · Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why…