[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DE8R4SMAP8MYHKSMBFHSA7":3,"skill-same:01M7DE8R4SMAP8MYHKSMBFHSA7":61},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7DE8R4SMAP8MYHKSMBFHSA7","show-me-your-work",null,"Use when the user invokes `show-me-your-work`, for long-running, autonomous, or multi-phase work, or for work a human will review after stepping away.","pascalandy\u002Fskills","pascalandy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6694151?v=4","01M7DDRR1T4AMR6J3FV6RHHV5M","Pascal Andy","01M7DDRR2B04BJ8S7QZYZV1WFK",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fshow-me-your-work\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"show-me-your-work\"\ndescription: \"Use when the user invokes `show-me-your-work`, for long-running, autonomous, or multi-phase work, or for work a human will review after stepping away.\"\nkind: \"dev\"\nrole: \"helper\"\n---\n\n# Show me your work\n\nRead [the agent runtime contract](..\u002Fpoteto-mode\u002Freferences\u002Fagent-runtime.md) before using runtime tools, loading related skills, or delegating. Use only capabilities and model IDs verified in this session.\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. This is illustration only. Don't copy these rows into a real log.\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. It answers in one JSON line, `{\"ok\":true,\"changes\":[[\"append\",\"\u003Cabsolute logfile>\"]]}`; on a failure it exits non-zero, and the last stderr line is `{\"ok\":false,\"errors\":[…]}`. 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 a `mktemp -d` folder outside the checkout, or at a path the repository ignores, so checks that refuse untracked files still run.\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- One row is one decision or checkpoint.\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 (poteto-mode's **Encode Lessons in Structure** principle).\n\n## Audit the log against the transcript\n\nAt the end of the run, before handing back, check the log told the truth. Discover this run's authorized history or export using the runtime contract. If it is unavailable, audit against visible tool evidence and artifacts and report the missing transcript as a coverage gap. 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## Independent review of the trail\n\nBefore handing back, spawn an independent agent with the `Reviewer` role. If no separate context is available, mark the independent review incomplete. 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.\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\nRead [the agent runtime contract](..\u002Fpoteto-mode\u002Freferences\u002Fagent-runtime.md) before using runtime tools, loading related skills, or delegating. Use only capabilities and model IDs verified in this session.\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. This is illustration only. Don't copy these rows into a real log.\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. It answers in one JSON line, `{\"ok\":true,\"changes\":[[\"append\",\"\u003Cabsolute logfile>\"]]}`; on a failure it exits non-zero, and the last stderr line is `{\"ok\":false,\"errors\":[…]}`. 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 a `mktemp -d` folder outside the checkout, or at a path the repository ignores, so checks that refuse untracked files still run.\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- One row is one decision or checkpoint.\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 (poteto-mode's **Encode Lessons in Structure** principle).\n\n## Audit the log against the transcript\n\nAt the end of the run, before handing back, check the log told the truth. Discover this run's authorized history or export using the runtime contract. If it is unavailable, audit against visible tool evidence and artifacts and report the missing transcript as a coverage gap. 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## Independent review of the trail\n\nBefore handing back, spawn an independent agent with the `Reviewer` role. If no separate context is available, mark the independent review incomplete. 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.\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",{"kind":24,"name":5,"role":25,"description":7},"dev","helper","main","c2b929d1a54305e77aad0296872e90e08d68a637","skills\u002Fshow-me-your-work",1,"https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills","https:\u002F\u002Fgithub.com\u002Fpascalandy","https:\u002F\u002Fblog.pascalandy.com","The question: how can I build the default one-stop place where entrepreneurs can start their mobile-first websites and blog? Psst psst… play-with-ghost.com","2026-11-15 03:34:59",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add pascalandy\u002Fskills --skill show-me-your-work",{"tool":41,"command":42},"bunx","bunx skills add pascalandy\u002Fskills --skill show-me-your-work",{"tool":44,"command":45},"pnpm","pnpm dlx skills add pascalandy\u002Fskills --skill show-me-your-work","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fshow-me-your-work\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fdecision-log-template.tsv","REFERENCE","参考文档",38,"https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fshow-me-your-work\u002Freferences\u002Fdecision-log-template.tsv",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Flog.sh","SCRIPT","脚本",2991,"https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fshow-me-your-work\u002Fscripts\u002Flog.sh",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DEA67FREYEGQJYTWD9D0GB","writing-great-skills","Use when creating, modifying, evaluating a skill.","https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DEA3ZN566HSV6YJ8KPE824","writing-for-agents","Use when creating, editing, or reviewing a skill, AGENTS.md, CLAUDE.md, or another document agents read.","https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DEA0FRE0FEYV9XS0YTTBPJ","why","Use for questions about design rationale, the history of regressions or incidents, or the evidence behind thresholds and tradeoffs. Use `how` for runtime behavior. Do not use for plain commit or date lookups.","https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DE9XVZASJS9PC1A5BVMVHG","verify-video-archive","Use when validating the macOS or Linux archive workflow reached by `just convert-video`, including real media, prerequisites, terminal progress, source safety, locking, and recovery.","https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify-video-archive\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7DE9VTG6ZEQH1M10J66T8MR","verify-transcript","Use when validating transcript CLI behavior, locating its verification features, or running the paid YouTube end-to-end check.","https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify-transcript\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7DE9RWQ6WNVG455HQFHVNFR","verify-skills","Use when verifying `just compile-skills`, `just remote-skills`, `just install-skills`, or `just skills-discover` in the skills repository, such as after changing their scripts or adding, renaming, or moving a skill.","https:\u002F\u002Fgithub.com\u002Fpascalandy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify-skills\u002FSKILL.md",[],[]]