[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CYVWWG5H1JSZ4DET4N2JDN":3,"skill-same:01M7CYVWWG5H1JSZ4DET4N2JDN":60},{"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":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7CYVWWG5H1JSZ4DET4N2JDN","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 $show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.","justinramos101\u002Fxstack","justinramos101","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F195591384?v=4","01M7CYH6VP70MGKFPYNHH83HTK","Justin Ramos","01M7CYH6WESBC787R5AKN24BY2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\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 $show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.\"\n---\n\n# Show me your work\n\nRead [Codex runtime](..\u002Fpoteto-mode\u002Freferences\u002Fhost-runtime.md) before using Codex tools or delegating. Resolve configured roles there even when this skill is invoked directly.\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 `.agents\u002Fstate\u002Fxstack\u002F\u003Crun-id>\u002Fdecisions.tsv` unless the user names another path. Use a unique run ID and leave the file 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 using the exact active-session path or history API described in Codex runtime. Don't glob across unrelated project transcript directories. 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, request an independent review on a different configured model family when available. Follow Codex runtime when model overrides or delegation are unavailable, and report the reduced independence. 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 effort for the job, and fast mode only when the session exposes it, 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\nRead [Codex runtime](..\u002Fpoteto-mode\u002Freferences\u002Fhost-runtime.md) before using Codex tools or delegating. Resolve configured roles there even when this skill is invoked directly.\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 `.agents\u002Fstate\u002Fxstack\u002F\u003Crun-id>\u002Fdecisions.tsv` unless the user names another path. Use a unique run ID and leave the file 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 using the exact active-session path or history API described in Codex runtime. Don't glob across unrelated project transcript directories. 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, request an independent review on a different configured model family when available. Follow Codex runtime when model overrides or delegation are unavailable, and report the reduced independence. 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 effort for the job, and fast mode only when the session exposes it, 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},"main","478b73862a26db66dde6e035f6bd31a8ec2b21cc","src\u002Fskills\u002Fshow-me-your-work","https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack","https:\u002F\u002Fgithub.com\u002Fjustinramos101","2026-11-14 14:29:49",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add justinramos101\u002Fxstack --skill show-me-your-work",{"tool":36,"command":37},"bunx","bunx skills add justinramos101\u002Fxstack --skill show-me-your-work",{"tool":39,"command":40},"pnpm","pnpm dlx skills add justinramos101\u002Fxstack --skill show-me-your-work","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshow-me-your-work\u002FSKILL.md",true,[44,50,54],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshow-me-your-work\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdecision-log-template.tsv",38,"https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshow-me-your-work\u002Freferences\u002Fdecision-log-template.tsv",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"scripts\u002Flog.sh","SCRIPT","脚本",1377,"https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshow-me-your-work\u002Fscripts\u002Flog.sh",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7CYWQ45E30TZWMFA75DPVNS","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\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7CYWK9SS3DHJXWC1TH3407S","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7CYWHGXT78RV5VHDNAQKMNV","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7CYWDSDMWRA3CM3NSP385V3","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CYWAWZH7TPMHXY11WTDK0K","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\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7CYW6PNDEBKV287YB6C54TX","tdd","Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","https:\u002F\u002Fgithub.com\u002Fjustinramos101\u002Fxstack\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]