[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DT3VTB8NEKEVDPR7JS17JM":3,"skill-same:01M6DT3VTB8NEKEVDPR7JS17JM":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":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M6DT3VTB8NEKEVDPR7JS17JM","retro",null,"Conduct a retrospective on a coding session.","nicolasLuduena\u002Fskills","nicolasLuduena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47897388?v=4","01M6DT2J6QHQB14SH18EFBKT6D","Nicolás Ludueña","01M6DT2JBREQBVQYEQBR2AC31G",0,"MIT","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fretro\u002FSKILL.md",[],[5,19,20,21,22,23],"retrospective","coding","session","true","conduct","2026-11-10 10:12:30",false,"---\nname: retro\ndescription: \"Conduct a retrospective on a coding session.\"\ndisable-model-invocation: true\n---\n\nThe user has asked for a **retrospective**. You are suggesting improvements to the coding agent's **environment** to improve future runs.\n\n## Steps\n\n1. Call the Skill tool with `writing-for-agents` for the writing style guide.\n\n2. Read the primary sources for the session the user specifies. This may mean searching through session logs on this machine. If the user doesn't specify a session, default to the current one.\n\n3. Look for candidates for improvement in these categories.\n\n- **Navigation**: how easy was it for the agent to find the right files? Are there hidden dependencies between files? Would a **navigation pointer** make it easier? _Use when_ the session took a long time to find a piece of information.\n- **Automated checks**: are there automated checks that could catch errors the agent made? Linting, typing, tests, filesystem linters? Read the repo's own check command first (its `package.json`\u002Fbuild-tool `lint`\u002F`check` scripts, its CI workflow), so a check that already exists but sits unwired or silently broken is the finding, not a reinvention. A repo with no **guardrail** (no pre-commit hook and no CI job running its lint\u002Ftypecheck\u002Ftest command) is itself a finding: an un-linted repo is a standing missed opportunity, not a neutral default. _Use when_ the agent made a mistake an automated check could have caught, or the repo has no guardrail at all.\n- **Coding standards**: should the **reviewer agent** be given a new rule to enforce? Should an existing rule be removed or clarified? Classify the violation first: a **mechanical** one (a fixed syntactic pattern, a banned API, an import shape, a file-location rule) gets a deterministic check, full stop: a custom rule in the repo's own linter, a new pre-commit hook, or a new CI job, whichever the repo's language and existing guardrail make cheapest. Default to building the check over writing the rule. Reserve `CODING_STANDARDS.md` for genuine **judgement calls** (cross-file consistency, \"matches the surrounding style,\" anything no guardrail could ever substitute for). _Use when_ the reviewer agent failed to catch a mistake.\n- **Global AGENTS.md**: are there any steering instructions that should be moved to coding standards (or automated checks) instead? _Use when_ the AGENTS.md file is particularly large - in the repo OR the user's global scope.\n- **Tool economy**: did the agent make expensive tool calls that could be streamlined? Is there any custom tooling (CLI's, MCP's) that is particularly token-inefficient? _Use when_ the agent made an expensive tool call.\n- **No-ops**: look for instructions in steering files that don't modify the agent's behavior. _Use when_ the steering files are large and unwieldy.\n- **Information access**: look for opportunities to increase the agent's access to information. Teeing dev server logs, readonly access to third-party services. _Use when_ a crucial piece of information was not available to the agent.\n\n4. Present these candidates to the user, in order of severity.\n\n## Reference\n\n### Implementation vs Review\n\nRemember that all work goes through two stages: implementation and review. The implementation agent has the most **context pressure**. They are responsible for exploration, writing code, and debugging failures.\n\nThe review agent has the least context pressure - it receives a diff, so no exploration needed. It often does not need to write code or debug.\n\nThis means that the review agent should be responsible for imposing coding standards, not the implementation agent.\n\n### Files\n\nYou have access to several files in the repo:\n\n- `CLAUDE.md`\u002F`AGENTS.md`: these files are pushed to the context window of any agent working in this repo. They should be used incredibly sparingly, usually only for **navigation pointers** to other files.\n- `CODING_STANDARDS.md`: this file is read during review, not implementation. Add **navigation pointers** to docs folders if the standards file gets more than 1,000 lines long.\n- Docs: use docs as references files, pointed to by other files. Look for existing docs before writing new ones.\n- Skills: use skills for docs (since their description goes into the agent's context window), or for user-invoked commands. Follow the advice in the `writing-for-agents` skill.\n","The user has asked for a **retrospective**. You are suggesting improvements to the coding agent's **environment** to improve future runs.\n\n## Steps\n\n1. Call the Skill tool with `writing-for-agents` for the writing style guide.\n\n2. Read the primary sources for the session the user specifies. This may mean searching through session logs on this machine. If the user doesn't specify a session, default to the current one.\n\n3. Look for candidates for improvement in these categories.\n\n- **Navigation**: how easy was it for the agent to find the right files? Are there hidden dependencies between files? Would a **navigation pointer** make it easier? _Use when_ the session took a long time to find a piece of information.\n- **Automated checks**: are there automated checks that could catch errors the agent made? Linting, typing, tests, filesystem linters? Read the repo's own check command first (its `package.json`\u002Fbuild-tool `lint`\u002F`check` scripts, its CI workflow), so a check that already exists but sits unwired or silently broken is the finding, not a reinvention. A repo with no **guardrail** (no pre-commit hook and no CI job running its lint\u002Ftypecheck\u002Ftest command) is itself a finding: an un-linted repo is a standing missed opportunity, not a neutral default. _Use when_ the agent made a mistake an automated check could have caught, or the repo has no guardrail at all.\n- **Coding standards**: should the **reviewer agent** be given a new rule to enforce? Should an existing rule be removed or clarified? Classify the violation first: a **mechanical** one (a fixed syntactic pattern, a banned API, an import shape, a file-location rule) gets a deterministic check, full stop: a custom rule in the repo's own linter, a new pre-commit hook, or a new CI job, whichever the repo's language and existing guardrail make cheapest. Default to building the check over writing the rule. Reserve `CODING_STANDARDS.md` for genuine **judgement calls** (cross-file consistency, \"matches the surrounding style,\" anything no guardrail could ever substitute for). _Use when_ the reviewer agent failed to catch a mistake.\n- **Global AGENTS.md**: are there any steering instructions that should be moved to coding standards (or automated checks) instead? _Use when_ the AGENTS.md file is particularly large - in the repo OR the user's global scope.\n- **Tool economy**: did the agent make expensive tool calls that could be streamlined? Is there any custom tooling (CLI's, MCP's) that is particularly token-inefficient? _Use when_ the agent made an expensive tool call.\n- **No-ops**: look for instructions in steering files that don't modify the agent's behavior. _Use when_ the steering files are large and unwieldy.\n- **Information access**: look for opportunities to increase the agent's access to information. Teeing dev server logs, readonly access to third-party services. _Use when_ a crucial piece of information was not available to the agent.\n\n4. Present these candidates to the user, in order of severity.\n\n## Reference\n\n### Implementation vs Review\n\nRemember that all work goes through two stages: implementation and review. The implementation agent has the most **context pressure**. They are responsible for exploration, writing code, and debugging failures.\n\nThe review agent has the least context pressure - it receives a diff, so no exploration needed. It often does not need to write code or debug.\n\nThis means that the review agent should be responsible for imposing coding standards, not the implementation agent.\n\n### Files\n\nYou have access to several files in the repo:\n\n- `CLAUDE.md`\u002F`AGENTS.md`: these files are pushed to the context window of any agent working in this repo. They should be used incredibly sparingly, usually only for **navigation pointers** to other files.\n- `CODING_STANDARDS.md`: this file is read during review, not implementation. Add **navigation pointers** to docs folders if the standards file gets more than 1,000 lines long.\n- Docs: use docs as references files, pointed to by other files. Look for existing docs before writing new ones.\n- Skills: use skills for docs (since their description goes into the agent's context window), or for user-invoked commands. Follow the advice in the `writing-for-agents` skill.\n",{"name":5,"description":7,"disable-model-invocation":29},true,"main","7ea7cd250b1d6a56795f2f23baf513a21420124b","skills\u002Fhand\u002Fretro","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills","https:\u002F\u002Fgithub.com\u002FnicolasLuduena","https:\u002F\u002Fnico-luduena.online","Senior full-stack engineer at @txpipe · Rust, TypeScript, blockchain infrastructure, developer tooling, and privacy-preserving applications.","2026-11-10 04:46:43",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":29},[40,43,46],{"tool":41,"command":42},"npx","npx skills add nicolasLuduena\u002Fskills --skill retro",{"tool":44,"command":45},"bunx","bunx skills add nicolasLuduena\u002Fskills --skill retro",{"tool":47,"command":48},"pnpm","pnpm dlx skills add nicolasLuduena\u002Fskills --skill retro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fretro\u002FSKILL.md",[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"agents\u002Fopenai.yaml","REFERENCE","参考文档",146,"https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fretro\u002Fagents\u002Fopenai.yaml",[58,65,96,117,139,154],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":24},"01M717YJYMV0G9H52HJ9R259M2","improve","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fimprove\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fimprove\u002FSKILL.md",[],[60],{"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":76,"publishedAt":24},"01M6DT66VWY2M4VM3J7G2813T6","create-verification-skill","Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for \u002Fcreate-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI\u002FCLI\u002Fservice behavior.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002Fcreate-verification-skill\u002FSKILL.md",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[77,78,79,30,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95],"create verification skill","verification","create","app","control","platform","project","local","evidence","use","generated","repo","verify","license","harness","generate","pr","github","cli",{"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":24},"01M6DT604C3A5GRG03S2XM9QR4","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Ftdd\u002FSKILL.md",[],[98,103,104,105,86,106,107,108,109,110,111,112,113,114,115,116],"test","build","red-green-refactor","fix","user","first","refactor","integration","development","integration tests","green","red","driven","tests",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":24},"01M6DT6ABQ8TMVEFEFRQ7SP58V","maintain-verification-skill","Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for \u002Fmaintain-verification-skill or \"audit the verify skill\".","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002Fmaintain-verification-skill\u002FSKILL.md",[123],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[125,126,78,127,90,93,94,89,128,129,130,22,131,132,133,83,134,30,135,86,21,136,88,137,138],"maintain","maintain verification skill","audit","normal","weekly","for","tree","as","feature","map","periodic","implementer","parallel","loop",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":24},"01M6DT64EQS172J3GFTSGW6MZR","verdict","The Reviewer's Verdict on a PR: re-run the repo's verification skill at the PR's head, hold the PR's Evidence against it, and record pass or fail with nico-agent.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Fverdict\u002FSKILL.md",[],[141,146,147,22,148,149,150,151,85,88,152,78,153,93],"record","at","re","with","it","head","reviewer","run",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":24},"01M6DT5X7ZAHFMFDSMM1RA2500","research","Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Fresearch\u002FSKILL.md",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000021","资料检索与研究",[156,164,165,166,167,168,88,169,107,170,171,172,173,174,175,132,176,177,86],"investigate","markdown","capture","file","docs","api","when","background","facts","high","reading","sources","trust","question"]