show-me-your-work

Maintains an append-only TSV decision log with evidence pointers for long-running or unattended work.

2|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/imjasonh/playground --skill show-me-your-work-imjasonh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: show-me-your-work
Source: https://github.com/imjasonh/playground/tree/main/.cursor/skills/show-me-your-work
Command: npx skills add https://github.com/imjasonh/playground --skill show-me-your-work-imjasonh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Long-running, autonomous, or multi-phase work leaves no reviewable trail, so a human who steps away cannot verify what was decided, why, or whether the evidence backs it up. ## Core Features & Use Cases - Structured decision log: One TSV row per decision with timestamp, phase, decision, why, evidence, and result columns, kept single-line and spreadsheet-safe. - Helper script: scripts/log.sh appends well-formed rows, stamps ISO8601 timestamps, writes the header on first use, and neutralizes spreadsheet formula injection in cells. - Audit and cross-model review: End-of-run checks reconcile the log against the actual transcript, and a subagent on a different model family flags weak evidence or risky choices. - Use Case: During an unattended multi-hour refactor, each fork, revert, and verification result is logged with a commit SHA or test output, so a reviewer can later read the TSV top to bottom and trust the outcome. ## Quick Start Ask the agent to start a show-me-your-work decision log for this task and record each major decision with its evidence as the run progresses.

Frequently Asked Questions about show-me-your-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I not log a row in the decision trail?▼

Skip trivial and self-evident actions. Log only decision points and checkpoints: a fork chosen, a unit completed with its verification result, a pivot or revert with its trigger, a blocker surfaced, or a gate fixed.