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
In Claude Code, read [the Claude Code adapter](../../docs/harness/claude-code.md) once per session before you follow this skill. It maps the Cursor names in pstack skills to Claude Code.
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
…
The line at the top of this page pins the label git:20261016.182f2ce, 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_yr5q4z44njwddxmx
GET https://markdownregistry.com/api/v1/resolve?ref=cursor/plugins/show-me-your-work
GET https://markdownregistry.com/api/v1/blob/4936325425064cbbbd1e82a7813cef5593ed8a273671d43ac5b1360de93f880a
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.
cursor/plugins · advisor/skills/advisor/SKILL.md · Advisor mode. Consult a stronger (or different) model at key checkpoints: before major decisions, when stuck on an…
cursor/plugins · agent-compatibility/skills/check-agent-compatibility/SKILL.md · Run the full repository compatibility pass: scanner score, startup path, validation loop, and docs reliability.
cursor/plugins · cli-for-agent/skills/cli-for-agents/SKILL.md · Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples…
cursor/plugins · create-plugin/skills/create-plugin-scaffold/SKILL.md · Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when…
cursor/plugins · create-plugin/skills/review-plugin-submission/SKILL.md · Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths…
cursor/plugins · cursor-sdk/skills/cursor-sdk/SKILL.md · Guide users building apps, scripts, CI pipelines, or automations on top of the Cursor TypeScript SDK (`@cursor/sdk`)…
cursor/plugins · cursor-team-kit/skills/control-cli/SKILL.md · Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use…
cursor/plugins · cursor-team-kit/skills/control-ui/SKILL.md · Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI…
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…
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…
creedants/pstack-t3 · t3/overrides/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…
creedants/pstack-t3 · 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…
