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:20261005.32edae5, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_mnwyn7mruamdet37
GET https://markdownregistry.com/api/v1/resolve?ref=barbieri/local-openfinance/show-me-your-work
GET https://markdownregistry.com/api/v1/blob/bcff5f7f9fd23f92c12b251f9cd6b947e9485e1055cfacb6fdd9cae0789d7550
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.
barbieri/local-openfinance · .agents/skills/agent-browser/SKILL.md · Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages…
barbieri/local-openfinance · .agents/skills/ai-sdk/SKILL.md · Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK…
barbieri/local-openfinance · .agents/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
barbieri/local-openfinance · .agents/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…
barbieri/local-openfinance · .agents/skills/automate-me/SKILL.md · Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a…
barbieri/local-openfinance · .agents/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…
barbieri/local-openfinance · .agents/skills/cancel-ralph/SKILL.md · Cancel an active Ralph Loop. Use when the user wants to stop, cancel, or abort a running ralph loop.
barbieri/local-openfinance · .agents/skills/cli-for-agents/SKILL.md · Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples…
barbieri/local-openfinance · .agents/skills/code-review/SKILL.md · Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code…
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…
iap/pstack-hermes · 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…
