[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C0X6DFC1PR7989S3R2TF0B":3,"skill-same:01M7C0X6DFC1PR7989S3R2TF0B":57},{"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":6,"updatedAt":30,"install":31,"resources":44},"01M7C0X6DFC1PR7989S3R2TF0B","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.","MateuszRomek\u002Fskills","MateuszRomek","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F46934668?v=4","01M7C0PY1M3ENSCMRTV5QZJQG4","Mateusz Romek","01M7C0PY2JNPFD2DP2HQ0YW7BV",0,"MIT","https:\u002F\u002Fgithub.com\u002FMateuszRomek\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). A reviewer should understand each row without decoding it.\n\nUse the helper so rows stay well-formed: `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 so a reviewer opening the log in a spreadsheet doesn't trigger formula execution. 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. Most work doesn't need a committed trail; the local log still keeps the run honest and can be discarded after.\n\nCommit it only when the work is ambitious enough that a reviewer needs the trail to trust the result: a large cross-language port, a multi-week migration, anything where confidence has to be shown rather than assumed. A committed log renders as a table in the PR.\n\n## Rules\n\n- One row is one decision or checkpoint. If it doesn't fit on one line, the decision isn't crisp yet.\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, so a reviewer can re-run it (the **encode-lessons-in-structure** principle skill).\n\n## Audit the log against the transcript\n\nResolve history and delegation capabilities through [`HOST-COMPATIBILITY.md`](..\u002F..\u002Fagent-mode\u002FHOST-COMPATIBILITY.md).\n\nAt the end of the run, before handing back, check the log told the truth. Use the host's task history or the workspace-scoped transcript supplied by the host. If neither exists, audit against the visible conversation and tool results. Never read unrelated project histories. 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, dispatch the audit-trail review brief as `reviewer` through the active profile. Every resolved worker reads the trail and available task history, then flags what the user should scrutinize. Setup owns independence, roster size, models, and reasoning; this skill adds no fallback. This is a scan for weak evidence and risk, not a redo.\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. Identify each returned review by its configured roster label, then list flags pointing to specific rows or moments. \"No flags\" is valid. If the `reviewer` route is unavailable, say that independent review was unavailable. The self-audit asks if the log told the truth; this asks what the user should still scrutinize even when it did.\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. A row whose evidence doesn't resolve, or whose result is unverified, is the audit catching a gap.\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). A reviewer should understand each row without decoding it.\n\nUse the helper so rows stay well-formed: `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 so a reviewer opening the log in a spreadsheet doesn't trigger formula execution. 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. Most work doesn't need a committed trail; the local log still keeps the run honest and can be discarded after.\n\nCommit it only when the work is ambitious enough that a reviewer needs the trail to trust the result: a large cross-language port, a multi-week migration, anything where confidence has to be shown rather than assumed. A committed log renders as a table in the PR.\n\n## Rules\n\n- One row is one decision or checkpoint. If it doesn't fit on one line, the decision isn't crisp yet.\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, so a reviewer can re-run it (the **encode-lessons-in-structure** principle skill).\n\n## Audit the log against the transcript\n\nResolve history and delegation capabilities through [`HOST-COMPATIBILITY.md`](..\u002F..\u002Fagent-mode\u002FHOST-COMPATIBILITY.md).\n\nAt the end of the run, before handing back, check the log told the truth. Use the host's task history or the workspace-scoped transcript supplied by the host. If neither exists, audit against the visible conversation and tool results. Never read unrelated project histories. 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, dispatch the audit-trail review brief as `reviewer` through the active profile. Every resolved worker reads the trail and available task history, then flags what the user should scrutinize. Setup owns independence, roster size, models, and reasoning; this skill adds no fallback. This is a scan for weak evidence and risk, not a redo.\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. Identify each returned review by its configured roster label, then list flags pointing to specific rows or moments. \"No flags\" is valid. If the `reviewer` route is unavailable, say that independent review was unavailable. The self-audit asks if the log told the truth; this asks what the user should still scrutinize even when it did.\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. A row whose evidence doesn't resolve, or whose result is unverified, is the audit catching a gap.\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","b604251d9d562521f58b39a240910968f6564a89",".agents\u002Fskills\u002Fshow-me-your-work","https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills","https:\u002F\u002Fgithub.com\u002FMateuszRomek","mateuszromek.com","2026-11-13 01:35:46",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add MateuszRomek\u002Fskills --skill show-me-your-work",{"tool":37,"command":38},"bunx","bunx skills add MateuszRomek\u002Fskills --skill show-me-your-work",{"tool":40,"command":41},"pnpm","pnpm dlx skills add MateuszRomek\u002Fskills --skill show-me-your-work","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshow-me-your-work\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fdecision-log-template.tsv","REFERENCE","参考文档",38,"https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshow-me-your-work\u002Freferences\u002Fdecision-log-template.tsv",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"scripts\u002Flog.sh","SCRIPT","脚本",1377,"https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshow-me-your-work\u002Fscripts\u002Flog.sh",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7C0YZ4R20ZCCZVCSMETEX5S","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7C0YVJJ1SJD9A5Z9RVGZCHN","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7C0YR2G4WDJ6C0HE05G6MRD","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Searches available evidence sources and returns a cited account of decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7C0YND1NS2EFSS21JGC7EFX","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7C0YH23EQCKD3R92V3BCS91","unslop","Cut AI tells from prose. Use before writing or revising any reply, doc, PR description, commit message, or skill text another reader will see, or for \u002Funslop.","https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7C0YF7BZVR2VXKS425SFMY0","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002FMateuszRomek\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[]]