[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KBGJEYXNE8A8HTGQ259B9":3,"skill-same:01M77KBGJEYXNE8A8HTGQ259B9":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},"01M77KBGJEYXNE8A8HTGQ259B9","harness",null,"Use when asked to install the harness into a project, to update a tree that already holds it, or to confirm a copy is intact; and in a freshly installed tree, which has core and none of the project's own answers yet.","dveyarangi\u002Fmeteoscape","dveyarangi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F693404?v=4","01M77KAGWZ8X0CNA092ZDNEF6T","Fima Rotter","01M77KAGXT8AD0B9SZCNM5807F",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fmeteoscape\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fharness\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: harness\ndescription: >-\n  Use when asked to install the harness into a project, to update a tree that already holds it,\n  or to confirm a copy is intact; and in a freshly installed tree, which has core and none of the\n  project's own answers yet.\n---\n\nMechanism: harness\n\nThe source is always the repository, cloned fresh at a ref; a working tree is never read. Where\nthat repository is, this tree says once:\n\nRepository: https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness.git\n\nThat is the only authored home of it. The script reads its default `--from` there, an install\nstamps a recipient's copy with the source the run actually read, and a fork edits the line once\nand everything it installs names the fork. A check or an update from another `--from` sets the\nline aside rather than reading an edit in core, as it does the local block and the block of any\nmechanism of the tree's own.\n\nRun the script from any clone of the harness, or from the tree's own copy once it has one. An\nupdate is run by the incoming ref's installer, which reads what an earlier one left: run it from\na clone, since a tree's own copy may predate handing the run on.\n\n```\npython \u003Cclone>\u002F.agents\u002Fscripts\u002Fgw\u002Fharness.py \u003Ctarget> --install [--replace-clone] [--from REPOSITORY] [--at REF]\npython \u003Cclone>\u002F.agents\u002Fscripts\u002Fgw\u002Fharness.py \u003Ctarget> --update [--overwrite] [--from REPOSITORY] [--at REF]\npython \u003Ctarget>\u002F.agents\u002Fscripts\u002Fgw\u002Fharness.py . --check [--from REPOSITORY]\npython \u003Ctarget>\u002F.agents\u002Fscripts\u002Fgw\u002Fharness.py . --links\n```\n\n`--from` defaults to the harness's own repository; `--at` to its default branch's head, and takes\na branch, a tag or a commit. To try a ref before it is pushed, pass a local clone's path as\n`--from`: its committed `HEAD` is then the ref. The target is the top level of a git work tree.\n\n`--links` is the per-clone step: the loader links are never committed, so a fresh clone of a\nproject that holds core runs it once, from the clone's own copy, with no source and no network.\nIt makes or repairs both links, names them in the clone's `.git\u002Finfo\u002Fexclude`, and reports whether\neach resolves; where the platform refuses, it prints the elevated commands and exits non-zero\nuntil they have been run.\n\n## What a run does\n\nCopies every file under `.agents\u002F` plus `AGENTS.md` and `CLAUDE.md`, the source's root\n`LICENSE` as `.agents\u002FLICENSE`, and its root `README.md` beside this skill, with the origin's local blocks removed and every straw-dog wrapper and `TODO` binding sheared so the rule stays and the question it waits on, which only this tree holds, does not;\nstamps the entry file's announce line `\u003Crepository>@\u003Cref>, \u003Cdate>`, which is the tree's only\nrevision record and what every session there announces; merges core's hooks into each host's\nshared hook file — `.claude\u002Fsettings.json`, `.codex\u002Fhooks.json`, `.cursor\u002Fhooks.json` — beside the\nproject's own, an update replacing core's entries alone; makes the loader links; installs every\nmechanism's rules and then the project's local file last; and runs the gate — the copy compared\nagainst the ref, the injector's check, the shape check, in seconds. The report ends\n`arrived: true` only when all three hold, and says beside it whether each loader link resolves.\nThe shipped suite is not run; a project that wants it runs it from its own verification set.\nWhether a host reads the link is not observable from inside a tree; the first session announcing\nthe stamped line is the evidence a person reads.\n\n## Refusals, and what to do\n\nEvery refusal writes nothing and names its step.\n\n- **A link the platform refused to create** is not a refusal: everything else landed, and the\n  report's `pending` lines are the exact commands. Present those for the hosts the person works\n  in, verbatim, to run once in an elevated prompt; once they say they have, run `--links`\n  yourself — it confirms each resolves without a source, and is never asked of the person.\n- **A folder that is not a Git repository**: empty, the install runs `git init` there first and\n  says so in its notes — every script of core reads a tree through Git, so a target is a\n  repository. Holding files of its own, it is refused with the step: where the root goes is the\n  person's decision, so they run `git init` there, or install at the root they mean.\n- **A subfolder of a repository**: refused naming the top level. Install there; one installation\n  is one tree.\n- **Git refuses the target for dubious ownership**: the `.git` directory is owned by another\n  identity than the one running — a sandbox and a shell often differ. The refusal carries Git's\n  own `safe.directory` command; the person runs it once, then the install runs again.\n- **A `\u003Cproject-local>` block in the entry file**: its content is the project's and the file is\n  overwritten. Move each fact into `local.rules.md` as a rule, delete the block, run again.\n- **A core file that differs from the announced ref**: an edit made in core. Keep it out of core\n  — a project's answer or override goes in the local file — and run `--update --overwrite`,\n  which replaces the file and names it.\n- **A file of the project's at a path the new ref adds**: refused naming it. Move it first, or\n  run `--update --overwrite`, which replaces it and names it.\n- **A tree that announces no ref**: a copy that predates this script. `--update --overwrite` is\n  required; nothing is deleted, and files under `.agents\u002F` outside the manifest are reported as\n  the project's own.\n- **The injector refused**: a malformed local file, an override naming a rule this ref no longer\n  sends there, or a local anchor a new anchor now follows — asked before the copy. Fix the local\n  file and run again.\n- **Core already here, on an install**: a previous install, whole or stopped partway.\n  `--update --overwrite` completes it.\n- **A host's hook file that is not valid JSON, or sets a key core's hooks need otherwise**: the\n  file is the project's as much as core's. Fix it by hand and run again; nothing rewrites it.\n- **A junction, a directory or a file where a link goes**: the project's own. Move it; a symlink\n  goes there.\n- **No readable `Repository:` line beside the script**: with no `--from`, the script cannot tell\n  where core comes from. Pass `--from` this once, then restore the line — it is what every later\n  run reads.\n- **A ref whose harness skill carries no such line**: not the harness, in the same sense as an\n  entry file with no announce line. Check the ref, or the repository.\n- **The source itself as target**: the origin is never installed into. A clean clone of it standing\n  where the project was meant — the person asked for an install there and the host cloned — is\n  turned into one from inside it, `harness.py . --install --replace-clone`: the tree is emptied,\n  a repository begun afresh, and core installed at the clone's commit. A clone holding anything of\n  its own — a change, an ignored file, a commit its origin's branches lack — is somebody's work and\n  is refused: install into the project's own folder instead.\n\n## Friction goes upstream\n\nFile any friction in a run — a crash, a workaround, a step this skill did not foresee — as an issue\non the harness's repository: the ref, the command, the platform, the step, the error verbatim, the\nworkaround. Nothing of the project's own. A workaround\nleft in the recipient links the issue.\n\n## After the first install\n\nThe tree has core and no answers, and its entry file arrived after this session began, so none of\nits rules are in your context: read it now — from here they govern this session, as they will\nevery next one. Write `local.rules.md` beside the entry file, in the rules-file format the entry file's *Project-local* section describes, from the environment you stand in: the\nproject's facts for the entry file, its autonomy switches, and its verification set — its\ntypechecker, its tests, every command required of landed work, read off its own toolchain, a\nproject without one having none of its own and its local file saying so; and, offered beside them,\nthe harness's checks. Then `inject_rules.py local --install`, and `--check`.\nThat check is the install's verification: the `commit` switch just written decides the install's\ncommit, as it decides any other, named in the project's own convention where it states one.\n\nThe person asked for a method to work by, not for files. Before asking anything, introduce it in\ntheir language, in a few lines: who you now are to them, what you will do for them, and where you\nstop for their yes. Ask each answer with the reason a project would choose it, in their terms —\n*commit on my own once the checks pass, or ask each time* — never as a switch's name and values;\nthe origin's own answers, read in its clone, are not this project's and are offered as no default.\nThe harness's checks\nare two kinds: those of the records the method keeps — `tickets.py`, `questions.py`, `edges.py`,\n`product.py`, `maintain.py` — serve every project that works by it; those of core itself — `mechanisms.py`,\n`inject_rules.py` — serve a project that means to change the harness. End with the first question the work asks. What was copied, gated and registered stays in the\nfiles and the commit, said on request.\n\n`uv run --offline --no-project python` is the harness's own habit; the scripts need only the\nstandard library, so a bare `python` works.\n","Mechanism: harness\n\nThe source is always the repository, cloned fresh at a ref; a working tree is never read. Where\nthat repository is, this tree says once:\n\nRepository: https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness.git\n\nThat is the only authored home of it. The script reads its default `--from` there, an install\nstamps a recipient's copy with the source the run actually read, and a fork edits the line once\nand everything it installs names the fork. A check or an update from another `--from` sets the\nline aside rather than reading an edit in core, as it does the local block and the block of any\nmechanism of the tree's own.\n\nRun the script from any clone of the harness, or from the tree's own copy once it has one. An\nupdate is run by the incoming ref's installer, which reads what an earlier one left: run it from\na clone, since a tree's own copy may predate handing the run on.\n\n```\npython \u003Cclone>\u002F.agents\u002Fscripts\u002Fgw\u002Fharness.py \u003Ctarget> --install [--replace-clone] [--from REPOSITORY] [--at REF]\npython \u003Cclone>\u002F.agents\u002Fscripts\u002Fgw\u002Fharness.py \u003Ctarget> --update [--overwrite] [--from REPOSITORY] [--at REF]\npython \u003Ctarget>\u002F.agents\u002Fscripts\u002Fgw\u002Fharness.py . --check [--from REPOSITORY]\npython \u003Ctarget>\u002F.agents\u002Fscripts\u002Fgw\u002Fharness.py . --links\n```\n\n`--from` defaults to the harness's own repository; `--at` to its default branch's head, and takes\na branch, a tag or a commit. To try a ref before it is pushed, pass a local clone's path as\n`--from`: its committed `HEAD` is then the ref. The target is the top level of a git work tree.\n\n`--links` is the per-clone step: the loader links are never committed, so a fresh clone of a\nproject that holds core runs it once, from the clone's own copy, with no source and no network.\nIt makes or repairs both links, names them in the clone's `.git\u002Finfo\u002Fexclude`, and reports whether\neach resolves; where the platform refuses, it prints the elevated commands and exits non-zero\nuntil they have been run.\n\n## What a run does\n\nCopies every file under `.agents\u002F` plus `AGENTS.md` and `CLAUDE.md`, the source's root\n`LICENSE` as `.agents\u002FLICENSE`, and its root `README.md` beside this skill, with the origin's local blocks removed and every straw-dog wrapper and `TODO` binding sheared so the rule stays and the question it waits on, which only this tree holds, does not;\nstamps the entry file's announce line `\u003Crepository>@\u003Cref>, \u003Cdate>`, which is the tree's only\nrevision record and what every session there announces; merges core's hooks into each host's\nshared hook file — `.claude\u002Fsettings.json`, `.codex\u002Fhooks.json`, `.cursor\u002Fhooks.json` — beside the\nproject's own, an update replacing core's entries alone; makes the loader links; installs every\nmechanism's rules and then the project's local file last; and runs the gate — the copy compared\nagainst the ref, the injector's check, the shape check, in seconds. The report ends\n`arrived: true` only when all three hold, and says beside it whether each loader link resolves.\nThe shipped suite is not run; a project that wants it runs it from its own verification set.\nWhether a host reads the link is not observable from inside a tree; the first session announcing\nthe stamped line is the evidence a person reads.\n\n## Refusals, and what to do\n\nEvery refusal writes nothing and names its step.\n\n- **A link the platform refused to create** is not a refusal: everything else landed, and the\n  report's `pending` lines are the exact commands. Present those for the hosts the person works\n  in, verbatim, to run once in an elevated prompt; once they say they have, run `--links`\n  yourself — it confirms each resolves without a source, and is never asked of the person.\n- **A folder that is not a Git repository**: empty, the install runs `git init` there first and\n  says so in its notes — every script of core reads a tree through Git, so a target is a\n  repository. Holding files of its own, it is refused with the step: where the root goes is the\n  person's decision, so they run `git init` there, or install at the root they mean.\n- **A subfolder of a repository**: refused naming the top level. Install there; one installation\n  is one tree.\n- **Git refuses the target for dubious ownership**: the `.git` directory is owned by another\n  identity than the one running — a sandbox and a shell often differ. The refusal carries Git's\n  own `safe.directory` command; the person runs it once, then the install runs again.\n- **A `\u003Cproject-local>` block in the entry file**: its content is the project's and the file is\n  overwritten. Move each fact into `local.rules.md` as a rule, delete the block, run again.\n- **A core file that differs from the announced ref**: an edit made in core. Keep it out of core\n  — a project's answer or override goes in the local file — and run `--update --overwrite`,\n  which replaces the file and names it.\n- **A file of the project's at a path the new ref adds**: refused naming it. Move it first, or\n  run `--update --overwrite`, which replaces it and names it.\n- **A tree that announces no ref**: a copy that predates this script. `--update --overwrite` is\n  required; nothing is deleted, and files under `.agents\u002F` outside the manifest are reported as\n  the project's own.\n- **The injector refused**: a malformed local file, an override naming a rule this ref no longer\n  sends there, or a local anchor a new anchor now follows — asked before the copy. Fix the local\n  file and run again.\n- **Core already here, on an install**: a previous install, whole or stopped partway.\n  `--update --overwrite` completes it.\n- **A host's hook file that is not valid JSON, or sets a key core's hooks need otherwise**: the\n  file is the project's as much as core's. Fix it by hand and run again; nothing rewrites it.\n- **A junction, a directory or a file where a link goes**: the project's own. Move it; a symlink\n  goes there.\n- **No readable `Repository:` line beside the script**: with no `--from`, the script cannot tell\n  where core comes from. Pass `--from` this once, then restore the line — it is what every later\n  run reads.\n- **A ref whose harness skill carries no such line**: not the harness, in the same sense as an\n  entry file with no announce line. Check the ref, or the repository.\n- **The source itself as target**: the origin is never installed into. A clean clone of it standing\n  where the project was meant — the person asked for an install there and the host cloned — is\n  turned into one from inside it, `harness.py . --install --replace-clone`: the tree is emptied,\n  a repository begun afresh, and core installed at the clone's commit. A clone holding anything of\n  its own — a change, an ignored file, a commit its origin's branches lack — is somebody's work and\n  is refused: install into the project's own folder instead.\n\n## Friction goes upstream\n\nFile any friction in a run — a crash, a workaround, a step this skill did not foresee — as an issue\non the harness's repository: the ref, the command, the platform, the step, the error verbatim, the\nworkaround. Nothing of the project's own. A workaround\nleft in the recipient links the issue.\n\n## After the first install\n\nThe tree has core and no answers, and its entry file arrived after this session began, so none of\nits rules are in your context: read it now — from here they govern this session, as they will\nevery next one. Write `local.rules.md` beside the entry file, in the rules-file format the entry file's *Project-local* section describes, from the environment you stand in: the\nproject's facts for the entry file, its autonomy switches, and its verification set — its\ntypechecker, its tests, every command required of landed work, read off its own toolchain, a\nproject without one having none of its own and its local file saying so; and, offered beside them,\nthe harness's checks. Then `inject_rules.py local --install`, and `--check`.\nThat check is the install's verification: the `commit` switch just written decides the install's\ncommit, as it decides any other, named in the project's own convention where it states one.\n\nThe person asked for a method to work by, not for files. Before asking anything, introduce it in\ntheir language, in a few lines: who you now are to them, what you will do for them, and where you\nstop for their yes. Ask each answer with the reason a project would choose it, in their terms —\n*commit on my own once the checks pass, or ask each time* — never as a switch's name and values;\nthe origin's own answers, read in its clone, are not this project's and are offered as no default.\nThe harness's checks\nare two kinds: those of the records the method keeps — `tickets.py`, `questions.py`, `edges.py`,\n`product.py`, `maintain.py` — serve every project that works by it; those of core itself — `mechanisms.py`,\n`inject_rules.py` — serve a project that means to change the harness. End with the first question the work asks. What was copied, gated and registered stays in the\nfiles and the commit, said on request.\n\n`uv run --offline --no-project python` is the harness's own habit; the scripts need only the\nstandard library, so a bare `python` works.\n",{"name":5,"description":7},"main","d2bf1c688554a199b2433460c08378a28c368373",".agents\u002Fskills\u002Fharness","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fmeteoscape","https:\u002F\u002Fgithub.com\u002Fdveyarangi","http:\u002F\u002Fdveyarangi.blogspot.com\u002F","2026-10-14 08:50:21",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add dveyarangi\u002Fmeteoscape --skill harness",{"tool":37,"command":38},"bunx","bunx skills add dveyarangi\u002Fmeteoscape --skill harness",{"tool":40,"command":41},"pnpm","pnpm dlx skills add dveyarangi\u002Fmeteoscape --skill harness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fmeteoscape\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fharness\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"README.md","REFERENCE","参考文档",15543,"https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fmeteoscape\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fharness\u002FREADME.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},"01M77KD67QK512NQZZ0KG710E7","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. Repair-and-report where that policy holds.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fmeteoscape\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},"01M77KD3YKE65N7D472BJAQAGW","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\u002Fmeteoscape\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},"01M77KCZCEZJVQ8YV739MHA5YB","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\u002Fmeteoscape\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},"01M77KCW8EYKHZ0HWCGN9FTQP3","spec","Use to develop a spec for substantial work through \u002Falign, then hand off to \u002Fticket. Use when a change needs agreed scope, behavior, boundaries and testing before decomposition. An existing spec for the work is developed in place.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fmeteoscape\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspec\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},"01M77KCRGB1CFTZJ39P7RGSKQ8","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\u002Fmeteoscape\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-up\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},"01M77KCK8PEVY9Z2PJ38ERGZQH","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\u002Fmeteoscape\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-devops\u002FSKILL.md",[],[]]