[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CD9327KDGZSPD2D1RP1DAJ":3,"skill-same:01M7CD9327KDGZSPD2D1RP1DAJ":59},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7CD9327KDGZSPD2D1RP1DAJ","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 \u002Fskill:show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.","Whamp\u002Fpi-extensions","Whamp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1115485?v=4","01M6GV45K5PM2S7V3H0JERGBXN","Will Hampson","01M7CD24WR8BM48CT1X6HWVASD",1,"MIT","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\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 \u002Fskill:show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.\"\ndisable-model-invocation: true\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\nA run is one agent conversation, including its later turns and any summary of it. A pickup, a replacement agent, or a new chat starts a new run. When a run adds to a log that already has rows, its first row has phase `start`, and so does its first row after another run's `start` row. So a run that comes back to a log in a later turn first reads the log's last rows to see whether another run wrote since. A `start` row names the `ts` range of the rows before it that this run did not write, and its evidence names this run, such as its agent id. Use phase `start` for nothing else.\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 **encode-lessons-in-structure** principle 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. Prefer `$PI_SESSION_FILE`. Otherwise use `~\u002F.pi\u002Fagent\u002Fsessions\u002F--\u003Cslug>--\u002F` (`\u003Cslug>` is the workspace path with the leading slash dropped and each \"\u002F\" turned into \"-\"). Stay inside that directory. Do not glob sibling slugs under `~\u002F.pi\u002Fagent\u002Fsessions\u002F`. That reads unrelated private chats. Walk this run's rows against what actually happened. Each stretch of them begins at one of this run's `start` rows, or at the first row if this run created the log, and ends at the next `start` row of another run:\n\n- Check that every row maps to a real decision or action.\n- Check that 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\nCorrect the log, not the story. The audit never edits or removes a row, even an invented one. When a row records neither a real decision nor a real action, or its claim or evidence is wrong, add a row that supersedes it with what actually happened and a pointer that resolves. This audit does not check rows outside this run's stretches. If this run's own work shows one of them is wrong, supersede it like any wrong call.\n\n## Cross-model review of the trail\n\nBefore handing back, spawn a subagent on a different model family from the one that did the work. Self-review 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. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **poteto-mode** skill.\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\nA run is one agent conversation, including its later turns and any summary of it. A pickup, a replacement agent, or a new chat starts a new run. When a run adds to a log that already has rows, its first row has phase `start`, and so does its first row after another run's `start` row. So a run that comes back to a log in a later turn first reads the log's last rows to see whether another run wrote since. A `start` row names the `ts` range of the rows before it that this run did not write, and its evidence names this run, such as its agent id. Use phase `start` for nothing else.\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 **encode-lessons-in-structure** principle 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. Prefer `$PI_SESSION_FILE`. Otherwise use `~\u002F.pi\u002Fagent\u002Fsessions\u002F--\u003Cslug>--\u002F` (`\u003Cslug>` is the workspace path with the leading slash dropped and each \"\u002F\" turned into \"-\"). Stay inside that directory. Do not glob sibling slugs under `~\u002F.pi\u002Fagent\u002Fsessions\u002F`. That reads unrelated private chats. Walk this run's rows against what actually happened. Each stretch of them begins at one of this run's `start` rows, or at the first row if this run created the log, and ends at the next `start` row of another run:\n\n- Check that every row maps to a real decision or action.\n- Check that 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\nCorrect the log, not the story. The audit never edits or removes a row, even an invented one. When a row records neither a real decision nor a real action, or its claim or evidence is wrong, add a row that supersedes it with what actually happened and a pointer that resolves. This audit does not check rows outside this run's stretches. If this run's own work shows one of them is wrong, supersede it like any wrong call.\n\n## Cross-model review of the trail\n\nBefore handing back, spawn a subagent on a different model family from the one that did the work. Self-review 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. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **poteto-mode** skill.\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,"disable-model-invocation":24},true,"master","1d75a8ae76094c017ddb973723b6d6dfa1e0c1c3","packages\u002Fpi-pstack\u002Fskills\u002Fshow-me-your-work",0,"https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions","https:\u002F\u002Fgithub.com\u002FWhamp","https:\u002F\u002Ftwitter.com\u002Fhampsonw","Motorcycles. Dogs. Bonds. Autodidact. http:\u002F\u002Fcourse.fast.ai  alum","2026-10-24 21:56:00",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Whamp\u002Fpi-extensions --skill show-me-your-work",{"tool":40,"command":41},"bunx","bunx skills add Whamp\u002Fpi-extensions --skill show-me-your-work",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Whamp\u002Fpi-extensions --skill show-me-your-work","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fshow-me-your-work\u002FSKILL.md",[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdecision-log-template.tsv","REFERENCE","参考文档",38,"https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fshow-me-your-work\u002Freferences\u002Fdecision-log-template.tsv",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"scripts\u002Flog.sh","SCRIPT","脚本",1377,"https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fshow-me-your-work\u002Fscripts\u002Flog.sh",[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7CD9WQEV4QVY73VGX1TDQ43","sidekick-browser","Use the pinned local AXI launcher for explicit, isolated browser verification in a Sidekick child.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-sidekick\u002Fskills\u002Fsidekick-browser\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CD9PVK6TRMX8DZR5B9QS1W","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CD9KY7SH6P8ENEZG6463DV","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CD9J8RY8ZH1XMHNC1A2423","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7CD9DY3PRH9Z1X7JTZMZRBG","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Fskill:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7CD9B6C9NXWJHEKGYPCFD6M","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]