[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APY34P0584TQKP2KPB3GY1":3,"skill-same:01M7APY34P0584TQKP2KPB3GY1":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7APY34P0584TQKP2KPB3GY1","idg-verification",null,"Defines the CHT verification framework and provenance output for the Gate phase of the IDG cycle. Use when entering the Gate phase, verifying document completeness and truthfulness, running CHT scores, deciding DELIVER vs REVISE vs ESCALATE, or producing provenance metadata blocks.","Rynaro\u002Fmagicite","Rynaro","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5271543?v=4","01M70CFYFMB316W23THVQAQ42M","Henrique A. Lavezzo","01M7APN2KCVWBNY727T57KR2ZJ",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fidg\u002Fskills\u002Fverification\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: idg-verification\ndescription: Defines the CHT verification framework and provenance output for the Gate phase of the IDG cycle. Use when entering the Gate phase, verifying document completeness and truthfulness, running CHT scores, deciding DELIVER vs REVISE vs ESCALATE, or producing provenance metadata blocks.\nmetadata:\n  methodology: IDG\n  phase: G\n---\n\n# Verification Gates\n\nLoaded during the Gate phase. Defines the CHT verification framework and provenance output.\n\n## When to use\n\nLoad this skill when entering the Gate (G) phase of the IDG cycle — specifically when running the CHT gate (Completeness \u002F Helpfulness \u002F Truthfulness), generating provenance metadata, or deciding whether to deliver, revise, or escalate. Also load for the section-level mini-gate in G5 parallel mode. Do NOT load upfront; trigger on demand at Gate entry.\n\n---\n\n## CHT Framework\n\nThree dimensions. Score each 1–5 after completing the draft.\n\n### C — Completeness\n\nDoes the document cover everything it should?\n\n| Score | Meaning |\n|-------|---------|\n| 5 | All template sections filled. No `[GAP]` markers. |\n| 4 | All sections filled. 1–2 minor `[GAP]` markers with justification. |\n| 3 | Most sections filled. Some `[GAP]` markers. Core content present. |\n| 2 | Significant sections missing or skeletal. Multiple `[GAP]` markers. |\n| 1 | Document is a stub. Insufficient context was provided. |\n\n**Checks:**\n- Every section in the template\u002Fskeleton is addressed\n- Required structural markers are present (at least one `[DECISION]` in ADRs, at least one `[ACTION]` in runbooks)\n- Cross-references between sections are consistent\n- If a section is intentionally omitted, the omission is justified\n\n### H — Helpfulness\n\nCan the target audience understand and act on this document?\n\n| Score | Meaning |\n|-------|---------|\n| 5 | Reader can act immediately. Clear next steps, no ambiguity. |\n| 4 | Reader understands fully. Minor clarification might help in edge cases. |\n| 3 | Reader understands the main points. Some sections need more context. |\n| 2 | Reader would need to ask follow-up questions to act. |\n| 1 | Document is confusing or disorganized. Audience mismatch. |\n\n**Checks:**\n- Technical depth matches stated audience\n- Jargon is appropriate (defined if cross-functional audience)\n- `[ACTION]` items have enough context to be actionable\n- Document structure follows a logical reading path\n- Conclusions and summaries appear where readers expect them\n\n### T — Truthfulness\n\nIs every claim grounded in source material?\n\n| Score | Meaning |\n|-------|---------|\n| 5 | Every claim sourced. No inference without labeling. |\n| 4 | Claims sourced. 1–2 minor inferences clearly labeled. |\n| 3 | Most claims sourced. Some inferences not explicitly labeled. |\n| 2 | Several unsourced claims. Risk of misleading reader. |\n| 1 | Significant fabrication or unsupported assertions. |\n\n**Checks:**\n- Every factual statement traces to a source artifact\n- Inferences are labeled (\"Inferred:\", \"Likely:\")\n- `[DISPUTED]` markers present where sources conflict\n- No invented rationale attributed to people or teams\n- Error messages, commands, file paths are exact (not paraphrased)\n- If the source artefact arrived with an `*.envelope.json` sidecar, the provenance block records the envelope's `message_id`, `thread_id`, `from`, `performative`, and `verify_pass` \u002F `verify_fail` outcome. A `verify_fail` does not lower the score below 4 by itself; it is captured as `[DISPUTED]` in the document.\n\n---\n\n## Gate Decision\n\n| Condition | Action |\n|-----------|--------|\n| All dimensions ≥ 4 | **DELIVER** — document is ready |\n| Any dimension 2–3 | **REVISE** — one targeted revision pass on failing dimensions only |\n| Any dimension 1 | **ESCALATE** — insufficient context to produce this document. Report what's missing. |\n\n### Revision Protocol\n\nWhen revising:\n1. Identify the specific sections causing the low score\n2. Fix only those sections — do not rewrite the entire document\n3. Re-check the specific dimension that failed\n4. Deliver with a note on what was revised\n\n**Hard cap: one revision pass.** If the document still has issues after revision, deliver it with the remaining issues explicitly flagged in the provenance metadata. The requester can provide additional context for a follow-up pass rather than the Scribe entering an unbounded loop.\n\n---\n\n## Provenance Metadata\n\nEvery delivered document includes a provenance block at the end:\n\n```markdown\n---\n\n## Provenance\n\n- **Scribe version**: \u003Cversion>\n- **Document type**: [type]\n- **Generated**: [timestamp]\n- **Source artifacts**:\n  - [list of source artifacts used, with identifiers]\n- **CHT scores**: C:[N]\u002F5 H:[N]\u002F5 T:[N]\u002F5\n- **Coverage**: [brief assessment — what's well-covered vs gaps]\n- **Flags**: [any unresolved `[GAP]` or `[DISPUTED]` markers]\n```\n\n### Source Artifact Identifiers\n\nUse the most specific identifier available:\n\n| Source Type | Identifier Format |\n|-------------|------------------|\n| Git commit | `commit:abc1234` |\n| File | `file:path\u002Fto\u002Ffile.rb` |\n| Agent output | `agent:[agent-name]:[task-id]` |\n| Conversation | `conversation:turn-[N]` |\n| External doc | `doc:[title-or-url]` |\n| Spec \u002F ticket | `spec:[ID]` |\n| ECL envelope | `ecl:\u002F\u002Fthread\u002F\u003Cthread_id>\u002Fmessage\u002F\u003Cmessage_id>` |\n\n---\n\n## Memory Ingest (Phase G — after DELIVER)\n\nOnce the Gate decision is **DELIVER** (or DELIVER-with-flags after revision), persist\nthe document handoff to CRYSTALIUM.\n\n### Ingest\n\nIf the document was handed off with an ECL sidecar envelope (`*.envelope.json`),\ningest via:\n\n```\nmcp__crystalium__ingest(\n  envelope = \u003Cthe validated *.envelope.json contents>,\n  payload  = \u003Cdelivered document contents>\n)\n```\n\nThis records the document at T1 (`from.eidolon=idg` drives tier derivation).\n\nIf no ECL sidecar is present, commit an episodic note directly:\n\n```\nmcp__crystalium__commit(\n  layer      = \"episodic\",\n  payload    = \u003Cdocument type + CHT scores + key decisions\u002Fgaps summary>,\n  provenance = { author_agent: \"idg\", document_type: \u003Ctype> }\n)\n```\n\n`author_agent` MUST be `\"idg\"` on every direct commit.\n\n### Session end\n\nAfter ingest (or after delivery if CRYSTALIUM is absent), call:\n\n```\nmcp__crystalium__session_end()\n```\n\nThis triggers Dream consolidation asynchronously. Call it once per IDG dispatch\ncompletion. Dream promotes corroborated episodic entries (terminology conventions,\nstructural patterns) to the semantic layer — improving future recall quality.\n\n**Graceful skip:** if `mcp__crystalium__*` tools are unavailable (CRYSTALIUM not\ninstalled), skip ingest and session_end and mark the Gate phase complete normally.\nNever hard-fail on absent CRYSTALIUM tools. IDG is EIIS-standalone-conformant.\n\n---\n\n*Scribe — Verification Skill*\n","# Verification Gates\n\nLoaded during the Gate phase. Defines the CHT verification framework and provenance output.\n\n## When to use\n\nLoad this skill when entering the Gate (G) phase of the IDG cycle — specifically when running the CHT gate (Completeness \u002F Helpfulness \u002F Truthfulness), generating provenance metadata, or deciding whether to deliver, revise, or escalate. Also load for the section-level mini-gate in G5 parallel mode. Do NOT load upfront; trigger on demand at Gate entry.\n\n---\n\n## CHT Framework\n\nThree dimensions. Score each 1–5 after completing the draft.\n\n### C — Completeness\n\nDoes the document cover everything it should?\n\n| Score | Meaning |\n|-------|---------|\n| 5 | All template sections filled. No `[GAP]` markers. |\n| 4 | All sections filled. 1–2 minor `[GAP]` markers with justification. |\n| 3 | Most sections filled. Some `[GAP]` markers. Core content present. |\n| 2 | Significant sections missing or skeletal. Multiple `[GAP]` markers. |\n| 1 | Document is a stub. Insufficient context was provided. |\n\n**Checks:**\n- Every section in the template\u002Fskeleton is addressed\n- Required structural markers are present (at least one `[DECISION]` in ADRs, at least one `[ACTION]` in runbooks)\n- Cross-references between sections are consistent\n- If a section is intentionally omitted, the omission is justified\n\n### H — Helpfulness\n\nCan the target audience understand and act on this document?\n\n| Score | Meaning |\n|-------|---------|\n| 5 | Reader can act immediately. Clear next steps, no ambiguity. |\n| 4 | Reader understands fully. Minor clarification might help in edge cases. |\n| 3 | Reader understands the main points. Some sections need more context. |\n| 2 | Reader would need to ask follow-up questions to act. |\n| 1 | Document is confusing or disorganized. Audience mismatch. |\n\n**Checks:**\n- Technical depth matches stated audience\n- Jargon is appropriate (defined if cross-functional audience)\n- `[ACTION]` items have enough context to be actionable\n- Document structure follows a logical reading path\n- Conclusions and summaries appear where readers expect them\n\n### T — Truthfulness\n\nIs every claim grounded in source material?\n\n| Score | Meaning |\n|-------|---------|\n| 5 | Every claim sourced. No inference without labeling. |\n| 4 | Claims sourced. 1–2 minor inferences clearly labeled. |\n| 3 | Most claims sourced. Some inferences not explicitly labeled. |\n| 2 | Several unsourced claims. Risk of misleading reader. |\n| 1 | Significant fabrication or unsupported assertions. |\n\n**Checks:**\n- Every factual statement traces to a source artifact\n- Inferences are labeled (\"Inferred:\", \"Likely:\")\n- `[DISPUTED]` markers present where sources conflict\n- No invented rationale attributed to people or teams\n- Error messages, commands, file paths are exact (not paraphrased)\n- If the source artefact arrived with an `*.envelope.json` sidecar, the provenance block records the envelope's `message_id`, `thread_id`, `from`, `performative`, and `verify_pass` \u002F `verify_fail` outcome. A `verify_fail` does not lower the score below 4 by itself; it is captured as `[DISPUTED]` in the document.\n\n---\n\n## Gate Decision\n\n| Condition | Action |\n|-----------|--------|\n| All dimensions ≥ 4 | **DELIVER** — document is ready |\n| Any dimension 2–3 | **REVISE** — one targeted revision pass on failing dimensions only |\n| Any dimension 1 | **ESCALATE** — insufficient context to produce this document. Report what's missing. |\n\n### Revision Protocol\n\nWhen revising:\n1. Identify the specific sections causing the low score\n2. Fix only those sections — do not rewrite the entire document\n3. Re-check the specific dimension that failed\n4. Deliver with a note on what was revised\n\n**Hard cap: one revision pass.** If the document still has issues after revision, deliver it with the remaining issues explicitly flagged in the provenance metadata. The requester can provide additional context for a follow-up pass rather than the Scribe entering an unbounded loop.\n\n---\n\n## Provenance Metadata\n\nEvery delivered document includes a provenance block at the end:\n\n```markdown\n---\n\n## Provenance\n\n- **Scribe version**: \u003Cversion>\n- **Document type**: [type]\n- **Generated**: [timestamp]\n- **Source artifacts**:\n  - [list of source artifacts used, with identifiers]\n- **CHT scores**: C:[N]\u002F5 H:[N]\u002F5 T:[N]\u002F5\n- **Coverage**: [brief assessment — what's well-covered vs gaps]\n- **Flags**: [any unresolved `[GAP]` or `[DISPUTED]` markers]\n```\n\n### Source Artifact Identifiers\n\nUse the most specific identifier available:\n\n| Source Type | Identifier Format |\n|-------------|------------------|\n| Git commit | `commit:abc1234` |\n| File | `file:path\u002Fto\u002Ffile.rb` |\n| Agent output | `agent:[agent-name]:[task-id]` |\n| Conversation | `conversation:turn-[N]` |\n| External doc | `doc:[title-or-url]` |\n| Spec \u002F ticket | `spec:[ID]` |\n| ECL envelope | `ecl:\u002F\u002Fthread\u002F\u003Cthread_id>\u002Fmessage\u002F\u003Cmessage_id>` |\n\n---\n\n## Memory Ingest (Phase G — after DELIVER)\n\nOnce the Gate decision is **DELIVER** (or DELIVER-with-flags after revision), persist\nthe document handoff to CRYSTALIUM.\n\n### Ingest\n\nIf the document was handed off with an ECL sidecar envelope (`*.envelope.json`),\ningest via:\n\n```\nmcp__crystalium__ingest(\n  envelope = \u003Cthe validated *.envelope.json contents>,\n  payload  = \u003Cdelivered document contents>\n)\n```\n\nThis records the document at T1 (`from.eidolon=idg` drives tier derivation).\n\nIf no ECL sidecar is present, commit an episodic note directly:\n\n```\nmcp__crystalium__commit(\n  layer      = \"episodic\",\n  payload    = \u003Cdocument type + CHT scores + key decisions\u002Fgaps summary>,\n  provenance = { author_agent: \"idg\", document_type: \u003Ctype> }\n)\n```\n\n`author_agent` MUST be `\"idg\"` on every direct commit.\n\n### Session end\n\nAfter ingest (or after delivery if CRYSTALIUM is absent), call:\n\n```\nmcp__crystalium__session_end()\n```\n\nThis triggers Dream consolidation asynchronously. Call it once per IDG dispatch\ncompletion. Dream promotes corroborated episodic entries (terminology conventions,\nstructural patterns) to the semantic layer — improving future recall quality.\n\n**Graceful skip:** if `mcp__crystalium__*` tools are unavailable (CRYSTALIUM not\ninstalled), skip ingest and session_end and mark the Gate phase complete normally.\nNever hard-fail on absent CRYSTALIUM tools. IDG is EIIS-standalone-conformant.\n\n---\n\n*Scribe — Verification Skill*\n",{"name":5,"metadata":24,"description":7},{"phase":25,"methodology":26},"G","IDG","main","38c3a82583abf9806de764f89ac0099ad690933a",".eidolons\u002Fidg\u002Fskills\u002Fverification",0,"https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite","https:\u002F\u002Fgithub.com\u002FRynaro","https:\u002F\u002Fhlavezzo.me","A Code Alchemist with a passion for weaving tales and inscribing transmutation circles in pure code.","2026-10-14 02:35:37",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Rynaro\u002Fmagicite --skill idg-verification",{"tool":42,"command":43},"bunx","bunx skills add Rynaro\u002Fmagicite --skill idg-verification",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Rynaro\u002Fmagicite --skill idg-verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fidg\u002Fskills\u002Fverification\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7AQ4GHJQVV8TJBJ8T1V7ZQ9","wine-dxvk-cache-clear","Clear a stale DXVK shader cache that is causing graphical corruption in a\nWine or Proton game. Use when: a game shows corrupted textures or shader\nflicker that started after a driver or DXVK version change.","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Ftoy-registry\u002Fskills\u002Fwine-dxvk-cache-clear\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7AQ4CY1NHSMY1HCZ91387YY","steam-download-region-fix","Fix a Steam client stuck at very low download speed by changing its\ndownload region. Use when: Steam downloads are far below the local\ninternet speed for every game, not just one.","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Ftoy-registry\u002Fskills\u002Fsteam-download-region-fix\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AQ49P7Y0CDRSYMPVABX80K","proton-battleye-eac-toggle","Toggle BattlEye or Easy Anti-Cheat runtime support for a Steam Proton game.\nUse when: a multiplayer game refuses to launch with an anti-cheat error under Proton.","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Ftoy-registry\u002Fskills\u002Fproton-battleye-eac-toggle\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AQ45326FAP3X4Q86FK1X4N","vivi-verify-incoming","Load when reading any upstream artefact handed off to Vivi that carries a sibling .envelope.json. BLOCKING per ECL §6.2.2: the orchestrator MUST have verified the envelope's SHA-256 (eidolons verify-envelope --block \u002F eidolons run --verify) and recorded a verify_pass before dispatch. If no verify_pass exists for the message_id, or a verify_fail is present, REFUSE to process the payload and hand back to the orchestrator. Symmetric receiver gate — every Eidolon enforces it identically.","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fvivi\u002Fskills\u002Fverify-incoming\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AQ402861P0P3C2TEGFGMA1","vivi-parallel-tracks","Load ONLY under TRANCE authorization when the Plan phase yields N independent, non-overlapping implementation tracks (disjoint file sets). Operationalizes the TRANCE G4 form — parallel multi-track implementation in mandatory git-worktree isolation, max 5 clean-context tracks, a per-track verifier cascade, a non-fungible per-track ≤3 reflection budget, explicit stop conditions, and a single-threaded merge\u002Faggregation step. Absent TRANCE gating, Vivi runs exactly as today: single-track A→P→I→V→Δ\u002FR.","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fvivi\u002Fskills\u002Fparallel-tracks\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AQ3RH9BZF9ZMTC7VG5P7PB","vivi-methodology","Full Vivi cycle reference — A(nalyze) → P(lan) → I(mplement) → V(erify) → Δ(Delta)\u002FR(eflect). Use when the task is a non-trivial feature implementation in a brownfield codebase and you need the complete methodology reference: complexity routing, evidence-grounded planning rules, test-anchoring requirements, and failure-escalation thresholds.","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fvivi\u002Fskills\u002Fmethodology\u002FSKILL.md",[],[]]