[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVVEMPVGXGVTBJMNNT6Q0T":3,"skill-same:01M6JVVEMPVGXGVTBJMNNT6Q0T":55},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6JVVEMPVGXGVTBJMNNT6Q0T","verify-interpreter",null,"Interpret the output of `specgraph verify` and explain what each status means and what to do next.","45ck\u002Fskill-harness","45ck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F98618920?v=4","01M6JVMEERB77XKFGN2RT770BP","Calvin","01M6JVMEK42E6WBBD4R3QE9Y4P",15,"MIT","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fpacks\u002Fspecgraph-skills\u002Fskills\u002Fverify-interpreter\u002FSKILL.md",[],[19,20,21,22,23,24,25,26],"verify","interpreter","verify interpreter","status","explain","do","next","output","2026-11-10 10:12:30",false,"---\nname: verify-interpreter\ndescription: Interpret the output of `specgraph verify` and explain what each status means and what to do next.\n---\n\nRead and explain the output of `specgraph verify` in plain language, then recommend next steps.\n\n## Status meanings\n\n| Status | Meaning | Action |\n|--------|---------|--------|\n| `PASS` | All required evidence thresholds met | Nothing required |\n| `WARN` | Evidence exists but below required strength for this state | Strengthen evidence or lower requirement |\n| `FAIL` | No evidence found for a required dimension | Add evidence or add waiver |\n| `INSUFFICIENT` | Evidence found but strength is below required level | Raise evidence strength (e.g. E0 → E2) |\n| `SKIP` | Spec has no evidence requirements (draft\u002Fdeprecated) | Review if state is correct |\n| `WAIVED` | Requirement waived — check expiry | Verify waiver is still valid |\n\n### Example output\n\n```\n  PASS          FEAT-001  [accepted]\n  WARN          FEAT-002  [in_progress]\n                 warn: No verification claims found (advisory)\n  FAIL          FEAT-003  [accepted]\n                 fail: No implementation claims found. Required: E2 (indexed)\n  INSUFFICIENT  FEAT-004  [accepted]\n                 insufficient-evidence: implementation: found E0 but required E2\n```\n\n## Verify commands reference\n\n```bash\nspecgraph verify                         # summary table for all specs\nspecgraph verify --spec FEAT-001         # single spec only\nspecgraph verify --json                  # machine-readable output\nspecgraph verify --changed src\u002Ffoo.ts    # incremental scan (changed files only)\nspecgraph verify --no-db                 # dry run — skip writing to DB\nspecgraph explain \u003CSPEC-ID>              # full claim breakdown for one spec\nspecgraph explain                        # all specs\nspecgraph find --spec FEAT-001           # locate files that reference a spec\nspecgraph find --relation IMPLEMENTS     # all IMPLEMENTS claims\nspecgraph find --provider annotation     # claims from a specific provider\nspecgraph find --strength 1              # E1 and above\nspecgraph waivers                        # list active waivers\nspecgraph waivers FEAT-001               # waivers for one spec\nspecgraph subject issue:beads:bd-a1b2    # show a specific Beads issue's claims\nspecgraph subject symbol:annotation:MyClass  # show a symbol's claims\n```\n\nSubject IDs follow the format `kind:provider:identity` (e.g. `issue:beads:bd-a1b2`, `symbol:annotation:TodoStore`).\n\n## Interpretation checklist\n\n1. Count PASS \u002F WARN \u002F FAIL \u002F INSUFFICIENT counts — overall health indicator.\n2. For each FAIL: run `specgraph explain \u003CID>` to see what claims exist.\n3. For each INSUFFICIENT: check the `required_evidence` threshold in the spec frontmatter — lower it or add stronger evidence.\n4. For each WARN: check if the evidence level matches the spec's `state` requirements.\n5. Check waiver expiry dates — expired waivers flip to WARN\u002FFAIL.\n6. Confirm provider scans are recent — stale scan data can hide real gaps.\n\n## Common causes\n\n| Symptom | Likely cause | Fix |\n|---------|-------------|-----|\n| All specs FAIL | Annotations not scanned | Run `specgraph verify` again; check `@spec` syntax |\n| INSUFFICIENT on `accepted` specs | Evidence is E0\u002FE1, need E2+ | Add cross-refs or tests to raise strength |\n| WARN on `accepted` specs | Evidence is E0\u002FE1, need E2+ | Add cross-refs or tests |\n| Unexpected PASS | Waiver is covering a gap | Check `specgraph waivers` for active waivers |\n| Missing specs in output | Spec file not in `docs\u002F` | Check path and `.specgraph\u002Fconfig.json` |\n| Beads claims missing | Beads not enabled | Set `beads.enabled: true` in `.specgraph\u002Fconfig.json` |\n\n## Rules\n\n1. Never dismiss a FAIL without understanding the root cause.\n2. Use `specgraph explain` before deciding whether to add evidence or a waiver.\n3. Report the exact spec IDs and dimensions in any gap summary you produce.\n4. Config file is `.specgraph\u002Fconfig.json` (falls back to `.agent-docs\u002Fconfig.json`).\n","Read and explain the output of `specgraph verify` in plain language, then recommend next steps.\n\n## Status meanings\n\n| Status | Meaning | Action |\n|--------|---------|--------|\n| `PASS` | All required evidence thresholds met | Nothing required |\n| `WARN` | Evidence exists but below required strength for this state | Strengthen evidence or lower requirement |\n| `FAIL` | No evidence found for a required dimension | Add evidence or add waiver |\n| `INSUFFICIENT` | Evidence found but strength is below required level | Raise evidence strength (e.g. E0 → E2) |\n| `SKIP` | Spec has no evidence requirements (draft\u002Fdeprecated) | Review if state is correct |\n| `WAIVED` | Requirement waived — check expiry | Verify waiver is still valid |\n\n### Example output\n\n```\n  PASS          FEAT-001  [accepted]\n  WARN          FEAT-002  [in_progress]\n                 warn: No verification claims found (advisory)\n  FAIL          FEAT-003  [accepted]\n                 fail: No implementation claims found. Required: E2 (indexed)\n  INSUFFICIENT  FEAT-004  [accepted]\n                 insufficient-evidence: implementation: found E0 but required E2\n```\n\n## Verify commands reference\n\n```bash\nspecgraph verify                         # summary table for all specs\nspecgraph verify --spec FEAT-001         # single spec only\nspecgraph verify --json                  # machine-readable output\nspecgraph verify --changed src\u002Ffoo.ts    # incremental scan (changed files only)\nspecgraph verify --no-db                 # dry run — skip writing to DB\nspecgraph explain \u003CSPEC-ID>              # full claim breakdown for one spec\nspecgraph explain                        # all specs\nspecgraph find --spec FEAT-001           # locate files that reference a spec\nspecgraph find --relation IMPLEMENTS     # all IMPLEMENTS claims\nspecgraph find --provider annotation     # claims from a specific provider\nspecgraph find --strength 1              # E1 and above\nspecgraph waivers                        # list active waivers\nspecgraph waivers FEAT-001               # waivers for one spec\nspecgraph subject issue:beads:bd-a1b2    # show a specific Beads issue's claims\nspecgraph subject symbol:annotation:MyClass  # show a symbol's claims\n```\n\nSubject IDs follow the format `kind:provider:identity` (e.g. `issue:beads:bd-a1b2`, `symbol:annotation:TodoStore`).\n\n## Interpretation checklist\n\n1. Count PASS \u002F WARN \u002F FAIL \u002F INSUFFICIENT counts — overall health indicator.\n2. For each FAIL: run `specgraph explain \u003CID>` to see what claims exist.\n3. For each INSUFFICIENT: check the `required_evidence` threshold in the spec frontmatter — lower it or add stronger evidence.\n4. For each WARN: check if the evidence level matches the spec's `state` requirements.\n5. Check waiver expiry dates — expired waivers flip to WARN\u002FFAIL.\n6. Confirm provider scans are recent — stale scan data can hide real gaps.\n\n## Common causes\n\n| Symptom | Likely cause | Fix |\n|---------|-------------|-----|\n| All specs FAIL | Annotations not scanned | Run `specgraph verify` again; check `@spec` syntax |\n| INSUFFICIENT on `accepted` specs | Evidence is E0\u002FE1, need E2+ | Add cross-refs or tests to raise strength |\n| WARN on `accepted` specs | Evidence is E0\u002FE1, need E2+ | Add cross-refs or tests |\n| Unexpected PASS | Waiver is covering a gap | Check `specgraph waivers` for active waivers |\n| Missing specs in output | Spec file not in `docs\u002F` | Check path and `.specgraph\u002Fconfig.json` |\n| Beads claims missing | Beads not enabled | Set `beads.enabled: true` in `.specgraph\u002Fconfig.json` |\n\n## Rules\n\n1. Never dismiss a FAIL without understanding the root cause.\n2. Use `specgraph explain` before deciding whether to add evidence or a waiver.\n3. Report the exact spec IDs and dimensions in any gap summary you produce.\n4. Config file is `.specgraph\u002Fconfig.json` (falls back to `.agent-docs\u002Fconfig.json`).\n",{"name":5,"description":7},"main","31fedf0ad5fb02ca599add38ef92ce9ebfdaf785","packs\u002Fspecgraph-skills\u002Fskills\u002Fverify-interpreter",1,"https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Freleases\u002Ftag\u002Fv0.1.0","https:\u002F\u002Fgithub.com\u002F45ck","calvinkennedy.com","2026-06-23 16:42:42",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add 45ck\u002Fskill-harness --skill verify-interpreter",{"tool":47,"command":48},"bunx","bunx skills add 45ck\u002Fskill-harness --skill verify-interpreter",{"tool":50,"command":51},"pnpm","pnpm dlx skills add 45ck\u002Fskill-harness --skill verify-interpreter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fpacks\u002Fspecgraph-skills\u002Fskills\u002Fverify-interpreter\u002FSKILL.md",true,[],[56,74,84,107,120,140],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":67,"publishedAt":27},"01M6JVWQZDB2JC8FC6Q2KKH0HV","risky-skill","Synthetic risky skill for intake scanner coverage.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fexternal-skill-intake\u002Frisky-script-pack\u002Fskills\u002Frisky-skill\u002FSKILL.md",[62],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[68,69,70,71,72,73],"risky skill","for","synthetic","scanner","coverage","intake",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":81,"publishedAt":27},"01M6JVWKG4SGT1M3TVDDDS4PDD","fixture-skill","Synthetic skill for intake scanner coverage.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fexternal-skill-intake\u002Fclean-cross-host-pack\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[80],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[82,83,70,73,72,71,69],"fixture skill","fixture",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":91,"publishedAt":27},"01M6JVWE7C4FKEF3PGZVZ31FFG","third-party-skill-intake","Review third-party skill repos for format fit, provenance, and first-party adoption paths without treating them as direct harness dependencies.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-harness-helpers\u002Fskills\u002Fthird-party-skill-intake\u002FSKILL.md",[90],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[73,92,93,94,95,96,97,98,99,100,101,102,103,69,104,105,106],"party","third party skill intake","paths","adoption","first","provenance","format","direct","dependencies","third-party","as","fit","harness","review","repos",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":114,"publishedAt":27},"01M6JVW8YAFFNP0Q1XWXE1WH6G","loop","Handle \u002Floop-style requests for finding, adapting, drafting, and preparing bounded agent loops without treating external loop catalogs as authorization.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-harness-helpers\u002Fskills\u002Floop\u002FSKILL.md",[113],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[109,115,116,102,117,118,119,69],"bounded","authorization","style","loops","requests",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":27},"01M6JVW3EWZ6DES0NQP7YMBZQS","beads-task-shaping","Convert analysis output into actionable Beads-ready work items with clear scope, priority, and acceptance checks.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-harness-helpers\u002Fskills\u002Fbeads-task-shaping\u002FSKILL.md",[],[127,128,129,130,131,132,133,134,135,136,137,138,26,139],"beads task shaping","task","shaping","beads","scope","acceptance","analysis","convert","work","ready","clear","actionable","with",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":27},"01M6JVVYNGXYZTFT7YRCE6MME6","agent-selection","Select the best workflow agent for a task based on task shape, deliverables, and dependency packs.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-harness-helpers\u002Fskills\u002Fagent-selection\u002FSKILL.md",[146],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[148,149,150,151,152,128,153,69,154],"agent selection","selection","select","dependency","shape","deliverables","workflow"]