[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DMAENSXPJJPWTRA9CMBV0":3,"skill-same:01M79DMAENSXPJJPWTRA9CMBV0":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M79DMAENSXPJJPWTRA9CMBV0","migrate",null,"Move this project's knowledge base from the layered layout (01_adr, 02_modules, 03_features, 04_domain, 05_screens and the surface roster) to the concept layout under inspire_kb\u002F01_spec\u002F, where every artifact has a typed extension, and convert its [[wikilinks]] to relative Markdown links. Run once, on purpose, after \u002Finspire:update reports the layered layout or counts wikilinks. Rebuilds nothing that is already built.","Genomcore\u002Finspire","Genomcore","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F67845649?v=4","01M79DGNHB5DVE1Q8TC7F3K4FY","01M79DGNM14QF64G5NWT5X00SY",0,"MIT","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fmigrate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: migrate\ndescription: \"Move this project's knowledge base from the layered layout (01_adr, 02_modules, 03_features, 04_domain, 05_screens and the surface roster) to the concept layout under inspire_kb\u002F01_spec\u002F, where every artifact has a typed extension, and convert its [[wikilinks]] to relative Markdown links. Run once, on purpose, after \u002Finspire:update reports the layered layout or counts wikilinks. Rebuilds nothing that is already built.\"\n---\n\n# \u002Finspire:migrate — the KB by concept\n\nINSPIRE 0.15.0 reads the specification only from `inspire_kb\u002F01_spec\u002F`, where every\nartifact is found by its typed extension (`.module.md`, `.feature.md`, `.entity.md`,\n`.action.md`, `.adr.md`, `.bundle.md`, `.face.md`, `.screen.md`, `.process.md`…).\nThis skill moves a KB written in the layered layout there, once. It is the only\nstep that moves anything in `inspire_kb\u002F`: `\u002Finspire:update` never does\n([`adr-kb-structure`](https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fdocs\u002Fadr\u002Fadr-kb-structure.md)\nD10).\n\nFrom 0.17.0 a KB link is a relative Markdown link to the target file,\n`[adr-audit](..\u002F..\u002F_adr\u002Faudit.adr.md)`. The skill converts every `[[wikilink]]` in\nits own step\n([`adr-markdown-links`](https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fdocs\u002Fadr\u002Fadr-markdown-links.md)\nD6). A KB already on the concept layout that still holds wikilinks starts at\nStep 4: its links are converted and nothing moves.\n\n**What it never does:** rename a module, an entity or an action; change any id but a\nscreen's; point a link at a different file; extract a shared screen into a pattern;\ncreate a process, or a bundle with an artifact of its own; write to git.\nEvery screen id it changes goes into `inspire_kb\u002F01_spec\u002F_migration\u002Fid-map.json`,\nwhich INSPIRE Factory 0.16.0 or later reads to rewrite the built code instead of\nrebuilding it.\n\n## Preconditions\n\n1. The runtime is already on 0.15.0 or later (`\u002Finspire:update` has run). The\n   validators and skills of this version read only `01_spec\u002F`.\n2. `jq` and `yq` (Mike Farah v4) are on `PATH`.\n3. **A clean working tree.** If `git status --porcelain` is non-empty, stop and ask the\n   operator to commit or stash first: the moves must be committed on their own, before\n   any edit, so git records them as renames and the history of every file survives.\n\n## Step 1 — Dry run, and the questions it asks\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmigrate-kb.sh\" --dry-run --kb inspire_kb\n```\n\nIt prints the plan, one tab-separated line per step (`move`, `write`, `idmap`,\n`unplaced`, `config`, `note`), and writes nothing. A `config` line names a file outside\nthe KB, `.inspire\u002Femanate.yml` or `.inspire\u002Femanate.json`, and the change to its spec\nroot, which moves to `inspire_kb\u002F01_spec`. Step 2 also prints a `seed` line for each\nskeleton file `--skeleton` adds. When it needs an answer it prints `ask` lines\ninstead and exits 3. Ask the operator each one, in their words, then run the dry run\nagain with the answers as flags:\n\n| `ask` key | Question | Flag |\n|---|---|---|\n| `face` | No roster, but there are screens: every screen moves to one face. What is its id? Propose the project's name in kebab-case. | `--face ID` |\n| `bundle` | No roster: every module is exposed by one bundle. What is its id (propose `api`), and which package exposes it (`source_root`-relative, for example `apps\u002Fapi`)? | `--bundle ID --bundle-package PATH` |\n| `bundle-modules:{id}` | The roster has several headless surfaces: which modules does `{id}` serve? Read the ADR that partitions them if there is one, and propose it. | `--bundle-modules {id}=m1,m2` |\n| `lib:{id}` | The lib surface `{id}`: does it become a bundle (a package with code of its own) or part of the design system (a UI kit)? | `--lib {id}=bundle` or `--lib {id}=design-system` |\n| `shared-face` | `05_screens\u002Fshared\u002F` holds screens two faces use. Which face keeps them? Nothing is extracted; each other face can add its own screen later. | `--shared-face ID` |\n\nNever answer a question yourself: these are specification decisions.\n\n**Relay the plan grouped:** how many files move per kind, every screen id that changes\n(the `idmap` lines, old → new), every file it cannot place (`unplaced`: moved under\n`_migration\u002Funplaced\u002F`, never dropped), every `config` change and every `note`. Add how many wikilinks\nthe KB holds outside code:\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmigrate-links.sh\" --count --kb inspire_kb\n```\n\nAsk the operator to confirm before Step 2.\n\n## Step 2 — Migrate\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmigrate-kb.sh\" --kb inspire_kb {the same answer flags} \\\n  --skeleton \"${CLAUDE_PLUGIN_ROOT}\u002Fbase\u002Fkb\u002F01_spec\"\n```\n\n`--skeleton` adds the READMEs, the starter patterns and the default theme the layered\nlayout never had, and seeds `design-system.md` from the theme if the project had none —\nonly where nothing is on disk. The plan it applied is saved to\n`inspire_kb\u002F01_spec\u002F_migration\u002Fplan.tsv`.\n\nIt refuses, and moves nothing, when:\n\n- `01_spec\u002F` already exists beside layered directories (a half-migrated KB) — find out\n  what put it there before going on;\n- a screen id is used by more than one screen — the id map would be ambiguous. Run\n  `.inspire\u002Fbin\u002Fscreen-coherence.sh` on the old tree with the previous runtime, or\n  fix the duplicate by hand, and run again.\n\nA second run on a migrated KB is a no-op.\n\n## Step 3 — Commit the moves on their own\n\nTell the operator to commit now, before any edit:\n\n```bash\ngit add -A && git commit -m \"chore(kb): move the KB to 01_spec (\u002Finspire:migrate)\"\n```\n\nThe tree was clean before Step 2, so every change is the run's: the KB, and the file of\neach `config` line. `git status --porcelain` is empty afterwards; the Factory's remap\nrefuses a dirty checkout. Do not commit for them unless they ask you to. Step 4 waits\nfor this commit.\n\n## Step 4 — Convert the links\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmigrate-links.sh\" --dry-run --kb inspire_kb\n```\n\nIt prints one `link` line per link it converts (file, line, the source that resolved\nit, the wikilink, the Markdown link), one `draft` or `unlinked` line per link it\nsettles, and writes nothing. A link resolves through, in order: its path, mapped\nthrough the move record; its path against the current files; the id index, which\nresolves a wikilink the way the validators did before 0.17.0 and reads the screen id\nmap, so the link names the file they read; its target as a pre-move file name, mapped\nthrough the move record. A pre-move name two files had resolves nothing. The move\nrecord is `_migration\u002Fplan.tsv`, or, when there is none, the renames git holds since\nthe commit before the layered directories left, read and never written; when the\nhistory does not show that commit, ask the operator for it and pass `--since REV`.\n\nA wikilink none of these resolves is settled without a person, because a wikilink left\nin the KB stops the Factory. An ADR id (`adr-{slug}`), an entity id whose module\nexists, an action id whose entity exists or a screen id whose face exists gets that\nartifact's draft, from its template and in its first state, with one `drafted` line\nper file; the link names it. Any other link becomes its text, one `unlinked` line each\nwith why: a retired file, a placeholder, an id that names no artifact type, or a name\na module and a face share.\n\nA Markdown link already in the KB that names nothing where it stands is rebased, one\n`link … rebased` line each: its path is read from the file's location before the move,\nand a target that moved, or a directory whose files all moved to one directory, is\nfollowed through the move record. A link to a layered directory, or to its README,\nnames the concept directory that took its contents (`01_adr` → `_adr`, `02_modules`,\n`03_features` and `04_domain` → `_modules`, `05_screens` → `_faces`), or that\ndirectory's README, and a subdirectory follows the layout (`02_modules\u002F{m}` →\n`_modules\u002F{m}`, `03_features\u002F{m}` → `_modules\u002F{m}\u002F_features`, `04_domain\u002F{m}` →\n`_modules\u002F{m}\u002F_domain`, `05_screens\u002F{f}\u002F{m}` → `_faces\u002F{f}\u002F_screens`, a screen index →\n`_faces\u002F{f}\u002F_index.md`); when the directory a link maps to does not exist, it names\nthe nearest directory on that path that does. No link is converted or rebased into\n`_migration\u002F`. A Markdown link it can neither rebase nor resolve, hand-written ones\nincluded, becomes its text, with an `unlinked` line and why (retired, placeholder,\nbroken), so the migrated KB holds no broken link. A template (`*.template.md`) is\nconverted like any other file, a placeholder path mapped through the layout, and its\nlinks are never unlinked or listed as broken.\n\nThe new link's text is the wikilink's alias, else the last segment of its target,\nso a link in a screen's `## Bindings` keeps the screen id it named. An anchor\n(`[[b#context]]`) stays on the new path, an embed (`![[b]]`) keeps its `!`, a path\nholding a space or a parenthesis is written in `\u003C…>`, and a link in frontmatter is a\nquoted string. Links inside code spans and fenced blocks stay as written.\n\n**Relay the count per source, the rebased count, and every `drafted` and `unlinked`\nline**: a draft is a file to fill in, and an unlinked one is text the operator may want\nto link again. Then run it without `--dry-run`;\nit refuses while git lists uncommitted moves, additions or deletions under the KB\n(Step 3 comes first), but not for the drafts an earlier conversion wrote. The link plan\nis saved to `inspire_kb\u002F01_spec\u002F_migration\u002Flinks.tsv`, and a second run changes\nnothing.\n\nTell the operator to commit the conversion:\n\n```bash\ngit add -A inspire_kb && git commit -m \"chore(kb): convert KB links to relative Markdown links (\u002Finspire:migrate)\"\n```\n\n## Step 5 — Review, then narrow\n\n```bash\n.inspire\u002Fbin\u002Freview.sh inspire_kb\n```\n\nExpected after a migration, and fine to fix in a later commit:\n\n- `face-exposure` warnings: every face lists every bundle, because the layered layout\n  did not say which bundles a face uses. Narrow each face's `bundles:`.\n- `spec-identity` warnings for a bundle with no `package:` — fill it in before the\n  Factory plans the bundle's mount test.\n\nAnything else the review reports was already wrong before the migration, or is a\ndefect in it: report the second kind.\n\n## Step 6 — The INSPIRE Factory\n\nTell the operator what comes next for code already built: INSPIRE Factory 0.16.0 or\nlater reads `_migration\u002Fid-map.json`, rewrites the screen\nids in the built code and the claim citations that name them, and commits that as a\nbranch for review, without running any agent. It rewrites literals only: code that\nreads a screen id's shape (its first segment was the module, it is now the face) is\nnot text it can fix, so its report lists those sites to review by hand. The test\nsuite runs on that branch before it is merged. The only new units it plans are the\ngrouping bundles, one mount test each. An older Factory refuses this KB and says why.\n\nThe same run rewrites the fingerprint of each built claim whose payload differs only\nin link syntax (adr-markdown-links D8), so the converted links rebuild nothing. That\nFactory reads Markdown links only and refuses a KB that still holds a wikilink; an\nolder Factory does not read Markdown links.\n","# \u002Finspire:migrate — the KB by concept\n\nINSPIRE 0.15.0 reads the specification only from `inspire_kb\u002F01_spec\u002F`, where every\nartifact is found by its typed extension (`.module.md`, `.feature.md`, `.entity.md`,\n`.action.md`, `.adr.md`, `.bundle.md`, `.face.md`, `.screen.md`, `.process.md`…).\nThis skill moves a KB written in the layered layout there, once. It is the only\nstep that moves anything in `inspire_kb\u002F`: `\u002Finspire:update` never does\n([`adr-kb-structure`](https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fdocs\u002Fadr\u002Fadr-kb-structure.md)\nD10).\n\nFrom 0.17.0 a KB link is a relative Markdown link to the target file,\n`[adr-audit](..\u002F..\u002F_adr\u002Faudit.adr.md)`. The skill converts every `[[wikilink]]` in\nits own step\n([`adr-markdown-links`](https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fdocs\u002Fadr\u002Fadr-markdown-links.md)\nD6). A KB already on the concept layout that still holds wikilinks starts at\nStep 4: its links are converted and nothing moves.\n\n**What it never does:** rename a module, an entity or an action; change any id but a\nscreen's; point a link at a different file; extract a shared screen into a pattern;\ncreate a process, or a bundle with an artifact of its own; write to git.\nEvery screen id it changes goes into `inspire_kb\u002F01_spec\u002F_migration\u002Fid-map.json`,\nwhich INSPIRE Factory 0.16.0 or later reads to rewrite the built code instead of\nrebuilding it.\n\n## Preconditions\n\n1. The runtime is already on 0.15.0 or later (`\u002Finspire:update` has run). The\n   validators and skills of this version read only `01_spec\u002F`.\n2. `jq` and `yq` (Mike Farah v4) are on `PATH`.\n3. **A clean working tree.** If `git status --porcelain` is non-empty, stop and ask the\n   operator to commit or stash first: the moves must be committed on their own, before\n   any edit, so git records them as renames and the history of every file survives.\n\n## Step 1 — Dry run, and the questions it asks\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmigrate-kb.sh\" --dry-run --kb inspire_kb\n```\n\nIt prints the plan, one tab-separated line per step (`move`, `write`, `idmap`,\n`unplaced`, `config`, `note`), and writes nothing. A `config` line names a file outside\nthe KB, `.inspire\u002Femanate.yml` or `.inspire\u002Femanate.json`, and the change to its spec\nroot, which moves to `inspire_kb\u002F01_spec`. Step 2 also prints a `seed` line for each\nskeleton file `--skeleton` adds. When it needs an answer it prints `ask` lines\ninstead and exits 3. Ask the operator each one, in their words, then run the dry run\nagain with the answers as flags:\n\n| `ask` key | Question | Flag |\n|---|---|---|\n| `face` | No roster, but there are screens: every screen moves to one face. What is its id? Propose the project's name in kebab-case. | `--face ID` |\n| `bundle` | No roster: every module is exposed by one bundle. What is its id (propose `api`), and which package exposes it (`source_root`-relative, for example `apps\u002Fapi`)? | `--bundle ID --bundle-package PATH` |\n| `bundle-modules:{id}` | The roster has several headless surfaces: which modules does `{id}` serve? Read the ADR that partitions them if there is one, and propose it. | `--bundle-modules {id}=m1,m2` |\n| `lib:{id}` | The lib surface `{id}`: does it become a bundle (a package with code of its own) or part of the design system (a UI kit)? | `--lib {id}=bundle` or `--lib {id}=design-system` |\n| `shared-face` | `05_screens\u002Fshared\u002F` holds screens two faces use. Which face keeps them? Nothing is extracted; each other face can add its own screen later. | `--shared-face ID` |\n\nNever answer a question yourself: these are specification decisions.\n\n**Relay the plan grouped:** how many files move per kind, every screen id that changes\n(the `idmap` lines, old → new), every file it cannot place (`unplaced`: moved under\n`_migration\u002Funplaced\u002F`, never dropped), every `config` change and every `note`. Add how many wikilinks\nthe KB holds outside code:\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmigrate-links.sh\" --count --kb inspire_kb\n```\n\nAsk the operator to confirm before Step 2.\n\n## Step 2 — Migrate\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmigrate-kb.sh\" --kb inspire_kb {the same answer flags} \\\n  --skeleton \"${CLAUDE_PLUGIN_ROOT}\u002Fbase\u002Fkb\u002F01_spec\"\n```\n\n`--skeleton` adds the READMEs, the starter patterns and the default theme the layered\nlayout never had, and seeds `design-system.md` from the theme if the project had none —\nonly where nothing is on disk. The plan it applied is saved to\n`inspire_kb\u002F01_spec\u002F_migration\u002Fplan.tsv`.\n\nIt refuses, and moves nothing, when:\n\n- `01_spec\u002F` already exists beside layered directories (a half-migrated KB) — find out\n  what put it there before going on;\n- a screen id is used by more than one screen — the id map would be ambiguous. Run\n  `.inspire\u002Fbin\u002Fscreen-coherence.sh` on the old tree with the previous runtime, or\n  fix the duplicate by hand, and run again.\n\nA second run on a migrated KB is a no-op.\n\n## Step 3 — Commit the moves on their own\n\nTell the operator to commit now, before any edit:\n\n```bash\ngit add -A && git commit -m \"chore(kb): move the KB to 01_spec (\u002Finspire:migrate)\"\n```\n\nThe tree was clean before Step 2, so every change is the run's: the KB, and the file of\neach `config` line. `git status --porcelain` is empty afterwards; the Factory's remap\nrefuses a dirty checkout. Do not commit for them unless they ask you to. Step 4 waits\nfor this commit.\n\n## Step 4 — Convert the links\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmigrate-links.sh\" --dry-run --kb inspire_kb\n```\n\nIt prints one `link` line per link it converts (file, line, the source that resolved\nit, the wikilink, the Markdown link), one `draft` or `unlinked` line per link it\nsettles, and writes nothing. A link resolves through, in order: its path, mapped\nthrough the move record; its path against the current files; the id index, which\nresolves a wikilink the way the validators did before 0.17.0 and reads the screen id\nmap, so the link names the file they read; its target as a pre-move file name, mapped\nthrough the move record. A pre-move name two files had resolves nothing. The move\nrecord is `_migration\u002Fplan.tsv`, or, when there is none, the renames git holds since\nthe commit before the layered directories left, read and never written; when the\nhistory does not show that commit, ask the operator for it and pass `--since REV`.\n\nA wikilink none of these resolves is settled without a person, because a wikilink left\nin the KB stops the Factory. An ADR id (`adr-{slug}`), an entity id whose module\nexists, an action id whose entity exists or a screen id whose face exists gets that\nartifact's draft, from its template and in its first state, with one `drafted` line\nper file; the link names it. Any other link becomes its text, one `unlinked` line each\nwith why: a retired file, a placeholder, an id that names no artifact type, or a name\na module and a face share.\n\nA Markdown link already in the KB that names nothing where it stands is rebased, one\n`link … rebased` line each: its path is read from the file's location before the move,\nand a target that moved, or a directory whose files all moved to one directory, is\nfollowed through the move record. A link to a layered directory, or to its README,\nnames the concept directory that took its contents (`01_adr` → `_adr`, `02_modules`,\n`03_features` and `04_domain` → `_modules`, `05_screens` → `_faces`), or that\ndirectory's README, and a subdirectory follows the layout (`02_modules\u002F{m}` →\n`_modules\u002F{m}`, `03_features\u002F{m}` → `_modules\u002F{m}\u002F_features`, `04_domain\u002F{m}` →\n`_modules\u002F{m}\u002F_domain`, `05_screens\u002F{f}\u002F{m}` → `_faces\u002F{f}\u002F_screens`, a screen index →\n`_faces\u002F{f}\u002F_index.md`); when the directory a link maps to does not exist, it names\nthe nearest directory on that path that does. No link is converted or rebased into\n`_migration\u002F`. A Markdown link it can neither rebase nor resolve, hand-written ones\nincluded, becomes its text, with an `unlinked` line and why (retired, placeholder,\nbroken), so the migrated KB holds no broken link. A template (`*.template.md`) is\nconverted like any other file, a placeholder path mapped through the layout, and its\nlinks are never unlinked or listed as broken.\n\nThe new link's text is the wikilink's alias, else the last segment of its target,\nso a link in a screen's `## Bindings` keeps the screen id it named. An anchor\n(`[[b#context]]`) stays on the new path, an embed (`![[b]]`) keeps its `!`, a path\nholding a space or a parenthesis is written in `\u003C…>`, and a link in frontmatter is a\nquoted string. Links inside code spans and fenced blocks stay as written.\n\n**Relay the count per source, the rebased count, and every `drafted` and `unlinked`\nline**: a draft is a file to fill in, and an unlinked one is text the operator may want\nto link again. Then run it without `--dry-run`;\nit refuses while git lists uncommitted moves, additions or deletions under the KB\n(Step 3 comes first), but not for the drafts an earlier conversion wrote. The link plan\nis saved to `inspire_kb\u002F01_spec\u002F_migration\u002Flinks.tsv`, and a second run changes\nnothing.\n\nTell the operator to commit the conversion:\n\n```bash\ngit add -A inspire_kb && git commit -m \"chore(kb): convert KB links to relative Markdown links (\u002Finspire:migrate)\"\n```\n\n## Step 5 — Review, then narrow\n\n```bash\n.inspire\u002Fbin\u002Freview.sh inspire_kb\n```\n\nExpected after a migration, and fine to fix in a later commit:\n\n- `face-exposure` warnings: every face lists every bundle, because the layered layout\n  did not say which bundles a face uses. Narrow each face's `bundles:`.\n- `spec-identity` warnings for a bundle with no `package:` — fill it in before the\n  Factory plans the bundle's mount test.\n\nAnything else the review reports was already wrong before the migration, or is a\ndefect in it: report the second kind.\n\n## Step 6 — The INSPIRE Factory\n\nTell the operator what comes next for code already built: INSPIRE Factory 0.16.0 or\nlater reads `_migration\u002Fid-map.json`, rewrites the screen\nids in the built code and the claim citations that name them, and commits that as a\nbranch for review, without running any agent. It rewrites literals only: code that\nreads a screen id's shape (its first segment was the module, it is now the face) is\nnot text it can fix, so its report lists those sites to review by hand. The test\nsuite runs on that branch before it is merged. The only new units it plans are the\ngrouping bundles, one mount test each. An older Factory refuses this KB and says why.\n\nThe same run rewrites the fingerprint of each built claim whose payload differs only\nin link syntax (adr-markdown-links D8), so the converted links rebuild nothing. That\nFactory reads Markdown links only and refuses a KB that still holds a wikilink; an\nolder Factory does not read Markdown links.\n",{"name":5,"description":7},"main","bf5124558fc1203b1fe5aea2d2ae38cfba34939b","plugin\u002Fskills\u002Fmigrate",1,"https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire","https:\u002F\u002Finspire.openbims.dev","https:\u002F\u002Fgithub.com\u002FGenomcore","https:\u002F\u002Fgenomcore.com","2026-11-13 22:27:32",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Genomcore\u002Finspire --skill migrate",{"tool":38,"command":39},"bunx","bunx skills add Genomcore\u002Finspire --skill migrate",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Genomcore\u002Finspire --skill migrate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fmigrate\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M79DMDSD4Z004V0CB01EYKT4","update","Update this project's INSPIRE runtime to the installed plugin's version: report drift, re-materialize unchanged files, and refuse to clobber local edits. Use after \u002Fplugin update inspire reports a newer base.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fupdate\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M79DM6HZ7YN9M3WGXVN64AW1","init","Install the INSPIRE runtime into this repository: materialize the skills, validators, hooks and knowledge-base skeleton, register the hooks, and freeze the runtime version. Run once per project. Use when setting up INSPIRE in a new or existing repo.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Finit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M79DM28JSC3GWEJ82346VGW6","inspire-workspace","Workspace-level validation: the global pre-PR review (orchestrating module + cross-module checks) and vault-structure validation. Use for the required pre-merge gate and top-level structure checks. ADR lifecycle lives in \u002Finspire-adr; the task tracker in \u002Finspire-task.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fbase\u002Fskills\u002Finspire-workspace\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M79DKYPKA8TKJCW1GF0W2WAN","inspire-task","Task tracker: create \u002F update \u002F close \u002F list \u002F show tickets in inspire_kb\u002F99_tracker\u002F. A plain-file kanban (one Markdown file per ticket, no external tool) for tracking work, drift, and skill-feedback. Use to open, advance, close, or query tickets.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fbase\u002Fskills\u002Finspire-task\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M79DKTXQWFBW2P6VMQW3DYWX","inspire-spike","Vertical spikes: register and harvest external functional-prototype repos. A spike is a narrow, deep, throwaway build in its OWN repo that answers 'can we build it as we think?'. Use to register such a repo (name\u002Freference it, set up its learnings hygiene) and to capture its learnings into the vault as a gap analysis against the current project.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fbase\u002Fskills\u002Finspire-spike\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M79DKQDXVS3TJ6GG6KXYTMXF","inspire-screens","Create and validate screens (a screen is the UI spec for one view). A screen declares its own bindings — data sources, dispatches, navigation, states — and names a shared layout and shared components as dependencies. Use when designing or reviewing an application's screens.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fbase\u002Fskills\u002Finspire-screens\u002FSKILL.md",[],[]]