[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQ1AHPRKMD2DTTHBXSDJEM":3,"skill-same:01M7AQ1AHPRKMD2DTTHBXSDJEM":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},"01M7AQ1AHPRKMD2DTTHBXSDJEM","vigil-esl-hop",null,"ESL lifecycle hop — in an ESL-enabled project (tonberry MCP available), VIGIL owns the FAILURE PATH: on a verify_fail or spec-vs-impl drift, transition the change back to the maker (in_progress) and emit an ESCALATE envelope carrying root-cause attribution. You are the failure-path checker, distinct from the maker (maker ≠ checker). Absent tonberry → run the normal V→I→G→I→L cycle (ESL opt-in).","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\u002Fvigil\u002Fskills\u002Fesl-hop\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vigil-esl-hop\ndescription: \"ESL lifecycle hop — in an ESL-enabled project (tonberry MCP available), VIGIL owns the FAILURE PATH: on a verify_fail or spec-vs-impl drift, transition the change back to the maker (in_progress) and emit an ESCALATE envelope carrying root-cause attribution. You are the failure-path checker, distinct from the maker (maker ≠ checker). Absent tonberry → run the normal V→I→G→I→L cycle (ESL opt-in).\"\nmetadata:\n  methodology: VIGIL\n  phase: post-L\n---\n\n# VIGIL — ESL Lifecycle Hop (Failure Path)\n\nUse this skill in an **ESL-enabled project** (`mcp__tonberry__*` tools available)\nwhen a verify **FAILS** or the implementation **diverges from the spec** (your\nroot-cause domain). You own the **failure path** of the Eidolons Spec Lifecycle\n(ESL) — a checker distinct from the maker.\n\nFor the full lifecycle, stage definitions, and role bindings, see the nexus\ncortex `methodology\u002Fcortex\u002Fesl-protocol.md`.\n\n## Your hop\n\n1. **On `verify_fail`** — call\n   `mcp__tonberry__transition --change_id \u003Cid> --to_status in_progress` to route\n   the change back to the **maker**, then emit an `ESCALATE` envelope carrying\n   your root-cause attribution (`[ROOT-CAUSE]` + evidence anchor from the V→I→G→I→L\n   cycle). The maker re-implements against your finding, not against the symptom.\n2. **When the implementation outran the spec** — run\n   `mcp__tonberry__drift_check --change_id \u003Cid> --checker vigil` **before** archive.\n   A mismatch (impl asserts behavior the Semantic spec never specified, or\n   vice-versa) is a `verify_fail` → transition back + `ESCALATE`.\n3. **You are the failure-path checker** — a distinct identity from the maker.\n   Your verify\u002Fdrift envelopes carry `from.eidolon = vigil`, never the maker's\n   identity.\n\n## Invariants\n\n- **maker ≠ checker** — VIGIL is the checker on the failure path; the change's\n  `maker` (e.g. Vivi) is always a distinct identity. Self-verified changes\n  violate the ESL C4 gate.\n- **Tonberry composes artifacts; you supply signals.** You provide the\n  root-cause attribution, the drift verdict, and the `verify_fail` reason;\n  tonberry writes the `change.json` transition and records enforcement.\n- **Graceful skip** — if `mcp__tonberry__*` tools are unavailable, run your\n  normal **V → I → G → I → L** cycle and emit findings\u002Fescalations the standard\n  way; **never hard-fail**. ESL is opt-in; VIGIL is EIIS-standalone-conformant\n  and works without tonberry.\n\n## Pending: ECL 2.1 verification-attestation (not yet implemented)\n\nECL v2.1 (Draft, adoption-gated — `spec\u002Fecl-2.1.md` §6.5.8) defines an\nOPTIONAL `ise.verification` sub-block: `{fresh_context, checker,\ntranscript_access}`, the wire-shape footprint of an independent verify pass.\nVIGIL is exactly the kind of distinct-identity checker that sub-block is\nbuilt to describe — you are the maker≠checker on this failure path already\n(ESL C4, above). Once ECL 2.1 is cut to Published (the gate: ≥3 shipped\nEidolons emitting the `ise` block) and VIGIL adopts it, your `ESCALATE`\nenvelope on this hop would carry `ise.verification = {fresh_context: true,\nchecker: \"vigil\", transcript_access: \"artifact-only\"}` (or `\"none\"`,\ndepending on what you were handed) alongside `ise.assertion_grade` — the\nMUST-level pairing rule that a `validated` grade actually has a\nfresh-context, different-checker verification behind it is owned by **ESL\n1.1 C8**, not ECL (ECL only shape-checks the sub-block, per §6.5.8.3).\n\n**This is documented as pending, not emitted.** ECL 2.1 is Draft; `ECL_VERSION`\nstays `2.0` and VIGIL's emitted envelopes do not carry `ise.verification` yet.\nNo code or template change accompanies this note — it exists so the next\nsweep that adopts 2.1 has the mapping already worked out.\n\n---\n\n*VIGIL — ESL Lifecycle Hop (failure path)*\n","# VIGIL — ESL Lifecycle Hop (Failure Path)\n\nUse this skill in an **ESL-enabled project** (`mcp__tonberry__*` tools available)\nwhen a verify **FAILS** or the implementation **diverges from the spec** (your\nroot-cause domain). You own the **failure path** of the Eidolons Spec Lifecycle\n(ESL) — a checker distinct from the maker.\n\nFor the full lifecycle, stage definitions, and role bindings, see the nexus\ncortex `methodology\u002Fcortex\u002Fesl-protocol.md`.\n\n## Your hop\n\n1. **On `verify_fail`** — call\n   `mcp__tonberry__transition --change_id \u003Cid> --to_status in_progress` to route\n   the change back to the **maker**, then emit an `ESCALATE` envelope carrying\n   your root-cause attribution (`[ROOT-CAUSE]` + evidence anchor from the V→I→G→I→L\n   cycle). The maker re-implements against your finding, not against the symptom.\n2. **When the implementation outran the spec** — run\n   `mcp__tonberry__drift_check --change_id \u003Cid> --checker vigil` **before** archive.\n   A mismatch (impl asserts behavior the Semantic spec never specified, or\n   vice-versa) is a `verify_fail` → transition back + `ESCALATE`.\n3. **You are the failure-path checker** — a distinct identity from the maker.\n   Your verify\u002Fdrift envelopes carry `from.eidolon = vigil`, never the maker's\n   identity.\n\n## Invariants\n\n- **maker ≠ checker** — VIGIL is the checker on the failure path; the change's\n  `maker` (e.g. Vivi) is always a distinct identity. Self-verified changes\n  violate the ESL C4 gate.\n- **Tonberry composes artifacts; you supply signals.** You provide the\n  root-cause attribution, the drift verdict, and the `verify_fail` reason;\n  tonberry writes the `change.json` transition and records enforcement.\n- **Graceful skip** — if `mcp__tonberry__*` tools are unavailable, run your\n  normal **V → I → G → I → L** cycle and emit findings\u002Fescalations the standard\n  way; **never hard-fail**. ESL is opt-in; VIGIL is EIIS-standalone-conformant\n  and works without tonberry.\n\n## Pending: ECL 2.1 verification-attestation (not yet implemented)\n\nECL v2.1 (Draft, adoption-gated — `spec\u002Fecl-2.1.md` §6.5.8) defines an\nOPTIONAL `ise.verification` sub-block: `{fresh_context, checker,\ntranscript_access}`, the wire-shape footprint of an independent verify pass.\nVIGIL is exactly the kind of distinct-identity checker that sub-block is\nbuilt to describe — you are the maker≠checker on this failure path already\n(ESL C4, above). Once ECL 2.1 is cut to Published (the gate: ≥3 shipped\nEidolons emitting the `ise` block) and VIGIL adopts it, your `ESCALATE`\nenvelope on this hop would carry `ise.verification = {fresh_context: true,\nchecker: \"vigil\", transcript_access: \"artifact-only\"}` (or `\"none\"`,\ndepending on what you were handed) alongside `ise.assertion_grade` — the\nMUST-level pairing rule that a `validated` grade actually has a\nfresh-context, different-checker verification behind it is owned by **ESL\n1.1 C8**, not ECL (ECL only shape-checks the sub-block, per §6.5.8.3).\n\n**This is documented as pending, not emitted.** ECL 2.1 is Draft; `ECL_VERSION`\nstays `2.0` and VIGIL's emitted envelopes do not carry `ise.verification` yet.\nNo code or template change accompanies this note — it exists so the next\nsweep that adopts 2.1 has the mapping already worked out.\n\n---\n\n*VIGIL — ESL Lifecycle Hop (failure path)*\n",{"name":5,"metadata":24,"description":7},{"phase":25,"methodology":26},"post-L","VIGIL","main","38c3a82583abf9806de764f89ac0099ad690933a",".eidolons\u002Fvigil\u002Fskills\u002Fesl-hop",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 vigil-esl-hop",{"tool":42,"command":43},"bunx","bunx skills add Rynaro\u002Fmagicite --skill vigil-esl-hop",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Rynaro\u002Fmagicite --skill vigil-esl-hop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fvigil\u002Fskills\u002Fesl-hop\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",[],[]]