[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDXJBKW23C0DW5EMTC8TC4":3,"skill-same:01M7CDXJBKW23C0DW5EMTC8TC4":51},{"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},"01M7CDXJBKW23C0DW5EMTC8TC4","mechanism",null,"Method is mechanism work: use before changing how the work is done here — a skill, a check, a record, the loop itself — before building or amending a mechanism, and before changing a rule inside an `\u003Cinstalled>` block, whose home is its mechanism's rules file. Not for what the project produces.","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\u002Fmechanism\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mechanism\ndescription: >-\n  Method is mechanism work: use before changing how the work is done here — a\n  skill, a check, a record, the loop itself — before building or amending a\n  mechanism, and before changing a rule inside an `\u003Cinstalled>` block, whose\n  home is its mechanism's rules file. Not for what the project produces.\n---\n\nMechanism: mechanism-shape\n\n# Build and amend mechanisms\n\nThe only home of the shape. A rule carrying a name and date is that person's to amend.\n\n## Is it a mechanism\n\nA mechanism is part of **how the work gets done**. What the project produces is not one,\nhowever much depends on it.\n\nTest: does other work rely on this as a source of instruction or behavior *about how\nto work*? Then it is a mechanism and owes a declaration.\n\n- A system, never a file. One spans skills, scripts, records, and rules injected into\n  skills it did not write.\n- **A skill has one mechanism** *(the user, 2026-09-06)*. A mechanism may own several,\n  each the act at one of its moments over a record it declares; a skill that acts on no\n  record of the mechanism is not its own *(loosened, the user, 2026-10-10)*. Rules it\n  needs in a skill it does not own are installed as text from its rules file, and no body\n  restates one *(the user, 2026-09-07)*.\n- Writing an entry into a record is not mechanism work. It belongs to the skill that\n  owns the entry.\n\n## Three homes, and the chain\n\n| home | holds | reaches a session |\n|---|---|---|\n| `AGENTS.md` | meta-principles, and a mechanism's rules only as installed blocks | at start, every session |\n| `.agents\u002Fskills\u002F\u003Cname>\u002F` | the act, and every rule read *in the work it governs* | when the skill is invoked |\n| `.agents\u002Fmechanisms\u002F\u003Cslug>\u002F` | why the instruction is what it is: parts, moments, and the mechanism's rules in their single home | when installing, amending or debugging |\n\nThe cut is **when is this read**. There is no fourth home. What a skill's act needs — a call, a\nrefusal and what to do at it, a script's name — is instruction and stays in the skill; the doc\ntakes only what informs.\n\n> The doc is the instruction's *why*. The evidence is the doc's *why*.\n> *(the user, 2026-09-06)*\n\n- Doc and instruction file are never the same file.\n- One evidence per mechanism, belonging to its doc. It lives **outside `.agents\u002F`**, under\n  `docs\u002Fmechanisms\u002F`, named by the slug *(the user, 2026-09-06)* — it cites records that\n  cannot travel, so the doc never names it; the shelf declares the record.\n- A skill's `EVIDENCE.md` predating its declaration is an unsorted mixture: doc\n  material to the doc, the doc's own why to the evidence.\n\nWorking parts stay where the harness needs them — skills, scripts, tests. Directory,\ndoc sections and what a script parses are\n[MECHANISM-FORMAT.md](.\u002FMECHANISM-FORMAT.md)'s; restate none of it here.\n\n## Moments\n\nA moment is an occasion at which a person acts on the mechanism. Every one carries an\ninstruction or a stated kind of absence, and either way a clause saying why.\n\n| kind | means | carries |\n|---|---|---|\n| `elsewhere` | instructed, by another mechanism | the instruction file that does it |\n| `embedded` | instructed, from the wrong home | where the instruction sits |\n| `unowned by design` | no rule warranted | its reason, nothing else |\n| `not yet` | a genuine gap | the open question it waits on, as a straw dog's binding |\n\nThere is no *none needed*: if nobody acts, it is not a moment. The verdict is per moment,\nnever per mechanism.\n\n## Rules, injection and retraction\n\nA rule lives in one file — `\u003Cslug>.rules.md`, in the mechanism's own directory. Nothing\nreads it at session time: a generic core installer, never a per-mechanism one, writes\nits rules into the targets as delimited and visibly owned blocks, and that is the only\nform in which they reach anyone. A copy in a target is **installed, never authored**.\n\nAuthor a rule in the skill's body when only that skill's act reads it. Put a rule that two\noccasions read in the rules file and install it everywhere it is read, the owner's own skill\nincluded *(the user, 2026-09-20)*.\n\n- Removable as written: retraction leaves the target byte-identical.\n- **No default mode.** A bare invocation refuses.\n- **Refuse rather than guess** — missing target, missing anchor, block present and differing.\n  A hand-edited block is drift, not a second opinion: its change is routed to the rules file.\n- A rules file's block is installed in every target it names, each member of a group included, or\n  the check fails.\n\nThe installer is `inject_rules.py`: `\u003Cslug> --install`, with `--overwrite` when the source has\nmoved, which also takes the source's block out of a file it no longer names; `\u003Cslug> --retract`; `--check` over the tree, in the verification set. Grammar and block\nform: [MECHANISM-FORMAT.md](.\u002FMECHANISM-FORMAT.md#the-rules-file).\n\nA mechanism that injects nothing has no rules file. A project's own rules file, beside the\nentry file, is the installer's other source, read through the same grammar and placed after\nevery mechanism's block; what it is and what it may override is R7's, installed at tier 1.\n\n**A sentence about another mechanism is that mechanism's** *(the user, 2026-09-07)*. What\nshapes how mechanisms are built around it — what `\u002Fmaintain` must be handed at inception, for\none — is a rule in its rules file, installed here, never authored here. Its core function\nreaches a session through its own description, strengthened at tier 1 where warranted; a\nprinciple that resonates through the whole harness may land in `AGENTS.md` — that mechanism's\ndecision, rare, and investigated first.\n\n## Mechanical by construction\n\nA mechanism is designed from inception for mechanical derivation, checking and repair: its\nidentity, governing sources, dependencies and record contracts are explicit enough for a script\nto enumerate what a change affects. Anything that can be maintained mechanically is; a missing\nscript is written as part of the repair; archived records are not exempt *(the user,\n2026-09-05)*.\n\n## What it produces\n\n**Everything a mechanism produces is read by someone, or the doc says why nobody does**\n*(the user, 2026-09-07)*. Name each artifact and its reader: a person at a stated moment, another\nmechanism, a script, a check. An output with no reader is either dead weight or a missing reader,\nand which of the two it is only becomes answerable once it is written down.\n\nThis covers what the mechanism emits as well as what it ships — a report nobody opens, a record\nnothing indexes, a file dropped where nothing looks.\n\n## Records\n\nA mechanism with records declares what a record is — its fields, what a row means, its\ntier, when a finished entry is gone: the condition, never the actor or the moment, which are the\ndoc's and the script's — in a format file beside its instruction file, referenced from its doc\nand its skill, or in the skill itself where the format is small; never in the doc *(the user,\n2026-09-07; where, 2026-09-27; the condition, 2026-10-23)*.\n\n\u003Cinstalled by=\"mechanism-shape\">\n**R1** Check a record-bearing mechanism's records with its maintainer script — format never\ncontent, live rows only. Where the script is missing, write it: that is the maintenance.\n\n**R4** Render an index on request; never commit one beside its records. A file listing what other\nfiles each say for themselves is an index, whatever it is called — an allowlist, a register,\na manifest — and each entry belongs at its authored home, wrapped there if provisional.\n\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## Incept\n\n1. **`\u002Falign` first**, on what the mechanism is: its moments, its\n   authority, its record shape, its index, the tier of each part, what retires it.\n2. Write the doc to [MECHANISM-FORMAT.md](.\u002FMECHANISM-FORMAT.md), naming the parts it\n   owns and the parts it relies on with their owners; and its rules file, installed before\n   the doc is checked.\n3. **Write the check before the thing it checks**, watching every diagnostic fail in\n   both polarities.\n4. **Run it over what already exists** and record the count of prior violations — or\n   state that there was no prior corpus, rather than a manufactured zero.\n5. Name what retires it.\n6. **Name what would show it working, graded by someone who did not build it.**\n   Pre-register it so a later session can answer without asking what was meant.\n\n**Absence is not clearance**: a clean run means nothing was caught, never that the tree\nobeys.\n\n\u003Cinstalled by=\"maintain\">\n**M1** Name what `\u002Fmaintain` must do for this mechanism — a maintainer script to run, records to\nre-check when its surfaces move — as rules in its rules file targeting `\u002Fmaintain`. Nothing is\nwritten into `\u002Fmaintain` by hand.\n\u003C\u002Finstalled>\n\n## Amend and retire\n\nEditing a skill that is an instruction file is amending its mechanism — run the steps\nstill live, aligning again when the shape itself moves. Amend a rule in its rules file, then\ninstall it with overwrite; the block in a target is never the place. A mechanism is re-checked\nwhen what governs it has moved; which skill does that is its doc's row, not this body's\nsentence.\n\nRetiring runs `--retract` first, then removes the mechanism's parts and its directory, its\nown trigger among them. An always-on mechanism cannot be retired.\n\n## Siblings\n\n- [`\u002Fskill-up`](..\u002Fskill-up\u002FSKILL.md) writes a skill's text; this governs the system it\n  belongs to. Both apply when a skill is an instruction file.\n- [`\u002Fimpact`](..\u002Fimpact\u002FSKILL.md) traces a change's consequences; this asks whether a\n  mechanism is sound at both ends.\n- [`\u002Fmaintain`](..\u002Fmaintain\u002FSKILL.md) applies the shape's rules and owns none of them; what it\n  asks of an inceptor is its own rule, installed above.\n- [`\u002Falign`](..\u002Falign\u002FSKILL.md) is called by incept, before anything is built.\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","Mechanism: mechanism-shape\n\n# Build and amend mechanisms\n\nThe only home of the shape. A rule carrying a name and date is that person's to amend.\n\n## Is it a mechanism\n\nA mechanism is part of **how the work gets done**. What the project produces is not one,\nhowever much depends on it.\n\nTest: does other work rely on this as a source of instruction or behavior *about how\nto work*? Then it is a mechanism and owes a declaration.\n\n- A system, never a file. One spans skills, scripts, records, and rules injected into\n  skills it did not write.\n- **A skill has one mechanism** *(the user, 2026-09-06)*. A mechanism may own several,\n  each the act at one of its moments over a record it declares; a skill that acts on no\n  record of the mechanism is not its own *(loosened, the user, 2026-10-10)*. Rules it\n  needs in a skill it does not own are installed as text from its rules file, and no body\n  restates one *(the user, 2026-09-07)*.\n- Writing an entry into a record is not mechanism work. It belongs to the skill that\n  owns the entry.\n\n## Three homes, and the chain\n\n| home | holds | reaches a session |\n|---|---|---|\n| `AGENTS.md` | meta-principles, and a mechanism's rules only as installed blocks | at start, every session |\n| `.agents\u002Fskills\u002F\u003Cname>\u002F` | the act, and every rule read *in the work it governs* | when the skill is invoked |\n| `.agents\u002Fmechanisms\u002F\u003Cslug>\u002F` | why the instruction is what it is: parts, moments, and the mechanism's rules in their single home | when installing, amending or debugging |\n\nThe cut is **when is this read**. There is no fourth home. What a skill's act needs — a call, a\nrefusal and what to do at it, a script's name — is instruction and stays in the skill; the doc\ntakes only what informs.\n\n> The doc is the instruction's *why*. The evidence is the doc's *why*.\n> *(the user, 2026-09-06)*\n\n- Doc and instruction file are never the same file.\n- One evidence per mechanism, belonging to its doc. It lives **outside `.agents\u002F`**, under\n  `docs\u002Fmechanisms\u002F`, named by the slug *(the user, 2026-09-06)* — it cites records that\n  cannot travel, so the doc never names it; the shelf declares the record.\n- A skill's `EVIDENCE.md` predating its declaration is an unsorted mixture: doc\n  material to the doc, the doc's own why to the evidence.\n\nWorking parts stay where the harness needs them — skills, scripts, tests. Directory,\ndoc sections and what a script parses are\n[MECHANISM-FORMAT.md](.\u002FMECHANISM-FORMAT.md)'s; restate none of it here.\n\n## Moments\n\nA moment is an occasion at which a person acts on the mechanism. Every one carries an\ninstruction or a stated kind of absence, and either way a clause saying why.\n\n| kind | means | carries |\n|---|---|---|\n| `elsewhere` | instructed, by another mechanism | the instruction file that does it |\n| `embedded` | instructed, from the wrong home | where the instruction sits |\n| `unowned by design` | no rule warranted | its reason, nothing else |\n| `not yet` | a genuine gap | the open question it waits on, as a straw dog's binding |\n\nThere is no *none needed*: if nobody acts, it is not a moment. The verdict is per moment,\nnever per mechanism.\n\n## Rules, injection and retraction\n\nA rule lives in one file — `\u003Cslug>.rules.md`, in the mechanism's own directory. Nothing\nreads it at session time: a generic core installer, never a per-mechanism one, writes\nits rules into the targets as delimited and visibly owned blocks, and that is the only\nform in which they reach anyone. A copy in a target is **installed, never authored**.\n\nAuthor a rule in the skill's body when only that skill's act reads it. Put a rule that two\noccasions read in the rules file and install it everywhere it is read, the owner's own skill\nincluded *(the user, 2026-09-20)*.\n\n- Removable as written: retraction leaves the target byte-identical.\n- **No default mode.** A bare invocation refuses.\n- **Refuse rather than guess** — missing target, missing anchor, block present and differing.\n  A hand-edited block is drift, not a second opinion: its change is routed to the rules file.\n- A rules file's block is installed in every target it names, each member of a group included, or\n  the check fails.\n\nThe installer is `inject_rules.py`: `\u003Cslug> --install`, with `--overwrite` when the source has\nmoved, which also takes the source's block out of a file it no longer names; `\u003Cslug> --retract`; `--check` over the tree, in the verification set. Grammar and block\nform: [MECHANISM-FORMAT.md](.\u002FMECHANISM-FORMAT.md#the-rules-file).\n\nA mechanism that injects nothing has no rules file. A project's own rules file, beside the\nentry file, is the installer's other source, read through the same grammar and placed after\nevery mechanism's block; what it is and what it may override is R7's, installed at tier 1.\n\n**A sentence about another mechanism is that mechanism's** *(the user, 2026-09-07)*. What\nshapes how mechanisms are built around it — what `\u002Fmaintain` must be handed at inception, for\none — is a rule in its rules file, installed here, never authored here. Its core function\nreaches a session through its own description, strengthened at tier 1 where warranted; a\nprinciple that resonates through the whole harness may land in `AGENTS.md` — that mechanism's\ndecision, rare, and investigated first.\n\n## Mechanical by construction\n\nA mechanism is designed from inception for mechanical derivation, checking and repair: its\nidentity, governing sources, dependencies and record contracts are explicit enough for a script\nto enumerate what a change affects. Anything that can be maintained mechanically is; a missing\nscript is written as part of the repair; archived records are not exempt *(the user,\n2026-09-05)*.\n\n## What it produces\n\n**Everything a mechanism produces is read by someone, or the doc says why nobody does**\n*(the user, 2026-09-07)*. Name each artifact and its reader: a person at a stated moment, another\nmechanism, a script, a check. An output with no reader is either dead weight or a missing reader,\nand which of the two it is only becomes answerable once it is written down.\n\nThis covers what the mechanism emits as well as what it ships — a report nobody opens, a record\nnothing indexes, a file dropped where nothing looks.\n\n## Records\n\nA mechanism with records declares what a record is — its fields, what a row means, its\ntier, when a finished entry is gone: the condition, never the actor or the moment, which are the\ndoc's and the script's — in a format file beside its instruction file, referenced from its doc\nand its skill, or in the skill itself where the format is small; never in the doc *(the user,\n2026-09-07; where, 2026-09-27; the condition, 2026-10-23)*.\n\n\u003Cinstalled by=\"mechanism-shape\">\n**R1** Check a record-bearing mechanism's records with its maintainer script — format never\ncontent, live rows only. Where the script is missing, write it: that is the maintenance.\n\n**R4** Render an index on request; never commit one beside its records. A file listing what other\nfiles each say for themselves is an index, whatever it is called — an allowlist, a register,\na manifest — and each entry belongs at its authored home, wrapped there if provisional.\n\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## Incept\n\n1. **`\u002Falign` first**, on what the mechanism is: its moments, its\n   authority, its record shape, its index, the tier of each part, what retires it.\n2. Write the doc to [MECHANISM-FORMAT.md](.\u002FMECHANISM-FORMAT.md), naming the parts it\n   owns and the parts it relies on with their owners; and its rules file, installed before\n   the doc is checked.\n3. **Write the check before the thing it checks**, watching every diagnostic fail in\n   both polarities.\n4. **Run it over what already exists** and record the count of prior violations — or\n   state that there was no prior corpus, rather than a manufactured zero.\n5. Name what retires it.\n6. **Name what would show it working, graded by someone who did not build it.**\n   Pre-register it so a later session can answer without asking what was meant.\n\n**Absence is not clearance**: a clean run means nothing was caught, never that the tree\nobeys.\n\n\u003Cinstalled by=\"maintain\">\n**M1** Name what `\u002Fmaintain` must do for this mechanism — a maintainer script to run, records to\nre-check when its surfaces move — as rules in its rules file targeting `\u002Fmaintain`. Nothing is\nwritten into `\u002Fmaintain` by hand.\n\u003C\u002Finstalled>\n\n## Amend and retire\n\nEditing a skill that is an instruction file is amending its mechanism — run the steps\nstill live, aligning again when the shape itself moves. Amend a rule in its rules file, then\ninstall it with overwrite; the block in a target is never the place. A mechanism is re-checked\nwhen what governs it has moved; which skill does that is its doc's row, not this body's\nsentence.\n\nRetiring runs `--retract` first, then removes the mechanism's parts and its directory, its\nown trigger among them. An always-on mechanism cannot be retired.\n\n## Siblings\n\n- [`\u002Fskill-up`](..\u002Fskill-up\u002FSKILL.md) writes a skill's text; this governs the system it\n  belongs to. Both apply when a skill is an instruction file.\n- [`\u002Fimpact`](..\u002Fimpact\u002FSKILL.md) traces a change's consequences; this asks whether a\n  mechanism is sound at both ends.\n- [`\u002Fmaintain`](..\u002Fmaintain\u002FSKILL.md) applies the shape's rules and owns none of them; what it\n  asks of an inceptor is its own rule, installed above.\n- [`\u002Falign`](..\u002Falign\u002FSKILL.md) is called by incept, before anything is built.\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\u002Fmechanism","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 mechanism",{"tool":37,"command":38},"bunx","bunx skills add dveyarangi\u002Fgoodwolf-harness --skill mechanism",{"tool":40,"command":41},"pnpm","pnpm dlx skills add dveyarangi\u002Fgoodwolf-harness --skill mechanism","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmechanism\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"MECHANISM-FORMAT.md","REFERENCE","参考文档",16825,"https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmechanism\u002FMECHANISM-FORMAT.md",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CDY7V9VR5DDC0TPXQRB6K1","skill-up","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.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-up\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]