[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74G2A8SCVWBB3JG3BVCK94M":3,"skill-same:01M74G2A8SCVWBB3JG3BVCK94M":46},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M74G2A8SCVWBB3JG3BVCK94M","cavekit-check",null,"Read-only Cavekit drift detector. Use when users invoke \u002Fck:check, ask whether code matches SPEC.md, check invariants, audit interfaces, or inspect §T status evidence.","casualjim\u002Fpi-mimir","casualjim","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F456109?v=4","01M74FWNWVYZQ29YNASRYNTCG4","Ivan Porto Carrero","01M74FWNXE5R8481XV0Q8Q7EY0",16,"MIT","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-cavekit\u002Fskills\u002Fcavekit-check\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: cavekit-check\ndescription: Read-only Cavekit drift detector. Use when users invoke \u002Fck:check, ask whether code matches SPEC.md, check invariants, audit interfaces, or inspect §T status evidence.\n---\n\n# cavekit-check — drift detector\n\nPure diagnostic workflow. Read `SPEC.md`, compare it to code, report evidence. Write nothing. Run after each `\u002Fck:build` and before each ship — drift caught here is a diff; drift caught in prod is a §B.\n\nRead bundled `..\u002F..\u002FFORMAT.md` before interpreting `SPEC.md` structure and addresses.\n\n## Load\n\n1. Read project-root `SPEC.md`. If missing, report `no SPEC.md, nothing to check` and stop.\n2. Parse invocation args:\n   - `§V` or no args → check invariants\n   - `§I` → check interfaces\n   - `§T` → audit task status against code evidence\n   - `--all` → check §V, §I, and §T\n3. Parse archive comments like `\u003C!-- archive: .cavekit\u002Farchive\u002FSPEC-\u003Cdate>.md §T T1-T12 -->`.\n4. Read referenced `.cavekit\u002Farchive\u002FSPEC-*.md` copies when needed to resolve archived §V\u002F§I cites, archived §T rows, or max-ID\u002Frange questions.\n\n## Optional Cavecrew investigation\n\nWhen evidence lookup needs code archaeology and `cavecrew-investigator` is available, use it for read-only compressed fact finding. Prefer it for locating §I implementations, §V enforcement\u002Ftests, §T status evidence, callers, and related files. The investigator must return file:line evidence only and must not design, fix, edit, or mutate state. If unavailable, use codebase-memory tools when available, then exact reads\u002Fsearch as fallback.\n\n## Check §V — invariants\n\nFor each `V\u003Cn>` in current `SPEC.md`; with `--all`, include archived `V\u003Cn>` ranges referenced by archive comments:\n\n1. Translate invariant into a verifiable claim about code\u002Ftests\u002Fconfig.\n2. Search and read relevant files.\n3. Classify: **HOLD** \u002F **VIOLATE** \u002F **UNVERIFIABLE**.\n4. Cite file:line evidence when possible.\n\n## Check §I — interfaces\n\nFor each interface item in current `SPEC.md`; with `--all`, include archived §I refs referenced by archive comments:\n\n1. Locate implementation.\n2. Classify:\n   - **MATCH** — implemented shape matches spec.\n   - **DRIFT** — implementation exists but shape differs.\n   - **MISSING** — spec surface absent from code.\n   - **EXTRA** — code exposes related surface absent from spec.\n3. Cite file:line evidence.\n\n## Check §T — tasks\n\nFor each task row in current `SPEC.md`; with `--all`, include archived §T rows referenced by archive comments:\n\n1. If status `x`, verify claimed work appears present.\n2. If status `~`, note as in-progress.\n3. If status `.`, note as pending.\n4. Flag `x` rows with no supporting evidence as **STALE**.\n\n## Report format\n\nUse concise grouped output:\n\n```text\n## §V drift\nV2 VIOLATE: auth\u002Fmw.go:47 uses `\u003C` not `≤`. see §B.1.\nV5 UNVERIFIABLE: no test covers req path.\n\n## §I drift\nI.api DRIFT: POST \u002Fx returns `{result}` not `{id}`. route.go:112.\nI.cmd MISSING: `foo bar` absent from cli\u002F*.go.\n\n## §T drift\nT3 STALE: status `x`, no middleware file exists.\n\n## summary\n2 violate. 1 missing. 1 stale. 1 unverifiable.\nnext: \u002Fck:spec bug: \u003Ccause>, \u002Fck:build \u003Ctask>, or amend spec.\n```\n\n## Remedy hints only\n\nEnd with one-line hints:\n\n- VIOLATE \u002F DRIFT → use `\u002Fck:spec bug: \u003Ccause>` or fix code.\n- MISSING → use `\u002Fck:build §T.n` if a task exists; otherwise `\u002Fck:spec amend §T`.\n- STALE → use `\u002Fck:spec amend §T` to uncheck or revise.\n- EXTRA → document with `\u002Fck:spec amend §I` or remove code.\n\n## Boundaries\n\n- Zero writes.\n- No `SPEC.md` edits.\n- No code edits.\n- No commits.\n- No scores or grades; classify by evidence.\n","# cavekit-check — drift detector\n\nPure diagnostic workflow. Read `SPEC.md`, compare it to code, report evidence. Write nothing. Run after each `\u002Fck:build` and before each ship — drift caught here is a diff; drift caught in prod is a §B.\n\nRead bundled `..\u002F..\u002FFORMAT.md` before interpreting `SPEC.md` structure and addresses.\n\n## Load\n\n1. Read project-root `SPEC.md`. If missing, report `no SPEC.md, nothing to check` and stop.\n2. Parse invocation args:\n   - `§V` or no args → check invariants\n   - `§I` → check interfaces\n   - `§T` → audit task status against code evidence\n   - `--all` → check §V, §I, and §T\n3. Parse archive comments like `\u003C!-- archive: .cavekit\u002Farchive\u002FSPEC-\u003Cdate>.md §T T1-T12 -->`.\n4. Read referenced `.cavekit\u002Farchive\u002FSPEC-*.md` copies when needed to resolve archived §V\u002F§I cites, archived §T rows, or max-ID\u002Frange questions.\n\n## Optional Cavecrew investigation\n\nWhen evidence lookup needs code archaeology and `cavecrew-investigator` is available, use it for read-only compressed fact finding. Prefer it for locating §I implementations, §V enforcement\u002Ftests, §T status evidence, callers, and related files. The investigator must return file:line evidence only and must not design, fix, edit, or mutate state. If unavailable, use codebase-memory tools when available, then exact reads\u002Fsearch as fallback.\n\n## Check §V — invariants\n\nFor each `V\u003Cn>` in current `SPEC.md`; with `--all`, include archived `V\u003Cn>` ranges referenced by archive comments:\n\n1. Translate invariant into a verifiable claim about code\u002Ftests\u002Fconfig.\n2. Search and read relevant files.\n3. Classify: **HOLD** \u002F **VIOLATE** \u002F **UNVERIFIABLE**.\n4. Cite file:line evidence when possible.\n\n## Check §I — interfaces\n\nFor each interface item in current `SPEC.md`; with `--all`, include archived §I refs referenced by archive comments:\n\n1. Locate implementation.\n2. Classify:\n   - **MATCH** — implemented shape matches spec.\n   - **DRIFT** — implementation exists but shape differs.\n   - **MISSING** — spec surface absent from code.\n   - **EXTRA** — code exposes related surface absent from spec.\n3. Cite file:line evidence.\n\n## Check §T — tasks\n\nFor each task row in current `SPEC.md`; with `--all`, include archived §T rows referenced by archive comments:\n\n1. If status `x`, verify claimed work appears present.\n2. If status `~`, note as in-progress.\n3. If status `.`, note as pending.\n4. Flag `x` rows with no supporting evidence as **STALE**.\n\n## Report format\n\nUse concise grouped output:\n\n```text\n## §V drift\nV2 VIOLATE: auth\u002Fmw.go:47 uses `\u003C` not `≤`. see §B.1.\nV5 UNVERIFIABLE: no test covers req path.\n\n## §I drift\nI.api DRIFT: POST \u002Fx returns `{result}` not `{id}`. route.go:112.\nI.cmd MISSING: `foo bar` absent from cli\u002F*.go.\n\n## §T drift\nT3 STALE: status `x`, no middleware file exists.\n\n## summary\n2 violate. 1 missing. 1 stale. 1 unverifiable.\nnext: \u002Fck:spec bug: \u003Ccause>, \u002Fck:build \u003Ctask>, or amend spec.\n```\n\n## Remedy hints only\n\nEnd with one-line hints:\n\n- VIOLATE \u002F DRIFT → use `\u002Fck:spec bug: \u003Ccause>` or fix code.\n- MISSING → use `\u002Fck:build §T.n` if a task exists; otherwise `\u002Fck:spec amend §T`.\n- STALE → use `\u002Fck:spec amend §T` to uncheck or revise.\n- EXTRA → document with `\u002Fck:spec amend §I` or remove code.\n\n## Boundaries\n\n- Zero writes.\n- No `SPEC.md` edits.\n- No code edits.\n- No commits.\n- No scores or grades; classify by evidence.\n",{"name":5,"description":7},"main","86a206d111fba4ffc9c47c363486479262e63513","packages\u002Fpi-cavekit\u002Fskills\u002Fcavekit-check",9,"https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir","https:\u002F\u002Fgithub.com\u002Fcasualjim","http:\u002F\u002Fflanders.co.nz","2026-11-10 15:32:15",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add casualjim\u002Fpi-mimir --skill cavekit-check",{"tool":38,"command":39},"bunx","bunx skills add casualjim\u002Fpi-mimir --skill cavekit-check",{"tool":41,"command":42},"pnpm","pnpm dlx skills add casualjim\u002Fpi-mimir --skill cavekit-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-cavekit\u002Fskills\u002Fcavekit-check\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":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M74GK3CG2X0988XMHBKNC0HG","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M74GK2A4034JSAN8BCGBEPVB","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M74GK13302GXTR58TM47BQY1","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M74GJYB1DJCA4AQH22MWYM9J","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Fskill:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M74GJW7794XM60AKH76941T0","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74GJPQN3RW4FN7G78W2NFR1","tdd","Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]