[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MYTE9DRC219EM8K48PDRW":3,"skill-same:01M77MYTE9DRC219EM8K48PDRW":58},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M77MYTE9DRC219EM8K48PDRW","setup",null,"Report where verification artifacts land and write the repository's docs\u002Fconventions\u002Fverification.yaml settings. check (read-only) names the memory root the verification skills resolve and validates the settings file; apply writes the keys its arguments name, proof_level, live_workers or both, after confirmation. Use when: 'set up verification', 'configure the verification plugin', 'is verification configured', 'verification setup', 'where do verification manifests \u002F baselines land', 'set the proof level for this repo', 'set live workers for this repo'. Actions: check (read-only, default) | apply [proof_level=VALUE] [live_workers=N]. Re-runnable.","melodic-software\u002Fclaude-code-plugins","melodic-software","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F58273638?v=4","01M77JVQTXNGKCE4MDFY2BC936","Melodic Software","01M77JVQVN9QDWKAH6W03ANP76",30,"MIT","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fverification\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Report where verification artifacts land and write the repository's docs\u002Fconventions\u002Fverification.yaml settings. check (read-only) names the memory root the verification skills resolve and validates the settings file; apply writes the keys its arguments name, proof_level, live_workers or both, after confirmation. Use when: 'set up verification', 'configure the verification plugin', 'is verification configured', 'verification setup', 'where do verification manifests \u002F baselines land', 'set the proof level for this repo', 'set live workers for this repo'. Actions: check (read-only, default) | apply [proof_level=VALUE] [live_workers=N]. Re-runnable.\"\nargument-hint: \"[check|apply] [proof_level=\u003Cpath|live|strict>] [live_workers=\u003Cn>]\"\nuser-invocable: true\ndisable-model-invocation: true\n---\n\n## Purpose\n\nArtifact placement is fixed by the plugin's lifecycle artifact protocol\n([`${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fartifact-protocol.md`](${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fartifact-protocol.md)):\n`\u002Fverification:confirm` writes its evidence manifest and `\u002Fverification:measure` its baselines and\nraw captures into the memory slice `\u003Cmemory_dir>\u002F\u003Cslug>\u002F`, never committed. `\u003Cmemory_dir>` is `.work\u002F`\nunless the project's own instructions declare another root. Nothing about placement is configured.\n\nThe plugin owns one tracked settings file, `docs\u002Fconventions\u002Fverification.yaml`, the repository\nlayer of its settings, `proof_level` and `live_workers=\u003Cn>` (values, layers and the level rules:\n[`${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fconfig.md`](${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fconfig.md); schema:\n`${CLAUDE_PLUGIN_ROOT}\u002Fschemas\u002Fverification.schema.json`). `check` reports it; `apply` writes it\nonly when the operator names the key or asks to set the proof level. Idempotent: re-running reads\nthe current state again.\n\n## `check` (read-only)\n\nReport a PASS\u002FINFO\u002FWARN table. Do not write anything.\n\n1. **Memory root.** Look for a working-docs root declared in the repo's own `CLAUDE.md`, `AGENTS.md`,\n   or `.claude\u002Frules`. Report the declared root, or `.work\u002F` when none is declared, as INFO.\n2. **Ignore state.** Run `git check-ignore -v \u003Cmemory_dir>\u002Fprobe\u002Fbaselines\u002Fx` on a representative\n   file path (a bare directory misses `**` patterns). A match is PASS and names the rule. No match is\n   INFO: the memory root's own self-ignoring `.gitignore` is created by the first memory-slice\n   write, announced, so an absent guard before any run is expected.\n3. **Settings file.** Run `node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" --check` from the\n   project root and add each line it prints with its own prefix: INFO when the file is absent\n   (`proof_level` and `live_workers` come from `userConfig` or their defaults), PASS with each\n   key's value when it validates, WARN when it does not (a `proof_level` outside `path`, `live`,\n   `strict`, a `live_workers` that is not a whole number of at least 1, a key set twice, an empty\n   value, null, a key the schema does not list, a file that does not parse, a list or map, a\n   symlink or hard link), quoting the file, key and value. A key the schema does not list is\n   ignored: the other keys keep their PASS lines, so a valid `proof_level` floor beside it counts.\n   A WARN never stops `\u002Fverification:confirm`: it names the value,\n   drops the layer and resolves that key's default (`path`, `1`). `apply` is the fix. `\u002Fverification:confirm` reads the default\n   branch's committed copy, so say that a working-tree value takes effect once it is merged there.\n\n## `apply`\n\n1. **Resolve the values.** Take each key the arguments name, `proof_level`, `live_workers` or\n   both, and use a complete `\u003Ckey>=\u003Cvalue>` as given. For each named key without a value, ask once,\n   recommendation first:\n   - `proof_level`: `path`, the default, unless the team wants every runnable change driven live\n     (`live`) or per-phase unit, live and performance proof (`strict`). Before recommending `live`\n     or `strict`, say that a member on an older verification release does not read this file, so\n     the level only holds once every member has upgraded.\n   - `live_workers`: `1`, the default, unless the team wants the live drive split across workers\n     by feature-map entry point.\n\n   Never invent a key the schema does not list, and never adjust a value: the script decides\n   whether it is allowed.\n2. **Write.** One call carrying every resolved key, each `\u003Ckey>=\u003Cvalue>` as one quoted argument:\n\n   ```bash\n   node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" \"proof_level=live\"\n   node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" \"live_workers=3\"\n   node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" \"proof_level=live\" \"live_workers=3\"\n   ```\n\n   Pass a key the operator accepts at the plugin default as `--default \u003Ckey>` instead of\n   `\u003Ckey>=\u003Cvalue>`, so a later change to that default reaches it; `\u003Ckey>=\u003Cvalue>` records the\n   team's choice, which the script never changes. The script also records `written_against` and\n   `provenance:`, so a file with no record, or one written against another plugin version, shows a\n   diff even when no value changes.\n\n   The script checks each value against the schema (`live_workers` takes an unquoted whole number\n   of at least 1, so `0`, `1.5` and `'2'` are refused), refuses a key given twice, validates the\n   existing file, and validates the whole resulting document before it writes. In the existing file\n   it overwrites only a value outside the key's values, an empty value or null; it refuses a key set\n   twice, a map or list in block or flow form, an empty quoted string, an unknown key set twice or\n   holding a map or list, or a file that does not parse; any other unknown key is named in one\n   warning and its line kept as written. It writes only\n   `\u003Cgit toplevel>\u002Fdocs\u002Fconventions\u002Fverification.yaml`. It resolves a symlinked root first, then\n   refuses a root that is `$HOME` or an ancestor of it, a symlinked `docs`, `docs\u002Fconventions` or\n   target, a hard-linked target, or a `docs\u002Fconventions` that resolves outside the repository,\n   checked again before each directory it creates and right before the write. Every refusal is\n   one line, exits 1 and leaves the file as it\n   was; a failed write removes only its own temp file. A missing file is created; a value already\n   in place prints `already configured`.\n3. **An existing file that would change** exits 3 and prints a unified diff without writing. Show\n   the operator that diff and ask whether to write it. Only on an explicit yes, re-run the same call\n   with `--yes`; on anything else, stop with the file unchanged.\n   When the convention-home offer prints below the diff, ask about it too (the next step) before\n   any re-run, since `--yes` writes both.\n4. **The convention-home offer.** When the repository's `AGENTS.md` or `CLAUDE.md` binds no\n   convention home, the script prints an offer: with the operator's confirmation it adds a\n   convention-home pointer region to that instruction file (creating `AGENTS.md` when neither\n   exists or `CLAUDE.md` only imports it) and the personal override ignore line\n   `docs\u002Fconventions\u002F**\u002F*.local.*` to `.gitignore`, the only files `apply` writes outside\n   `docs\u002Fconventions\u002F`. It prints the offer at the end of an exit 0 run and below the diff of an\n   exit 3 run, so show the operator stdout on exit 0 too. Ask whether to add the region and the\n   ignore line. Only on an explicit yes, re-run the same call with `--yes`, which also writes any\n   diff shown with it. On a no, run `node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" --decline`\n   alone: it records the decline in the instruction file, and the next run does not offer again.\n   To write a shown diff without the region, run `--decline` first, then the same call with\n   `--yes`. When the instruction file or `.gitignore` is a symlink or hard link the script will\n   not write through, it prints a one-line refusal in place of the offer, with the same exit\n   code: show it, and do not re-run with `--yes`, which that refusal stops with exit 1. A refused\n   instruction file refuses `--decline` too, so the operator fixes the link or adds the region by\n   hand.\n5. **Verify.** Re-run the settings-file `check` row and report the value it prints, not the value\n   written. Then run `git check-ignore -v docs\u002Fconventions\u002Fverification.yaml` (a match is FAIL with\n   the pattern) and `git ls-files --error-unmatch docs\u002Fconventions\u002Fverification.yaml` (non-zero\n   right after a fresh write means \"written but untracked: commit it to share with the team\").\n\n## Output\n\nThe `check` table. After `apply`: the diff shown, the written path, the value `check` reads back\nfor each key written, and whether the file is tracked.\n\n## Next\n\n`\u002Fverification:confirm`, which resolves `proof_level` from this file on the default branch.\n\n## What this skill does NOT do\n\n- Run a verification pass. That is the plugin's verification skills (`\u002Fverification:confirm`,\n  `\u002Fverification:measure`).\n- Write any settings file other than `docs\u002Fconventions\u002Fverification.yaml`, edit any ignore file\n  beyond the personal override line the operator confirms in the convention-home offer, or write the plugin directory or the plugin data directory (`${CLAUDE_PLUGIN_DATA}` is for caches\n  and generated state only).\n- Write Claude Code user settings or `pluginConfigs`. The per-user `proof_level` and\n  `live_workers` options are set through `\u002Fplugin configure`, not here.\n","## Purpose\n\nArtifact placement is fixed by the plugin's lifecycle artifact protocol\n([`${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fartifact-protocol.md`](${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fartifact-protocol.md)):\n`\u002Fverification:confirm` writes its evidence manifest and `\u002Fverification:measure` its baselines and\nraw captures into the memory slice `\u003Cmemory_dir>\u002F\u003Cslug>\u002F`, never committed. `\u003Cmemory_dir>` is `.work\u002F`\nunless the project's own instructions declare another root. Nothing about placement is configured.\n\nThe plugin owns one tracked settings file, `docs\u002Fconventions\u002Fverification.yaml`, the repository\nlayer of its settings, `proof_level` and `live_workers=\u003Cn>` (values, layers and the level rules:\n[`${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fconfig.md`](${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fconfig.md); schema:\n`${CLAUDE_PLUGIN_ROOT}\u002Fschemas\u002Fverification.schema.json`). `check` reports it; `apply` writes it\nonly when the operator names the key or asks to set the proof level. Idempotent: re-running reads\nthe current state again.\n\n## `check` (read-only)\n\nReport a PASS\u002FINFO\u002FWARN table. Do not write anything.\n\n1. **Memory root.** Look for a working-docs root declared in the repo's own `CLAUDE.md`, `AGENTS.md`,\n   or `.claude\u002Frules`. Report the declared root, or `.work\u002F` when none is declared, as INFO.\n2. **Ignore state.** Run `git check-ignore -v \u003Cmemory_dir>\u002Fprobe\u002Fbaselines\u002Fx` on a representative\n   file path (a bare directory misses `**` patterns). A match is PASS and names the rule. No match is\n   INFO: the memory root's own self-ignoring `.gitignore` is created by the first memory-slice\n   write, announced, so an absent guard before any run is expected.\n3. **Settings file.** Run `node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" --check` from the\n   project root and add each line it prints with its own prefix: INFO when the file is absent\n   (`proof_level` and `live_workers` come from `userConfig` or their defaults), PASS with each\n   key's value when it validates, WARN when it does not (a `proof_level` outside `path`, `live`,\n   `strict`, a `live_workers` that is not a whole number of at least 1, a key set twice, an empty\n   value, null, a key the schema does not list, a file that does not parse, a list or map, a\n   symlink or hard link), quoting the file, key and value. A key the schema does not list is\n   ignored: the other keys keep their PASS lines, so a valid `proof_level` floor beside it counts.\n   A WARN never stops `\u002Fverification:confirm`: it names the value,\n   drops the layer and resolves that key's default (`path`, `1`). `apply` is the fix. `\u002Fverification:confirm` reads the default\n   branch's committed copy, so say that a working-tree value takes effect once it is merged there.\n\n## `apply`\n\n1. **Resolve the values.** Take each key the arguments name, `proof_level`, `live_workers` or\n   both, and use a complete `\u003Ckey>=\u003Cvalue>` as given. For each named key without a value, ask once,\n   recommendation first:\n   - `proof_level`: `path`, the default, unless the team wants every runnable change driven live\n     (`live`) or per-phase unit, live and performance proof (`strict`). Before recommending `live`\n     or `strict`, say that a member on an older verification release does not read this file, so\n     the level only holds once every member has upgraded.\n   - `live_workers`: `1`, the default, unless the team wants the live drive split across workers\n     by feature-map entry point.\n\n   Never invent a key the schema does not list, and never adjust a value: the script decides\n   whether it is allowed.\n2. **Write.** One call carrying every resolved key, each `\u003Ckey>=\u003Cvalue>` as one quoted argument:\n\n   ```bash\n   node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" \"proof_level=live\"\n   node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" \"live_workers=3\"\n   node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" \"proof_level=live\" \"live_workers=3\"\n   ```\n\n   Pass a key the operator accepts at the plugin default as `--default \u003Ckey>` instead of\n   `\u003Ckey>=\u003Cvalue>`, so a later change to that default reaches it; `\u003Ckey>=\u003Cvalue>` records the\n   team's choice, which the script never changes. The script also records `written_against` and\n   `provenance:`, so a file with no record, or one written against another plugin version, shows a\n   diff even when no value changes.\n\n   The script checks each value against the schema (`live_workers` takes an unquoted whole number\n   of at least 1, so `0`, `1.5` and `'2'` are refused), refuses a key given twice, validates the\n   existing file, and validates the whole resulting document before it writes. In the existing file\n   it overwrites only a value outside the key's values, an empty value or null; it refuses a key set\n   twice, a map or list in block or flow form, an empty quoted string, an unknown key set twice or\n   holding a map or list, or a file that does not parse; any other unknown key is named in one\n   warning and its line kept as written. It writes only\n   `\u003Cgit toplevel>\u002Fdocs\u002Fconventions\u002Fverification.yaml`. It resolves a symlinked root first, then\n   refuses a root that is `$HOME` or an ancestor of it, a symlinked `docs`, `docs\u002Fconventions` or\n   target, a hard-linked target, or a `docs\u002Fconventions` that resolves outside the repository,\n   checked again before each directory it creates and right before the write. Every refusal is\n   one line, exits 1 and leaves the file as it\n   was; a failed write removes only its own temp file. A missing file is created; a value already\n   in place prints `already configured`.\n3. **An existing file that would change** exits 3 and prints a unified diff without writing. Show\n   the operator that diff and ask whether to write it. Only on an explicit yes, re-run the same call\n   with `--yes`; on anything else, stop with the file unchanged.\n   When the convention-home offer prints below the diff, ask about it too (the next step) before\n   any re-run, since `--yes` writes both.\n4. **The convention-home offer.** When the repository's `AGENTS.md` or `CLAUDE.md` binds no\n   convention home, the script prints an offer: with the operator's confirmation it adds a\n   convention-home pointer region to that instruction file (creating `AGENTS.md` when neither\n   exists or `CLAUDE.md` only imports it) and the personal override ignore line\n   `docs\u002Fconventions\u002F**\u002F*.local.*` to `.gitignore`, the only files `apply` writes outside\n   `docs\u002Fconventions\u002F`. It prints the offer at the end of an exit 0 run and below the diff of an\n   exit 3 run, so show the operator stdout on exit 0 too. Ask whether to add the region and the\n   ignore line. Only on an explicit yes, re-run the same call with `--yes`, which also writes any\n   diff shown with it. On a no, run `node \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fsetup-apply.mjs\" --decline`\n   alone: it records the decline in the instruction file, and the next run does not offer again.\n   To write a shown diff without the region, run `--decline` first, then the same call with\n   `--yes`. When the instruction file or `.gitignore` is a symlink or hard link the script will\n   not write through, it prints a one-line refusal in place of the offer, with the same exit\n   code: show it, and do not re-run with `--yes`, which that refusal stops with exit 1. A refused\n   instruction file refuses `--decline` too, so the operator fixes the link or adds the region by\n   hand.\n5. **Verify.** Re-run the settings-file `check` row and report the value it prints, not the value\n   written. Then run `git check-ignore -v docs\u002Fconventions\u002Fverification.yaml` (a match is FAIL with\n   the pattern) and `git ls-files --error-unmatch docs\u002Fconventions\u002Fverification.yaml` (non-zero\n   right after a fresh write means \"written but untracked: commit it to share with the team\").\n\n## Output\n\nThe `check` table. After `apply`: the diff shown, the written path, the value `check` reads back\nfor each key written, and whether the file is tracked.\n\n## Next\n\n`\u002Fverification:confirm`, which resolves `proof_level` from this file on the default branch.\n\n## What this skill does NOT do\n\n- Run a verification pass. That is the plugin's verification skills (`\u002Fverification:confirm`,\n  `\u002Fverification:measure`).\n- Write any settings file other than `docs\u002Fconventions\u002Fverification.yaml`, edit any ignore file\n  beyond the personal override line the operator confirms in the convention-home offer, or write the plugin directory or the plugin data directory (`${CLAUDE_PLUGIN_DATA}` is for caches\n  and generated state only).\n- Write Claude Code user settings or `pluginConfigs`. The per-user `proof_level` and\n  `live_workers` options are set through `\u002Fplugin configure`, not here.\n",{"description":7,"argument-hint":24,"user-invocable":25,"disable-model-invocation":25},"[check|apply] [proof_level=\u003Cpath|live|strict>] [live_workers=\u003Cn>]",true,"main","d0e68c3f36b92a1d6381f0ba0060d7a0b8b886c5","plugins\u002Fverification\u002Fskills\u002Fsetup",7,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins","https:\u002F\u002Fgithub.com\u002Fmelodic-software","https:\u002F\u002Fmelodicsoftware.com","Independent software studio building developer tools, automation, and application services, with roots in music.","2026-11-15 05:15:06",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":41,"command":42},"bunx","bunx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":44,"command":45},"pnpm","pnpm dlx skills add melodic-software\u002Fclaude-code-plugins --skill setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fverification\u002Fskills\u002Fsetup\u002FSKILL.md",[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fsetup-apply.mjs","SCRIPT","脚本",823,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fverification\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup-apply.mjs",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fsetup-apply.test.sh",42270,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fverification\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup-apply.test.sh",[59,66,73,80,85,92],{"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},"01M7DYYDG31B9YX7N9MB9QW2GW","track","Backlog reads through the bound tracker: search open and closed items, view one item with its comments and state history. Use when another skill searches or reads tracker items.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsession-flow\u002Fevals\u002Frecall-still-reports-reopened-bug\u002Fwork-items-stub\u002Fskills\u002Ftrack\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},"01M7DYXVBAVG3NV30PA7GKW9Q6","reviewer-media","Reviewer media for one pull request: decides whether it needs a narrated walkthrough, builds the storyboard from \u002Freview:explain-change's digest, has \u002Fexplainer-video:produce render it and hands the manifest to \u002Fsource-control:pull-request media. Use when asked for 'reviewer media', 'a walkthrough video for this PR', 'a produced video of this change', or when pull-request ready or monitor hands a PR over.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview\u002Fskills\u002Freviewer-media\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},"01M7DYRZ5YD44AMYH26YR25GZ8","route","Model and effort per agent role (orchestrator, worker, verifier, retrieval) for a multi-agent run, resolved through the bundled defaults and the user, team and personal override config layers into fenced JSON with single-agent and fan-out variants and the layer behind each value. Use when asked 'which model for the subagents', 'route the roles' or 'model routing', or before a skill passes a role's model on a spawn.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fevals\u002Fex-model-pin-without-override\u002Fmulti-agent-stub\u002Fskills\u002Froute\u002FSKILL.md",[],[],{"skillNo":81,"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":82,"categories":83,"keywords":84,"publishedAt":19},"01M7DYRTVT4FWTGDJY0HCCFJMZ","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fevals\u002Fex-model-override-from-route\u002Fmulti-agent-stub\u002Fskills\u002Froute\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7DYNZC8PNW3T27V2ADKECKJ","principles","Module-design vocabulary for architecture findings, and the checks built on it. Use when: 'what is a deep module', 'what is a seam', 'deep vs shallow module', 'what is the deletion test', 'leverage and locality', 'module design vocabulary', 'which word do we use for X in architecture findings'. Scanning a codebase for friction is \u002Farchitecture:improve.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchitecture\u002Fskills\u002Fprinciples\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7DYNMCZNEWBFHV9KTSS6H60","write","Structured five-field bug report (title, steps to reproduce, expected vs actual, justified severity, suggested fix location) from an informal description, read-only. Use when the user names a defect they observed, or asks for one written up ('report a bug', 'file a bug', 'write this up as a bug').","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchitecture\u002Fevals\u002Fdeepening-defect-goes-to-bugs-write\u002Fbugs-stub\u002Fskills\u002Fwrite\u002FSKILL.md",[],[]]