[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDY7V9VR5DDC0TPXQRB6K1":3,"skill-same:01M7CDY7V9VR5DDC0TPXQRB6K1":45},{"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},"01M7CDY7V9VR5DDC0TPXQRB6K1","skill-up",null,"Aid agent skill creation or modification. Use when creating a new skill or changing an existing one. Use whenever writing any agent instructions, whether to a file or directly in a reply.","dveyarangi\u002Fgoodwolf-harness","dveyarangi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F693404?v=4","01M77KAGWZ8X0CNA092ZDNEF6T","Fima Rotter","01M7CDVSGB58A879MVTYC1SVD0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-up\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skill-up\ndescription: >-\n  Aid agent skill creation or modification. Use when creating a new skill or changing an existing one.\n  Use whenever writing any agent instructions, whether to a file or directly in a reply.\n---\n\n\u003Cstraw-dog question=\"q-mzn7ek\">Mechanism: not yet\u003C\u002Fstraw-dog>\n\nYour goal is to aid agent skill creation or modification.\n\nWriting rules — to the mechanism shape, which produces instructions, a skill is a record of the\nkind *what must always hold*, and these are that kind's invariants for one:\n\n- A skill is instruction, not story. Be precise and concise. Prefer umbrella terms to enumeration, unless can be interpreted wrong in context of the skill.\n- State everything in definitive form — no evolution logic, no decision explanations.\n- Write a filter, a fixed form or a must only where it always holds; where judgement decides, leave it to the model rather than overfit the instruction.\n\nBefore writing, browse the existing skill set and match its structure and vibe — frontmatter shape, file layout, linking style, tone, altitude. Derive the set's conventions from the set itself; do not impose foreign ones.\n\nVerify the new or changed skill against the set:\n\n- It does not overlap an existing skill, unless the overlap is intentional — then name it and link the owning skill.\n- It does not contradict any existing skill.\n- It does not misfit the set — wrong altitude, wrong output location, conventions the set does not use.\n\nA fact the set already states in one skill is referenced from there, not restated.\n\nWeigh the whole skill on every change: say what the change removes before what it adds, and compare the body's size before and after. A body that has only grown is read whole for what restates another home, what a script already does for the reader, and what is a record's format, which goes to a format file beside it.\n\nThe frontmatter description narrates the use case — the skill's moments —, not the implementation, and stays in line with the skill's intent; the body holds what to do at them and never restates when. Capturing skill intent and usage is critical — \u002Falign when in tiniest doubt.\n\n## Project-local divergence\n\nA skill the harness ships carries a project fact only in the local block its installer writes; its body and appendices carry none. A project's own skill cites the project's documentation for what it holds.\n\n## Merging a reference corpus\n\nWhen asked to merge the skill corpus, ask which corpus to merge from.\nPort body changes, fixing defects as you port; leave every appendix file and installed block as it stands. A skill present in only one corpus is either local by intent or not yet ported — ask which.\n\n## Installed from other mechanisms\n\n\u003Cinstalled by=\"mechanism-shape\">\n**R5** Before writing a rule into AGENTS.md, find the mechanism whose work it governs. Land a\nmechanism's rule in AGENTS.md only as an installed block from its rules file. While the\nmechanism is undeclared, write the rule by hand and wrap it as a straw dog bound to the question\nof what the mechanism owns, as you write it.\n\n**R6** A skill is an instruction file of exactly one mechanism and opens its body with\n`Mechanism: \u003Cslug>`. A skill no mechanism names opens it with `Mechanism:` then `not yet`,\nwrapped as a straw dog bound to the question of what the skill owns, or `unowned by design` with\nits reason. A script, test or hook a mechanism owns opens with `# Mechanism: \u003Cslug>`, after a\nshebang where there is one. Write the line as you add the file; no list holds it.\n\n**R8** Name no skill of a mechanism whose state is `installed` in another skill's own text: what it asks\nof that skill reaches it as an installed block from its rules file.\n\u003C\u002Finstalled>\n\n\u003Cinstalled by=\"local\">\n**L10** What the harness ships names under `docs\u002F` only where a mechanism keeps a kind of record — the\ndirectory, or the one file that is a record — never a record inside one; a question only as a\nstraw dog's binding or a `TODO q-N`; a ticket never.\n\u003C\u002Finstalled>\n","\u003Cstraw-dog question=\"q-mzn7ek\">Mechanism: not yet\u003C\u002Fstraw-dog>\n\nYour goal is to aid agent skill creation or modification.\n\nWriting rules — to the mechanism shape, which produces instructions, a skill is a record of the\nkind *what must always hold*, and these are that kind's invariants for one:\n\n- A skill is instruction, not story. Be precise and concise. Prefer umbrella terms to enumeration, unless can be interpreted wrong in context of the skill.\n- State everything in definitive form — no evolution logic, no decision explanations.\n- Write a filter, a fixed form or a must only where it always holds; where judgement decides, leave it to the model rather than overfit the instruction.\n\nBefore writing, browse the existing skill set and match its structure and vibe — frontmatter shape, file layout, linking style, tone, altitude. Derive the set's conventions from the set itself; do not impose foreign ones.\n\nVerify the new or changed skill against the set:\n\n- It does not overlap an existing skill, unless the overlap is intentional — then name it and link the owning skill.\n- It does not contradict any existing skill.\n- It does not misfit the set — wrong altitude, wrong output location, conventions the set does not use.\n\nA fact the set already states in one skill is referenced from there, not restated.\n\nWeigh the whole skill on every change: say what the change removes before what it adds, and compare the body's size before and after. A body that has only grown is read whole for what restates another home, what a script already does for the reader, and what is a record's format, which goes to a format file beside it.\n\nThe frontmatter description narrates the use case — the skill's moments —, not the implementation, and stays in line with the skill's intent; the body holds what to do at them and never restates when. Capturing skill intent and usage is critical — \u002Falign when in tiniest doubt.\n\n## Project-local divergence\n\nA skill the harness ships carries a project fact only in the local block its installer writes; its body and appendices carry none. A project's own skill cites the project's documentation for what it holds.\n\n## Merging a reference corpus\n\nWhen asked to merge the skill corpus, ask which corpus to merge from.\nPort body changes, fixing defects as you port; leave every appendix file and installed block as it stands. A skill present in only one corpus is either local by intent or not yet ported — ask which.\n\n## Installed from other mechanisms\n\n\u003Cinstalled by=\"mechanism-shape\">\n**R5** Before writing a rule into AGENTS.md, find the mechanism whose work it governs. Land a\nmechanism's rule in AGENTS.md only as an installed block from its rules file. While the\nmechanism is undeclared, write the rule by hand and wrap it as a straw dog bound to the question\nof what the mechanism owns, as you write it.\n\n**R6** A skill is an instruction file of exactly one mechanism and opens its body with\n`Mechanism: \u003Cslug>`. A skill no mechanism names opens it with `Mechanism:` then `not yet`,\nwrapped as a straw dog bound to the question of what the skill owns, or `unowned by design` with\nits reason. A script, test or hook a mechanism owns opens with `# Mechanism: \u003Cslug>`, after a\nshebang where there is one. Write the line as you add the file; no list holds it.\n\n**R8** Name no skill of a mechanism whose state is `installed` in another skill's own text: what it asks\nof that skill reaches it as an installed block from its rules file.\n\u003C\u002Finstalled>\n\n\u003Cinstalled by=\"local\">\n**L10** What the harness ships names under `docs\u002F` only where a mechanism keeps a kind of record — the\ndirectory, or the one file that is a record — never a record inside one; a question only as a\nstraw dog's binding or a `TODO q-N`; a ticket never.\n\u003C\u002Finstalled>\n",{"name":5,"description":7},"main","a43633f7ef0eeeb220f42872be487150daec8575",".agents\u002Fskills\u002Fskill-up","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness","https:\u002F\u002Fgithub.com\u002Fdveyarangi","http:\u002F\u002Fdveyarangi.blogspot.com\u002F","2026-11-14 12:09:52",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add dveyarangi\u002Fgoodwolf-harness --skill skill-up",{"tool":37,"command":38},"bunx","bunx skills add dveyarangi\u002Fgoodwolf-harness --skill skill-up",{"tool":40,"command":41},"pnpm","pnpm dlx skills add dveyarangi\u002Fgoodwolf-harness --skill skill-up","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-up\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7CDYHDFRAZP8T121PGMZ46R","verify","Use after an implementation pass, or to verify a landed slice before close. Whole verification of landed work: ticket, RFC, governing docs, and the project's verification set.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7CDYES9QW4N2JZ8GX1Q9DMV","ticket","Use to decompose a parent work into independently-workable child tickets. Use to mint ticket(s), possibly a single one, when planning implementation without one.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fticket\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7CDYB6CFM7PD0APTBBS17HH","tdd","Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions \"red-green-refactor\", wants integration tests, or asks for test-first development.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CDY4B01RZP7Y90JGTCHNY5","setup-devops","Set up the project's engineering scaffolding, from toolchain to CICD and observability. Use when initializing a repo or filling a setup gap.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-devops\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CDY1P8T9VT2W2ZXEH1H4PR","review-architecture","Explore the codebase for module-deepening opportunities — architectural improvements that raise testability and navigability. Use when asked to improve or refactor the architecture.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview-architecture\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CDXYZWWB6QVZPF7Q4PXSMY","recall","Determine where the project stands and what to work on next, with the decisions already taken surfaced alongside the questions genuinely still open. Use when asked what is next, where things stand, or to continue or pick up work.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frecall\u002FSKILL.md",[],[]]