[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D08Y7PZYDN5QJG944EG593":3,"skill-same:01M6D08Y7PZYDN5QJG944EG593":102},{"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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6D08Y7PZYDN5QJG944EG593","assets",null,"Soft authoring conventions for skill assets as reusable, just-in-time procedural rulebooks.","itlackey\u002Fakm","itlackey","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6414031?v=4","01M6D08NHES2CPRGY5HCPJECD6","IT Lackey","01M6D08NP1PF52ABWJNQZKA5H0",70,"MPL-2.0","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Fskill.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"just-in-time","just","write","reusable","time","conventions","revise","authoring","as","asset","procedural","for","when","2026","2026-11-10 10:12:30",false,"---\ntype: fact\ncategory: convention\ndescription: Soft authoring conventions for skill assets as reusable, just-in-time procedural rulebooks.\nwhen_to_use: Surfaced to authoring agents when they write or revise a skill asset.\nupdated: 2026-07-28\n---\n\n\u003C!--\n  SOFT guidance only — advice, not a contract. Nothing here is enforced by the\n  proposal gate; validator-rejecting HARD rules live in src\u002Fcore\u002Fauthoring-rules.ts\n  and remain the sole enforced source. Editing or deleting this file cannot weaken\n  the gate. Tune the guidance below to match how your stash wants this asset type\n  maintained.\n-->\n\n# Skill authoring conventions\n\nA skill is a reusable, self-contained capability stored as `skills\u002F\u003Cname>\u002FSKILL.md`. Treat it like a compact operating manual that an agent can load just-in-time, follow without rediscovering the process, and improve when repeated use exposes gaps.\n\n## Purpose\n\nUse a skill when the stash needs reusable procedural guidance for a recurring class of work. A good skill reduces repeated reasoning cost: future agents should not have to reconstruct the same method from raw context.\n\n## Authoring strategy\n\n- Make the dispatch signal clear. The description should let a dispatcher decide whether to load the skill without reading the whole body.\n- Open with the outcome the skill helps produce.\n- State when to use it, when not to use it, and what inputs the agent should gather before acting.\n- Structure the body as a rulebook: principles first, then procedure, then checks.\n- Use short sections and ordered steps where sequence matters.\n- Match the level of detail to how fragile the task is: open-ended work gets high-level heuristics and room to reason, while fragile or consistency-critical steps get exact, unambiguous instructions.\n- Keep the body lean and move bulky background into companion knowledge docs referenced one level deep, so the skill loads cheaply and stays scannable.\n- Include failure modes and verification steps. A skill should tell the agent how to know the work is complete.\n- Keep one skill focused on one capability. Split unrelated concerns into separate skills and cross-reference them.\n\n## Maintenance strategy\n\n- Update the skill when session logs, feedback, or rejected proposals reveal repeatable confusion.\n- Add companion knowledge docs when the skill needs background material that would bloat the main procedure.\n- Promote durable recurring corrections into the skill; leave one-off observations in memories or lessons.\n- Prefer small edits that preserve the skill’s operational shape over broad rewrites that erase tested guidance.\n\n## Placement & linking\n\n- Skills are **reuse-born**: place `skills\u002F\u003Cdomain>\u002F\u003Cname>\u002FSKILL.md` under a\n  stable **domain** prefix from `facts\u002Fconventions\u002Fdomains`\n  (`skills\u002Ftesting\u002Fflaky-test-triage`) so any project finds and reuses it instead\n  of duplicating the procedure.\n","\u003C!--\n  SOFT guidance only — advice, not a contract. Nothing here is enforced by the\n  proposal gate; validator-rejecting HARD rules live in src\u002Fcore\u002Fauthoring-rules.ts\n  and remain the sole enforced source. Editing or deleting this file cannot weaken\n  the gate. Tune the guidance below to match how your stash wants this asset type\n  maintained.\n-->\n\n# Skill authoring conventions\n\nA skill is a reusable, self-contained capability stored as `skills\u002F\u003Cname>\u002FSKILL.md`. Treat it like a compact operating manual that an agent can load just-in-time, follow without rediscovering the process, and improve when repeated use exposes gaps.\n\n## Purpose\n\nUse a skill when the stash needs reusable procedural guidance for a recurring class of work. A good skill reduces repeated reasoning cost: future agents should not have to reconstruct the same method from raw context.\n\n## Authoring strategy\n\n- Make the dispatch signal clear. The description should let a dispatcher decide whether to load the skill without reading the whole body.\n- Open with the outcome the skill helps produce.\n- State when to use it, when not to use it, and what inputs the agent should gather before acting.\n- Structure the body as a rulebook: principles first, then procedure, then checks.\n- Use short sections and ordered steps where sequence matters.\n- Match the level of detail to how fragile the task is: open-ended work gets high-level heuristics and room to reason, while fragile or consistency-critical steps get exact, unambiguous instructions.\n- Keep the body lean and move bulky background into companion knowledge docs referenced one level deep, so the skill loads cheaply and stays scannable.\n- Include failure modes and verification steps. A skill should tell the agent how to know the work is complete.\n- Keep one skill focused on one capability. Split unrelated concerns into separate skills and cross-reference them.\n\n## Maintenance strategy\n\n- Update the skill when session logs, feedback, or rejected proposals reveal repeatable confusion.\n- Add companion knowledge docs when the skill needs background material that would bloat the main procedure.\n- Promote durable recurring corrections into the skill; leave one-off observations in memories or lessons.\n- Prefer small edits that preserve the skill’s operational shape over broad rewrites that erase tested guidance.\n\n## Placement & linking\n\n- Skills are **reuse-born**: place `skills\u002F\u003Cdomain>\u002F\u003Cname>\u002FSKILL.md` under a\n  stable **domain** prefix from `facts\u002Fconventions\u002Fdomains`\n  (`skills\u002Ftesting\u002Fflaky-test-triage`) so any project finds and reuses it instead\n  of duplicating the procedure.\n",{"type":43,"updated":44,"category":45,"description":7,"when_to_use":46},"fact",1785196800000,"convention","Surfaced to authoring agents when they write or revise a skill asset.","main","2af843f5300942bd7fe1f86fbfdffbe94484c6fe","src\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets",4,"https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm","https:\u002F\u002Fgithub.com\u002Fitlackey","2026-11-12 04:01:36",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add itlackey\u002Fakm --skill assets",{"tool":60,"command":61},"bunx","bunx skills add itlackey\u002Fakm --skill assets",{"tool":63,"command":64},"pnpm","pnpm dlx skills add itlackey\u002Fakm --skill assets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Fskill.md",true,[68,74,78,82,86,90,94,98],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"agent.md","REFERENCE","参考文档",2378,"https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Fagent.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"command.md",2234,"https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Fcommand.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"fact.md",2737,"https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Ffact.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"knowledge.md",2928,"https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Fknowledge.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"lesson.md",2490,"https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Flesson.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"memory.md",2380,"https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Fmemory.md",{"path":95,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":96,"sourceHtmlUrl":97},"script.md",2422,"https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Fscript.md",{"path":99,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":100,"sourceHtmlUrl":101},"workflow.md",2266,"https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Fsrc\u002Fassets\u002Fstash-skeleton\u002Ffacts\u002Fconventions\u002Fassets\u002Fworkflow.md",[103,125,148,170,202,214],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":38},"01M6D0A9JYBMC2RKABMSB478MG","svelte-components","Build reusable Svelte components with best practices for composition and state management","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fstashes\u002Franking-baseline\u002Fskills\u002Fsvelte-components\u002FSKILL.md",[],[110,111,112,113,114,115,116,117,118,119,120,121,122,27,123,124,35],"components","svelte","svelte components","state management","component","architecture","create","component architecture","best practices","state","ui","Composition","management","build","with",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":134,"publishedAt":38},"01M6D0A5JV0BXGCVCZ4KVVZSVM","k8s-deploy","Deploy and manage applications on Kubernetes clusters with kubectl and Helm","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fstashes\u002Franking-baseline\u002Fskills\u002Fk8s-deploy\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[135,136,137,124,138,139,140,141,142,143,144,145,146,147],"k8s deploy","deploy","kube","chart","k8s","manage","helm","applications","kubectl","kubernetes","deployment","apply","Clusters",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":38},"01M6D0A14W9YYDR3HR75K025QN","docker-homelab","Manage Docker containers, images, and networks in a homelab environment","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fstashes\u002Franking-baseline\u002Fskills\u002Fdocker-homelab\u002FSKILL.md",[154],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},[156,157,158,159,160,161,162,163,164,165,166,167,168,140,169],"docker homelab","docker","docker compose orchestration","environment","homelab","containers","orchestration","troubleshoot","setup","docker compose","networks","compose","images","docker-compose",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":185,"publishedAt":38},"01M6D09Y1HC29RW6B9J9Y5E69X","code-review-skill","Review code for quality issues, bugs, and adherence to best practices","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fstashes\u002Franking-baseline\u002Fskills\u002Fcode-review-skill\u002FSKILL.md",[176,179,180],{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":181,"categoryName":182,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[186,187,188,189,190,191,192,193,194,118,195,196,197,198,199,35,200,201],"review skill","code","code review skill","review","code review","check","code quality","pull request","lint","issues","pull","review code","quality","review pull request","bugs","request",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":209,"publishedAt":38},"01M6D09V2RYXMA519MEJAEBDDF","hello-world","Trivial demonstration skill that prints a greeting","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fstashes\u002Fminimal\u002Fskills\u002Fhello-world\u002FSKILL.md",[208],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[210,211,212,213],"world","hello","hello world","greeting",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":221,"publishedAt":38},"01M6D09QRPY362BWCT1FEQH73A","all-types-skill","Minimal skill fixture used by the all-types parity stash","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fstashes\u002Fall-types\u002Fskills\u002Fall-types-skill\u002FSKILL.md",[220],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[222,223,224,225,226,227,228,229,230],"all types skill","types","minimal","fixture","2025","parity","skill fixture","stash","minimal skill"]