Individual skill
show-me-your-work
Maintain a compact auditable decision trail during autonomous or high-stakes work. Use when the user will review decisions later.
skills/show-me-your-work/SKILL.md
Source commit 79595c97d47b5400034fb985e67f1a00389a81af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 22
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cursor Repository topic
- pstack Repository topic
- cline Repository topic
- copilot Repository topic
- gemini Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 745 bytes
Read excerpt
# Show Me Your Work
Keep `.potetos/decisions.tsv` with columns:
`timestamp\tunit\tdecision\tevidence\talternatives\tverification\trevision`
Rules:
1. Log decisions that materially change scope, architecture, risk, or the next unit. Do not log every command.
2. Use stable file/commit/test/URL references in evidence fields when available.
3. Record rejected alternatives briefly enough to explain why the chosen path won.
4. Update verification after the evidence exists; never pre-fill success.
5. Keep secrets and private transcript content out of committed logs.