[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APTF866N6ACTX0KG2XCY93":3,"skill-same:01M7APTF866N6ACTX0KG2XCY93":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},"01M7APTF866N6ACTX0KG2XCY93","atlas-esl-hop",null,"ESL lifecycle hop — the DISCOVER hop. When a scout mission's findings surface change-worthy signal (a defect, a spec\u002Fimpl drift, or a genuine gap) in an ESL-enabled project (.spectra\u002F present), ATLAS proposes opening an ESL change at 'proposed' by framing the scout-report + its ECL envelope it already emits as the proposal artifact — it never calls mcp__tonberry__* itself and never implements (refusal boundary intact). SPECTRA's own esl-hop owns the actual right_size\u002Fpropose\u002Fspecify tonberry calls on receipt, over the existing atlas-to-spectra handoff edge. Absent .spectra\u002F or absent change-worthy findings → hand off the scout-report normally (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\u002Fatlas\u002Fskills\u002Fesl-hop\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: atlas-esl-hop\ndescription: \"ESL lifecycle hop — the DISCOVER hop. When a scout mission's findings surface change-worthy signal (a defect, a spec\u002Fimpl drift, or a genuine gap) in an ESL-enabled project (.spectra\u002F present), ATLAS proposes opening an ESL change at 'proposed' by framing the scout-report + its ECL envelope it already emits as the proposal artifact — it never calls mcp__tonberry__* itself and never implements (refusal boundary intact). SPECTRA's own esl-hop owns the actual right_size\u002Fpropose\u002Fspecify tonberry calls on receipt, over the existing atlas-to-spectra handoff edge. Absent .spectra\u002F or absent change-worthy findings → hand off the scout-report normally (ESL opt-in).\"\nmetadata:\n  methodology: ATLAS\n  phase: S\n---\n\n# ATLAS — ESL Lifecycle Hop (the DISCOVER hop)\n\n## When to use\n\nLoad at Phase S (Synthesize), after the fold is validated and before\n`scout-report.md` is finalized, when **both** hold:\n\n- **Change-worthy signal.** ≥1 finding in `findings.md` asserts something is\n  broken, drifted, or missing relative to a spec\u002Fexpectation the mission\n  surfaced — not merely descriptive topology. See \"What counts as\n  change-worthy\" below.\n- **ESL-enabled project.** A `.spectra\u002F` directory exists at the consumer\n  project root — checked with a single read-only `list_dir` probe, never an\n  MCP call. ATLAS has no `mcp__tonberry__*` tool surface and never acquires\n  one.\n\nIf either condition is false, skip this skill silently and emit\n`scout-report.md` the normal way (`skills\u002Fsynthesize\u002FSKILL.md`). ESL is opt-in;\nATLAS is EIIS-standalone-conformant and works without it.\n\n## What counts as change-worthy\n\nA finding is change-worthy when its claim is one of:\n\n- a **defect** — behavior contradicts a spec, contract, or documented\n  invariant;\n- a **drift** — an implementation and its governing spec\u002Fdoc have diverged;\n- a **gap** — a required capability, test, or safeguard is absent.\n\nPurely descriptive findings (\"X calls Y at `path:line`\") are not\nchange-worthy on their own. When uncertain, the mission's own `GAPS`\u002F`RISKS`\nframing (scout-report §5) is the signal — anything already flagged there as\nneeding a decision or a fix is change-worthy by definition.\n\n## Your hop — DISCOVER (`proposed`), never MAKE\n\nYou are the furthest-upstream Eidolon in the ESL chain. You do **not** call\n`mcp__tonberry__*` — right-sizing, opening the `change.json` record, and\nrunning S→P→E→C→T→R→A belong to **SPECTRA's own hop**\n(`skills\u002Fesl-hop\u002FSKILL.md` in the SPECTRA repo), triggered when it receives your\nhand-off. Your job stops at **naming the change-worthy finding and handing it\noff** — the refusal boundary (P0 rule 1: read-only, no\n`edit`\u002F`write`\u002F`commit`\u002F`deploy`\u002F`migrate`\u002F`refactor`\u002F`fix`) stays fully\nintact: you never create, edit, or transition ESL state yourself.\n\n1. **flag the proposal in §4.** In `scout-report.md` §4 \"Recommended next\n   actions\", tag every change-worthy `R-N` item `[→ SPECTRA]` with an\n   explicit `[ESL-PROPOSAL]` marker naming the `FINDING-XXX`\u002F`GAP-XXX` it\n   rests on, and state plainly that the item proposes opening an ESL change\n   at `proposed`. This is the same artifact Phase S already emits — no new\n   file, no new schema.\n2. **frame the envelope objective.** In `scout-report.envelope.json`, set\n   `performative: \"PROPOSE\"` (the existing default for ATLAS→SPECTRA) and\n   word `objective` to name the ESL proposal intent, e.g. `\"Deliver scout\n   report for mission \u003Cid>, proposing an ESL change at 'proposed' for\n   FINDING-003\u002FFINDING-007.\"`. The `ise` block is unchanged from the standard\n   scout-report emission (`skills\u002Fsynthesize\u002FSKILL.md` \"Envelope sidecar\"):\n   `ise.assertion_grade: \"self-attested\"` and\n   `ise.receiver_authorization: {auto_route: true, auto_merge: false,\n   auto_deploy: false}` — SPECTRA MAY auto-route the finding into its own ESL\n   intake without an operator confirm, but MUST NOT auto-merge or\n   auto-deploy anything off an ATLAS-originated discovery.\n3. **hand off via the existing edge.** Deliver `scout-report.md` +\n   `scout-report.envelope.json` to SPECTRA exactly as `skills\u002Fsynthesize\u002FSKILL.md`\n   already prescribes (`contracts\u002Fatlas-to-spectra.yaml`,\n   `artifact.kind: scout-report`, unchanged). SPECTRA's `spectra-esl-hop`\n   skill (when `.spectra\u002F` and tonberry are present on its side) takes it\n   from there: right_size → propose → specify.\n\n## Invariants\n\n- **Refusal boundary intact.** ATLAS never calls a tonberry write verb\n  (`propose`, `transition`, `archive`, `verify`) and never touches\n  `.spectra\u002Fchanges\u002F`. This hop is discovery framing on an artifact ATLAS\n  already emits, not a new write surface.\n- **SPECTRA owns `proposed`.** The actual `change.json` at `proposed` status\n  is created by SPECTRA's hop, never ATLAS's. ATLAS's contribution is\n  evidence carried across the existing roster edge\n  (`contracts\u002Fatlas-to-spectra.yaml`), not a tonberry-recognized object.\n- **No new artifact kind, no new contract.** The proposal rides inside the\n  standard `scout-report` artifact\u002Fenvelope pair — inventing a distinct ECL\n  `artifact.kind` here would require a contract change outside ATLAS's repo;\n  this hop deliberately does not do that.\n- **Evidence-anchored, same as every ATLAS claim.** Every `[ESL-PROPOSAL]`\n  item cites a `FINDING-XXX`\u002F`GAP-XXX` + its `path:line` anchor (I-7). No new\n  claims are introduced at this hop.\n- **Graceful skip.** No `.spectra\u002F` directory, or no change-worthy finding →\n  skip silently, emit `scout-report.md` normally. ESL is opt-in.\n\n---\n\n*ATLAS — ESL Lifecycle Hop (the DISCOVER hop; upstream of `proposed`, never a maker)*\n","# ATLAS — ESL Lifecycle Hop (the DISCOVER hop)\n\n## When to use\n\nLoad at Phase S (Synthesize), after the fold is validated and before\n`scout-report.md` is finalized, when **both** hold:\n\n- **Change-worthy signal.** ≥1 finding in `findings.md` asserts something is\n  broken, drifted, or missing relative to a spec\u002Fexpectation the mission\n  surfaced — not merely descriptive topology. See \"What counts as\n  change-worthy\" below.\n- **ESL-enabled project.** A `.spectra\u002F` directory exists at the consumer\n  project root — checked with a single read-only `list_dir` probe, never an\n  MCP call. ATLAS has no `mcp__tonberry__*` tool surface and never acquires\n  one.\n\nIf either condition is false, skip this skill silently and emit\n`scout-report.md` the normal way (`skills\u002Fsynthesize\u002FSKILL.md`). ESL is opt-in;\nATLAS is EIIS-standalone-conformant and works without it.\n\n## What counts as change-worthy\n\nA finding is change-worthy when its claim is one of:\n\n- a **defect** — behavior contradicts a spec, contract, or documented\n  invariant;\n- a **drift** — an implementation and its governing spec\u002Fdoc have diverged;\n- a **gap** — a required capability, test, or safeguard is absent.\n\nPurely descriptive findings (\"X calls Y at `path:line`\") are not\nchange-worthy on their own. When uncertain, the mission's own `GAPS`\u002F`RISKS`\nframing (scout-report §5) is the signal — anything already flagged there as\nneeding a decision or a fix is change-worthy by definition.\n\n## Your hop — DISCOVER (`proposed`), never MAKE\n\nYou are the furthest-upstream Eidolon in the ESL chain. You do **not** call\n`mcp__tonberry__*` — right-sizing, opening the `change.json` record, and\nrunning S→P→E→C→T→R→A belong to **SPECTRA's own hop**\n(`skills\u002Fesl-hop\u002FSKILL.md` in the SPECTRA repo), triggered when it receives your\nhand-off. Your job stops at **naming the change-worthy finding and handing it\noff** — the refusal boundary (P0 rule 1: read-only, no\n`edit`\u002F`write`\u002F`commit`\u002F`deploy`\u002F`migrate`\u002F`refactor`\u002F`fix`) stays fully\nintact: you never create, edit, or transition ESL state yourself.\n\n1. **flag the proposal in §4.** In `scout-report.md` §4 \"Recommended next\n   actions\", tag every change-worthy `R-N` item `[→ SPECTRA]` with an\n   explicit `[ESL-PROPOSAL]` marker naming the `FINDING-XXX`\u002F`GAP-XXX` it\n   rests on, and state plainly that the item proposes opening an ESL change\n   at `proposed`. This is the same artifact Phase S already emits — no new\n   file, no new schema.\n2. **frame the envelope objective.** In `scout-report.envelope.json`, set\n   `performative: \"PROPOSE\"` (the existing default for ATLAS→SPECTRA) and\n   word `objective` to name the ESL proposal intent, e.g. `\"Deliver scout\n   report for mission \u003Cid>, proposing an ESL change at 'proposed' for\n   FINDING-003\u002FFINDING-007.\"`. The `ise` block is unchanged from the standard\n   scout-report emission (`skills\u002Fsynthesize\u002FSKILL.md` \"Envelope sidecar\"):\n   `ise.assertion_grade: \"self-attested\"` and\n   `ise.receiver_authorization: {auto_route: true, auto_merge: false,\n   auto_deploy: false}` — SPECTRA MAY auto-route the finding into its own ESL\n   intake without an operator confirm, but MUST NOT auto-merge or\n   auto-deploy anything off an ATLAS-originated discovery.\n3. **hand off via the existing edge.** Deliver `scout-report.md` +\n   `scout-report.envelope.json` to SPECTRA exactly as `skills\u002Fsynthesize\u002FSKILL.md`\n   already prescribes (`contracts\u002Fatlas-to-spectra.yaml`,\n   `artifact.kind: scout-report`, unchanged). SPECTRA's `spectra-esl-hop`\n   skill (when `.spectra\u002F` and tonberry are present on its side) takes it\n   from there: right_size → propose → specify.\n\n## Invariants\n\n- **Refusal boundary intact.** ATLAS never calls a tonberry write verb\n  (`propose`, `transition`, `archive`, `verify`) and never touches\n  `.spectra\u002Fchanges\u002F`. This hop is discovery framing on an artifact ATLAS\n  already emits, not a new write surface.\n- **SPECTRA owns `proposed`.** The actual `change.json` at `proposed` status\n  is created by SPECTRA's hop, never ATLAS's. ATLAS's contribution is\n  evidence carried across the existing roster edge\n  (`contracts\u002Fatlas-to-spectra.yaml`), not a tonberry-recognized object.\n- **No new artifact kind, no new contract.** The proposal rides inside the\n  standard `scout-report` artifact\u002Fenvelope pair — inventing a distinct ECL\n  `artifact.kind` here would require a contract change outside ATLAS's repo;\n  this hop deliberately does not do that.\n- **Evidence-anchored, same as every ATLAS claim.** Every `[ESL-PROPOSAL]`\n  item cites a `FINDING-XXX`\u002F`GAP-XXX` + its `path:line` anchor (I-7). No new\n  claims are introduced at this hop.\n- **Graceful skip.** No `.spectra\u002F` directory, or no change-worthy finding →\n  skip silently, emit `scout-report.md` normally. ESL is opt-in.\n\n---\n\n*ATLAS — ESL Lifecycle Hop (the DISCOVER hop; upstream of `proposed`, never a maker)*\n",{"name":5,"metadata":24,"description":7},{"phase":25,"methodology":26},"S","ATLAS","main","38c3a82583abf9806de764f89ac0099ad690933a",".eidolons\u002Fatlas\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 atlas-esl-hop",{"tool":42,"command":43},"bunx","bunx skills add Rynaro\u002Fmagicite --skill atlas-esl-hop",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Rynaro\u002Fmagicite --skill atlas-esl-hop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fatlas\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",[],[]]