[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ADM7KAXYRV132GSWCW9033":3,"skill-same:01M7ADM7KAXYRV132GSWCW9033":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ADM7KAXYRV132GSWCW9033","show-me-your-work",null,"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 \u002Fshow-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.","stepankuzmin\u002Fskills","stepankuzmin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F533564?v=4","01M7ADH01MGRSMC0YNW589Q6CE","Stepan Kuzmin","01M7ADH02CTNTX4NFP4S5WVYT9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshow-me-your-work\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: show-me-your-work\ndescription: \"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 \u002Fshow-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.\"\n---\n\n# Show me your work\n\nKeep one canonical log.\n\n## The format\n\nA single TSV file, one row per decision. Cells stay single-line. Evidence is a pointer, not prose.\n\nCopy `references\u002Fdecision-log-template.tsv` (the header row) to start a clean log. Columns:\n\n- **ts.** ISO8601 timestamp.\n- **phase.** The phase or workstream.\n- **decision.** What was chosen or done, one line.\n- **why.** The reason in plain words. If a principle drove it, say it plainly, not as a jargon tag.\n- **evidence.** A link or path that proves it: commit SHA, PR number, `file:line`, or an artifact, trace, or screenshot path. Never a paragraph.\n- **result.** The outcome or predicate state: `tests green`, `reverted`, `pixel-diff 0`, `INCONCLUSIVE`, `open`.\n\nAn example, plain-spoken so a reviewer reads it at a glance.\n\n```\nts\tphase\tdecision\twhy\tevidence\tresult\n2026-05-24T09:02:00Z\tframe\tcounted the work first, about 100 components and roughly 75 hours\twanted to know the size before starting a long run\tcommit 3a9f1c2\tfound 5 things to sort out before starting\n2026-05-24T09:40:00Z\tharness\ttook screenshots of the old version before changing anything\tso we can compare old against new and catch any visual change\tscripts\u002Fsnapshot.sh, baseline\u002F\tsaved 120 reference screenshots\n2026-05-24T11:15:00Z\twidget\tmoved the widget styles over without changing how it looks\tkeep the change small and the result identical\tcommit 7c21e0a, pixel-diff 0\tlooks identical, tests pass\n2026-05-24T12:30:00Z\twidget\tthrew out a helper's work because its screenshots were blank\tchecked the real files instead of trusting its summary\tworktree reset\treverted, tightened the instructions for next time\n```\n\n## Logging a row\n\nWrite each entry the way you'd tell a teammate what you did. Plain words, concrete actions, no AI speak or abstract jargon (the **unslop** skill applies to log text too).\n\nUse the helper `scripts\u002Flog.sh \u003Clogfile> \u003Cphase> \u003Cdecision> \u003Cwhy> \u003Cevidence> \u003Cresult>`. It stamps `ts`, writes the header on first use, strips stray tabs\u002Fnewlines, and prefixes any cell starting with `=`, `+`, `-`, or `@` with a single quote. A bare `printf` appending a row works too, but mind those same bytes if cells come from generated or user-supplied text.\n\nLog decision points and checkpoints, not every action: a fork chosen, a unit completed with its verification result, a pivot or revert with its trigger, a blocker surfaced, a gate fixed. For loop runs, one row per iteration. Skip the trivial and self-evident.\n\n## Where it lives\n\nBy default the log is a working artifact, not committed. Keep it at `decisions.tsv` in the work dir, or `.audit\u002F\u003Ctask-slug>.tsv` when several efforts run at once, and leave it out of git.\n\nCommit it only when the work is ambitious enough that a reviewer needs the trail to trust the result.\n\n## Rules\n\n- Append-only. A wrong call gets a new row that supersedes it. Never edit or delete history.\n- Prefer evidence produced by committed scripts over hand-made one-offs (the **principle-encode-lessons-in-structure** skill).\n\n## Audit the log against the transcript\n\nAt the end of the run, before handing back, check the log told the truth. Read this run's transcript. Claude Code keeps each session at `${CLAUDE_CONFIG_DIR:-~\u002F.claude}\u002Fprojects\u002F\u003Cslug>\u002F\u003Csession-id>.jsonl`, where `\u003Cslug>` is the workspace path with every `\u002F` turned into `-` (so `\u002FUsers\u002Fyou\u002Fproj` becomes `-Users-you-proj`), and its subagents under `\u003Csession-id>\u002Fsubagents\u002F`. Codex keeps sessions at `~\u002F.codex\u002Fsessions\u002F\u003Cyyyy>\u002F\u003Cmm>\u002F\u003Cdd>\u002Frollout-*.jsonl`. Every line is one event. Read only the current workspace's directory. Globbing across projects reads unrelated private chats. Walk the log against what actually happened:\n\n- Every row maps to a real action. Cut invented or aspirational entries.\n- Each row's evidence resolves and shows what the row claims.\n- A fork, pivot, or abandoned approach that shaped the work but isn't logged is a gap. Add it.\n- Drop padding.\n\nFix the log, not the story. If the work diverged from what a row claims, the row is wrong.\n\n## Cross-model review of the trail\n\nBefore handing back, spawn a reviewer on a different model family from the one that did the work, such as `codex exec` from Claude Code. If none is available, spawn a fresh subagent that saw none of the work. Self-review in the same context is not a substitute. The subagent reads the audit trail and the run's transcript, then flags what the user should pay attention to. Not a redo of the work, a scan for what's suboptimal or risky.\n\n- Decisions logged with weak or absent evidence.\n- Verification steps skipped or claimed without proof in the transcript.\n- Choices that look risky in hindsight (premature, scope-creeping, papering over a symptom).\n- Gaps the user would otherwise miss on a casual skim.\n\nEvery reply for a run that produced a trail ends with an \"Attention\" section. Lead with the reviewer's model on its own line (`reviewed by \u003Cmodel>`), then list each flag pointing to specific rows or moments. \"No flags\" is a valid value. The model name is not.\n\n## Reviewing the trail\n\nRead top to bottom, follow the evidence pointers, spot-check. GitHub renders a committed TSV as a table. `column -s$'\\t' -t decisions.tsv` renders it in a terminal.\n\n## Composing this skill\n\nOther skills route their audit trail here instead of inventing one. Reference it by name and let it own the format. Don't restate the columns.\n","# Show me your work\n\nKeep one canonical log.\n\n## The format\n\nA single TSV file, one row per decision. Cells stay single-line. Evidence is a pointer, not prose.\n\nCopy `references\u002Fdecision-log-template.tsv` (the header row) to start a clean log. Columns:\n\n- **ts.** ISO8601 timestamp.\n- **phase.** The phase or workstream.\n- **decision.** What was chosen or done, one line.\n- **why.** The reason in plain words. If a principle drove it, say it plainly, not as a jargon tag.\n- **evidence.** A link or path that proves it: commit SHA, PR number, `file:line`, or an artifact, trace, or screenshot path. Never a paragraph.\n- **result.** The outcome or predicate state: `tests green`, `reverted`, `pixel-diff 0`, `INCONCLUSIVE`, `open`.\n\nAn example, plain-spoken so a reviewer reads it at a glance.\n\n```\nts\tphase\tdecision\twhy\tevidence\tresult\n2026-05-24T09:02:00Z\tframe\tcounted the work first, about 100 components and roughly 75 hours\twanted to know the size before starting a long run\tcommit 3a9f1c2\tfound 5 things to sort out before starting\n2026-05-24T09:40:00Z\tharness\ttook screenshots of the old version before changing anything\tso we can compare old against new and catch any visual change\tscripts\u002Fsnapshot.sh, baseline\u002F\tsaved 120 reference screenshots\n2026-05-24T11:15:00Z\twidget\tmoved the widget styles over without changing how it looks\tkeep the change small and the result identical\tcommit 7c21e0a, pixel-diff 0\tlooks identical, tests pass\n2026-05-24T12:30:00Z\twidget\tthrew out a helper's work because its screenshots were blank\tchecked the real files instead of trusting its summary\tworktree reset\treverted, tightened the instructions for next time\n```\n\n## Logging a row\n\nWrite each entry the way you'd tell a teammate what you did. Plain words, concrete actions, no AI speak or abstract jargon (the **unslop** skill applies to log text too).\n\nUse the helper `scripts\u002Flog.sh \u003Clogfile> \u003Cphase> \u003Cdecision> \u003Cwhy> \u003Cevidence> \u003Cresult>`. It stamps `ts`, writes the header on first use, strips stray tabs\u002Fnewlines, and prefixes any cell starting with `=`, `+`, `-`, or `@` with a single quote. A bare `printf` appending a row works too, but mind those same bytes if cells come from generated or user-supplied text.\n\nLog decision points and checkpoints, not every action: a fork chosen, a unit completed with its verification result, a pivot or revert with its trigger, a blocker surfaced, a gate fixed. For loop runs, one row per iteration. Skip the trivial and self-evident.\n\n## Where it lives\n\nBy default the log is a working artifact, not committed. Keep it at `decisions.tsv` in the work dir, or `.audit\u002F\u003Ctask-slug>.tsv` when several efforts run at once, and leave it out of git.\n\nCommit it only when the work is ambitious enough that a reviewer needs the trail to trust the result.\n\n## Rules\n\n- Append-only. A wrong call gets a new row that supersedes it. Never edit or delete history.\n- Prefer evidence produced by committed scripts over hand-made one-offs (the **principle-encode-lessons-in-structure** skill).\n\n## Audit the log against the transcript\n\nAt the end of the run, before handing back, check the log told the truth. Read this run's transcript. Claude Code keeps each session at `${CLAUDE_CONFIG_DIR:-~\u002F.claude}\u002Fprojects\u002F\u003Cslug>\u002F\u003Csession-id>.jsonl`, where `\u003Cslug>` is the workspace path with every `\u002F` turned into `-` (so `\u002FUsers\u002Fyou\u002Fproj` becomes `-Users-you-proj`), and its subagents under `\u003Csession-id>\u002Fsubagents\u002F`. Codex keeps sessions at `~\u002F.codex\u002Fsessions\u002F\u003Cyyyy>\u002F\u003Cmm>\u002F\u003Cdd>\u002Frollout-*.jsonl`. Every line is one event. Read only the current workspace's directory. Globbing across projects reads unrelated private chats. Walk the log against what actually happened:\n\n- Every row maps to a real action. Cut invented or aspirational entries.\n- Each row's evidence resolves and shows what the row claims.\n- A fork, pivot, or abandoned approach that shaped the work but isn't logged is a gap. Add it.\n- Drop padding.\n\nFix the log, not the story. If the work diverged from what a row claims, the row is wrong.\n\n## Cross-model review of the trail\n\nBefore handing back, spawn a reviewer on a different model family from the one that did the work, such as `codex exec` from Claude Code. If none is available, spawn a fresh subagent that saw none of the work. Self-review in the same context is not a substitute. The subagent reads the audit trail and the run's transcript, then flags what the user should pay attention to. Not a redo of the work, a scan for what's suboptimal or risky.\n\n- Decisions logged with weak or absent evidence.\n- Verification steps skipped or claimed without proof in the transcript.\n- Choices that look risky in hindsight (premature, scope-creeping, papering over a symptom).\n- Gaps the user would otherwise miss on a casual skim.\n\nEvery reply for a run that produced a trail ends with an \"Attention\" section. Lead with the reviewer's model on its own line (`reviewed by \u003Cmodel>`), then list each flag pointing to specific rows or moments. \"No flags\" is a valid value. The model name is not.\n\n## Reviewing the trail\n\nRead top to bottom, follow the evidence pointers, spot-check. GitHub renders a committed TSV as a table. `column -s$'\\t' -t decisions.tsv` renders it in a terminal.\n\n## Composing this skill\n\nOther skills route their audit trail here instead of inventing one. Reference it by name and let it own the format. Don't restate the columns.\n",{"name":5,"description":7},"main","7c3fa2c0275bcee7c1633a3ab6b0374e1a059b6e",".agents\u002Fskills\u002Fshow-me-your-work","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills","https:\u002F\u002Fgithub.com\u002Fstepankuzmin","https:\u002F\u002Fstepankuzmin.com\u002F","Software Engineer at @Mapbox","2026-10-01 17:36:10",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add stepankuzmin\u002Fskills --skill show-me-your-work",{"tool":38,"command":39},"bunx","bunx skills add stepankuzmin\u002Fskills --skill show-me-your-work",{"tool":41,"command":42},"pnpm","pnpm dlx skills add stepankuzmin\u002Fskills --skill show-me-your-work","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshow-me-your-work\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdecision-log-template.tsv","REFERENCE","参考文档",38,"https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshow-me-your-work\u002Freferences\u002Fdecision-log-template.tsv",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Flog.sh","SCRIPT","脚本",1377,"https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshow-me-your-work\u002Fscripts\u002Flog.sh",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7ADN40WWNARJK5XDNNY59MR","vendor-skill","Adapt an external skill into this marketplace, or review upstream changes to one already adapted. Use when asked to vendor, import, adapt, mirror, or update a skill from skills.sh, `npx skills add`, or any external GitHub skills repo, especially to work around Claude Code Web only allowing one marketplace per GitHub repo name.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvendor-skill\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7ADMYB3AZ7CPMS9V6P48H61","why","Use when the user asks to investigate why code is built the way it is: 'why does X work this way', 'why we picked Y', design rationale, regressions, or postmortems. Not for explaining a single error or a quick question. Queries each available evidence source (git and PRs, issues, docs, team chat) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7ADMWR9QP2Q2G4D5ZEKPV8W","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7ADMNW2S09DQBJ34JP7BBY7","uncomplect","Pressure-test a stateful system or replacement design through Rich Hickey's simplicity and complection, Greg Young's deletability, Ousterhout's deep modules, DDD boundaries, typed effects, and explicit lifecycle modeling. Use when the user asks \"what would Rich Hickey do\", \"optimize for deletion\", \"make this simpler\", \"define this error out of existence\", \"review this state machine\", \"design it twice\", or wants to replace a working prototype without preserving its accidental architecture.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Funcomplect\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7ADMJMJ8M5PGK63N0GQ5B59","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7ADMER5KTJPY8J7M8MTP6WA","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fstepankuzmin\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[]]