[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APVS3MP17V2HB5XB0KWBNE":3,"skill-same:01M7APVS3MP17V2HB5XB0KWBNE":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},"01M7APVS3MP17V2HB5XB0KWBNE","forge-checker-handoff",null,"Governs the checker-handoff gate for FORGE verdicts that authorize an irreversible action. Use at the end of the Emit phase, after the verdict and recommended action are drafted, to check the recommended action against the five mechanically observable irreversibility trigger markers (deploy\u002Frelease, destructive migration or data deletion, security-boundary change, external spend\u002Fcommitment, public communication). On a match, set the emitted reasoning-report's requires_checker flag to true instead of letting the verdict flow straight to execution. Reversible verdicts (no marker match) are unaffected — do not fire this skill for them.","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\u002Fforge\u002Fskills\u002Fchecker-handoff\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: forge-checker-handoff\ndescription: Governs the checker-handoff gate for FORGE verdicts that authorize an irreversible action. Use at the end of the Emit phase, after the verdict and recommended action are drafted, to check the recommended action against the five mechanically observable irreversibility trigger markers (deploy\u002Frelease, destructive migration or data deletion, security-boundary change, external spend\u002Fcommitment, public communication). On a match, set the emitted reasoning-report's requires_checker flag to true instead of letting the verdict flow straight to execution. Reversible verdicts (no marker match) are unaffected — do not fire this skill for them.\nmetadata:\n  methodology: FORGE\n  phase: E\n---\n\n# Checker-Handoff Skill — FORGE (maker ≠ checker, additive)\n\nLoaded at the tail of the Emit phase, after the verdict and its recommended\naction are drafted but before the envelope is finalized. FORGE's own Gate\n(`skills\u002Fverification\u002FSKILL.md`) is a **self-review** pass — sound for most\nverdicts, but not sufficient authority to greenlight an action that cannot be\nundone. This skill is the mechanical trigger that routes those verdicts to a\n**distinct checker** before any action is taken.\n\n## When to use\n\nLoad this skill once per deliberation, at Emit, immediately after the winning\nhypothesis's recommended action is known. Check the recommended action\nagainst the trigger table below. Fire the hop only on a match. Do not use for\nverdicts whose recommended action is reversible at ordinary cost — those emit\nexactly as before, with `requires_checker: false` (the default).\n\n---\n\n## Irreversibility trigger table\n\nFive categories, checked mechanically against the recommended action's text\n— a match on **any** category fires the hop:\n\n| # | Category | Observable markers in the recommended action |\n|---|----------|-----------------------------------------------|\n| 1 | **Deploy \u002F release** | deploy, release, ship to production, go live, roll out, promote to prod |\n| 2 | **Destructive migration or data deletion** | drop table, truncate, delete from, irreversible migration, purge data, destroy backup |\n| 3 | **Security-boundary change** | change permissions, rotate credentials, modify IAM\u002FACL, disable auth, open firewall, grant\u002Frevoke access |\n| 4 | **External spend \u002F commitment** | sign contract, purchase, commit budget, vendor agreement, procurement, SLA commitment |\n| 5 | **Public communication** | press release, public announcement, customer-facing communication, publish blog post, public API contract change |\n\nThese five categories are the closed trigger set for this skill — do not\nextend them ad hoc. If a recommended action is genuinely irreversible but\ndoes not fit any of the five, the standard Reversibility dimension in\n`skills\u002Fframing\u002FSKILL.md` Step 4 and the verdict's `[RISK]` markers already carry\nthat signal; this skill only formalizes the mechanically-observable subset.\n\n## Your hop\n\n1. **Detect** — After drafting the recommended action, scan it against the\n   trigger table above. Zero matches → skip to step 4 (no hop).\n2. **Mark** — On a match, set `requires_checker: true` in the emitted\n   reasoning-report's frontmatter (`schemas\u002Freasoning-report-profile.v1.json`\n   `requires_checker` field). Add a `[CHECKER-REQUIRED]` line to the\n   verdict's Provenance section naming the fired category and a checker-class\n   hint: **VIGIL** for evidence-based\u002Ftechnical claims (root-cause,\n   feasibility, reproducibility — claims a second reasoning or investigation\n   pass can adjudicate), **human** for judgment calls (organizational,\n   strategic, or policy trade-offs no evidence pass resolves). The hint is\n   guidance, not a dispatch — see Invariants below.\n3. **Emit unchanged otherwise** — The hop does not add a reasoning pass, does\n   not trigger REFORGE, and does not block emission. FORGE still emits its\n   normal verdict on the normal 1–3 pass \u002F 1-REFORGE budget; `requires_checker`\n   is a payload marker, not a refusal.\n4. **Default** — Absent a trigger match, `requires_checker` is `false` (the\n   schema default). Reversible verdicts are byte-for-byte unaffected by this\n   skill's existence.\n\n## Invariants\n\n- **maker(forge) ≠ checker(vigil\u002Fhuman).** FORGE's own Gate is necessary but\n  not sufficient authority for an irreversible action. A `requires_checker:\n  true` report MUST be reviewed by a distinct party before any action —\n  FORGE never self-certifies past this line.\n- **Tool-less, always.** FORGE holds no tools (P0-1) and does not gain any\n  at this hop. The hop is expressed **purely via the emitted-artifact\n  marker** (`requires_checker: true` + the `[CHECKER-REQUIRED]` note) —\n  never a tool call, never a direct dispatch to VIGIL or a human. Routing\n  between VIGIL and human is the **orchestrator's** decision, informed by\n  but not bound to FORGE's checker-class hint.\n- **Additive, never blocking.** This hop composes with — does not extend —\n  the existing 3-pass \u002F 1-REFORGE cap and does not gate emission. A verdict\n  that fails to emit because of this skill is a bug in this skill, not\n  correct behavior.\n- **Backward compatible.** Orchestrators that do not read `requires_checker`\n  see no change in behavior — the field defaults to `false` and the rest of\n  the reasoning-report is unchanged.\n\n## Graceful skip\n\nIf the recommended action's text is ambiguous or the decision type makes the\nfive categories inapplicable (e.g. a pure `ROOT-CAUSE` verdict with no\nrecommended action beyond \"investigate further\"), `requires_checker` stays\n`false`. This skill never fabricates an irreversibility claim to be safe —\nfalse positives erode the signal as much as false negatives.\n\n---\n\n*Reasoner — Checker-Handoff Skill (maker ≠ checker, additive)*\n","# Checker-Handoff Skill — FORGE (maker ≠ checker, additive)\n\nLoaded at the tail of the Emit phase, after the verdict and its recommended\naction are drafted but before the envelope is finalized. FORGE's own Gate\n(`skills\u002Fverification\u002FSKILL.md`) is a **self-review** pass — sound for most\nverdicts, but not sufficient authority to greenlight an action that cannot be\nundone. This skill is the mechanical trigger that routes those verdicts to a\n**distinct checker** before any action is taken.\n\n## When to use\n\nLoad this skill once per deliberation, at Emit, immediately after the winning\nhypothesis's recommended action is known. Check the recommended action\nagainst the trigger table below. Fire the hop only on a match. Do not use for\nverdicts whose recommended action is reversible at ordinary cost — those emit\nexactly as before, with `requires_checker: false` (the default).\n\n---\n\n## Irreversibility trigger table\n\nFive categories, checked mechanically against the recommended action's text\n— a match on **any** category fires the hop:\n\n| # | Category | Observable markers in the recommended action |\n|---|----------|-----------------------------------------------|\n| 1 | **Deploy \u002F release** | deploy, release, ship to production, go live, roll out, promote to prod |\n| 2 | **Destructive migration or data deletion** | drop table, truncate, delete from, irreversible migration, purge data, destroy backup |\n| 3 | **Security-boundary change** | change permissions, rotate credentials, modify IAM\u002FACL, disable auth, open firewall, grant\u002Frevoke access |\n| 4 | **External spend \u002F commitment** | sign contract, purchase, commit budget, vendor agreement, procurement, SLA commitment |\n| 5 | **Public communication** | press release, public announcement, customer-facing communication, publish blog post, public API contract change |\n\nThese five categories are the closed trigger set for this skill — do not\nextend them ad hoc. If a recommended action is genuinely irreversible but\ndoes not fit any of the five, the standard Reversibility dimension in\n`skills\u002Fframing\u002FSKILL.md` Step 4 and the verdict's `[RISK]` markers already carry\nthat signal; this skill only formalizes the mechanically-observable subset.\n\n## Your hop\n\n1. **Detect** — After drafting the recommended action, scan it against the\n   trigger table above. Zero matches → skip to step 4 (no hop).\n2. **Mark** — On a match, set `requires_checker: true` in the emitted\n   reasoning-report's frontmatter (`schemas\u002Freasoning-report-profile.v1.json`\n   `requires_checker` field). Add a `[CHECKER-REQUIRED]` line to the\n   verdict's Provenance section naming the fired category and a checker-class\n   hint: **VIGIL** for evidence-based\u002Ftechnical claims (root-cause,\n   feasibility, reproducibility — claims a second reasoning or investigation\n   pass can adjudicate), **human** for judgment calls (organizational,\n   strategic, or policy trade-offs no evidence pass resolves). The hint is\n   guidance, not a dispatch — see Invariants below.\n3. **Emit unchanged otherwise** — The hop does not add a reasoning pass, does\n   not trigger REFORGE, and does not block emission. FORGE still emits its\n   normal verdict on the normal 1–3 pass \u002F 1-REFORGE budget; `requires_checker`\n   is a payload marker, not a refusal.\n4. **Default** — Absent a trigger match, `requires_checker` is `false` (the\n   schema default). Reversible verdicts are byte-for-byte unaffected by this\n   skill's existence.\n\n## Invariants\n\n- **maker(forge) ≠ checker(vigil\u002Fhuman).** FORGE's own Gate is necessary but\n  not sufficient authority for an irreversible action. A `requires_checker:\n  true` report MUST be reviewed by a distinct party before any action —\n  FORGE never self-certifies past this line.\n- **Tool-less, always.** FORGE holds no tools (P0-1) and does not gain any\n  at this hop. The hop is expressed **purely via the emitted-artifact\n  marker** (`requires_checker: true` + the `[CHECKER-REQUIRED]` note) —\n  never a tool call, never a direct dispatch to VIGIL or a human. Routing\n  between VIGIL and human is the **orchestrator's** decision, informed by\n  but not bound to FORGE's checker-class hint.\n- **Additive, never blocking.** This hop composes with — does not extend —\n  the existing 3-pass \u002F 1-REFORGE cap and does not gate emission. A verdict\n  that fails to emit because of this skill is a bug in this skill, not\n  correct behavior.\n- **Backward compatible.** Orchestrators that do not read `requires_checker`\n  see no change in behavior — the field defaults to `false` and the rest of\n  the reasoning-report is unchanged.\n\n## Graceful skip\n\nIf the recommended action's text is ambiguous or the decision type makes the\nfive categories inapplicable (e.g. a pure `ROOT-CAUSE` verdict with no\nrecommended action beyond \"investigate further\"), `requires_checker` stays\n`false`. This skill never fabricates an irreversibility claim to be safe —\nfalse positives erode the signal as much as false negatives.\n\n---\n\n*Reasoner — Checker-Handoff Skill (maker ≠ checker, additive)*\n",{"name":5,"metadata":24,"description":7},{"phase":25,"methodology":26},"E","FORGE","main","38c3a82583abf9806de764f89ac0099ad690933a",".eidolons\u002Fforge\u002Fskills\u002Fchecker-handoff",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 forge-checker-handoff",{"tool":42,"command":43},"bunx","bunx skills add Rynaro\u002Fmagicite --skill forge-checker-handoff",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Rynaro\u002Fmagicite --skill forge-checker-handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fforge\u002Fskills\u002Fchecker-handoff\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",[],[]]