[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APX55ANJGPXV5ASGMNDX5E":3,"skill-same:01M7APX55ANJGPXV5ASGMNDX5E":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},"01M7APX55ANJGPXV5ASGMNDX5E","gilgamesh-gauge",null,"Phase G (Gauge) mission-intake gate — verifies the mission-contract, decides KEEP vs REFUSE at generalist scale (specialist-fit, over-authority, underspecified), and instantiates the six-row capability-authority table. Use once per mission at the start of every GILGAMESH cycle, after the inbound envelope is verified. Do NOT use during Inventory\u002FLock\u002FGrind\u002FAttest.","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\u002Fgilgamesh\u002Fskills\u002Fgauge\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gilgamesh-gauge\ndescription: Phase G (Gauge) mission-intake gate — verifies the mission-contract, decides KEEP vs REFUSE at generalist scale (specialist-fit, over-authority, underspecified), and instantiates the six-row capability-authority table. Use once per mission at the start of every GILGAMESH cycle, after the inbound envelope is verified. Do NOT use during Inventory\u002FLock\u002FGrind\u002FAttest.\nmetadata:\n  methodology: Gilgamesh\n  phase: G\n---\n\n# Gauge Skill — Gilgamesh (Phase G intake)\n\n## When to use\n\nLoad during Phase G (Gauge). Runs once per mission, immediately after\n`skills\u002Fverify-incoming\u002FSKILL.md` passes. Triage cost ≈ 1 step. Do not load during\nInventory, Lock, Grind, or Attest.\n\nGauge is the additive-proof gate: Gilgamesh only spends cycles on missions it can\nplausibly win **and** that fit no specialist. Every misfit bounces cheaply, keeping the\nfallthrough seat structurally non-negative to the orchestrator's session — and keeping\nit from becoming a dumping ground (the identity-drift risk, R-032).\n\n---\n\n## Decision Tree (run in order — first failure exits)\n\n### Step 1 — Validate the mission-contract\n\nValidate the inbound payload against `schemas\u002Fmission-contract.v1.json`. It MUST carry\n`{objective, scope(paths,mode), deliverables, evidence_required, stop_conditions,\nauthority(read\u002Fwrite\u002Fexec\u002Fnetwork\u002Fsecrets\u002Fdeploy)}`.\n\n- **Valid** → continue to Step 2.\n- **Malformed \u002F missing fields** → `REFUSE{SCHEMA_INVALID}`.\n\n### Step 2 — Specialist-fit check (keep-or-kick at generalist scale)\n\nDoes the mission map **cleanly** to a roster specialist? Gilgamesh never outranks a\nspecialist and never enters Step-1 of dispatch (R-019) — it lives only in the\nfallthrough branch.\n\n| If the mission is… | REFUSE and suggest |\n|---|---|\n| a read-only discovery \u002F scout | `atlas` |\n| a plan \u002F spec authoring campaign | `ramza` |\n| a loop-native coding campaign (implement feature end-to-end) | `vivi` |\n| a localized ≤2-file verifier-backed micro-edit | `kupo` |\n| a root-cause \u002F defect hunt | `vigil` |\n| a decision record \u002F trade-off adjudication | `forge` |\n| a document \u002F long-form artefact | `idg` |\n\n- **Clean specialist fit** → `REFUSE{SPECIALIST_FIT, suggested_specialist: \u003Cname>}`.\n- **Underspecified \u002F ambiguous target** → `REFUSE{UNDERSPECIFIED}` (the orchestrator\n  emits a `clarification_request`).\n- **Actionable and fits no specialist** → continue to Step 3.\n\n### Step 3 — Instantiate the capability-authority table\n\nInstantiate `schemas\u002Fcapability-authority.v1.json` from the contract's `authority`\ngrant. Six rows × two columns (default \u002F escalation):\n\n| Row | Default | Escalation ceiling |\n|---|---|---|\n| read | scoped repo + tool output | broaden `scope.paths` (approved) |\n| write | sandbox only | none — PROPOSE-only is constitutional |\n| exec | named oracle commands in sandbox | more oracle commands (approved, sandboxed) |\n| network | none | proxied read via broker (approved) |\n| secrets | none | broker-issued, single-use, mission-scoped |\n| deploy | none | **never-grantable** |\n\n- If the mission requires authority **above the ceiling** — most importantly **deploy**,\n  or a secret the table cannot broker — `REFUSE{OVER_AUTHORITY}`.\n- Otherwise freeze the instantiated table into `TaskState.authority` and **KEEP**.\n\n---\n\n## Output format\n\nEmit exactly one of:\n\n```\nKEEP{authority: \u003Cinstantiated capability-authority table>}\n```\n```\nREFUSE{code: \"\u003CSCHEMA_INVALID|SPECIALIST_FIT|UNDERSPECIFIED|OVER_AUTHORITY|NOT_ROUTER|NO_ORACLE>\", suggested_specialist: \"\u003Cname|null>\", note: \"\u003Cone sentence for the orchestrator>\"}\n```\n\nOn KEEP, control passes to Phase I (Inventory). No other state from Gauge enters\nInventory except the frozen authority table; Gauge is a one-shot gate.\n\n---\n\n## Notes\n\n- **Triage cost ≈ 1 step.** Gauge must be cheap; do not invoke atlas-aci here — gather\n  happens in Inventory.\n- **Structural, not verbal.** KEEP iff the contract validates, fits no specialist, and\n  stays within the grantable ceiling. \"It looks doable\" is not a KEEP predicate.\n- **Specialist-preferring by construction.** When in doubt between KEEP and\n  `SPECIALIST_FIT`, prefer the specialist — the orchestrator can always re-route back.\n- **Deploy is a wall, not a slope.** No mission, no escalation, no operator override\n  reachable from within Gilgamesh grants deploy. Route it upward if it is truly needed.\n- **REFUSE is cheap and correct.** A fast REFUSE with a suggested specialist is more\n  valuable than a slow, out-of-scope grind.\n\n---\n\n*Gauge Skill — Gilgamesh Phase G intake, refusal, and authority instantiation*\n","# Gauge Skill — Gilgamesh (Phase G intake)\n\n## When to use\n\nLoad during Phase G (Gauge). Runs once per mission, immediately after\n`skills\u002Fverify-incoming\u002FSKILL.md` passes. Triage cost ≈ 1 step. Do not load during\nInventory, Lock, Grind, or Attest.\n\nGauge is the additive-proof gate: Gilgamesh only spends cycles on missions it can\nplausibly win **and** that fit no specialist. Every misfit bounces cheaply, keeping the\nfallthrough seat structurally non-negative to the orchestrator's session — and keeping\nit from becoming a dumping ground (the identity-drift risk, R-032).\n\n---\n\n## Decision Tree (run in order — first failure exits)\n\n### Step 1 — Validate the mission-contract\n\nValidate the inbound payload against `schemas\u002Fmission-contract.v1.json`. It MUST carry\n`{objective, scope(paths,mode), deliverables, evidence_required, stop_conditions,\nauthority(read\u002Fwrite\u002Fexec\u002Fnetwork\u002Fsecrets\u002Fdeploy)}`.\n\n- **Valid** → continue to Step 2.\n- **Malformed \u002F missing fields** → `REFUSE{SCHEMA_INVALID}`.\n\n### Step 2 — Specialist-fit check (keep-or-kick at generalist scale)\n\nDoes the mission map **cleanly** to a roster specialist? Gilgamesh never outranks a\nspecialist and never enters Step-1 of dispatch (R-019) — it lives only in the\nfallthrough branch.\n\n| If the mission is… | REFUSE and suggest |\n|---|---|\n| a read-only discovery \u002F scout | `atlas` |\n| a plan \u002F spec authoring campaign | `ramza` |\n| a loop-native coding campaign (implement feature end-to-end) | `vivi` |\n| a localized ≤2-file verifier-backed micro-edit | `kupo` |\n| a root-cause \u002F defect hunt | `vigil` |\n| a decision record \u002F trade-off adjudication | `forge` |\n| a document \u002F long-form artefact | `idg` |\n\n- **Clean specialist fit** → `REFUSE{SPECIALIST_FIT, suggested_specialist: \u003Cname>}`.\n- **Underspecified \u002F ambiguous target** → `REFUSE{UNDERSPECIFIED}` (the orchestrator\n  emits a `clarification_request`).\n- **Actionable and fits no specialist** → continue to Step 3.\n\n### Step 3 — Instantiate the capability-authority table\n\nInstantiate `schemas\u002Fcapability-authority.v1.json` from the contract's `authority`\ngrant. Six rows × two columns (default \u002F escalation):\n\n| Row | Default | Escalation ceiling |\n|---|---|---|\n| read | scoped repo + tool output | broaden `scope.paths` (approved) |\n| write | sandbox only | none — PROPOSE-only is constitutional |\n| exec | named oracle commands in sandbox | more oracle commands (approved, sandboxed) |\n| network | none | proxied read via broker (approved) |\n| secrets | none | broker-issued, single-use, mission-scoped |\n| deploy | none | **never-grantable** |\n\n- If the mission requires authority **above the ceiling** — most importantly **deploy**,\n  or a secret the table cannot broker — `REFUSE{OVER_AUTHORITY}`.\n- Otherwise freeze the instantiated table into `TaskState.authority` and **KEEP**.\n\n---\n\n## Output format\n\nEmit exactly one of:\n\n```\nKEEP{authority: \u003Cinstantiated capability-authority table>}\n```\n```\nREFUSE{code: \"\u003CSCHEMA_INVALID|SPECIALIST_FIT|UNDERSPECIFIED|OVER_AUTHORITY|NOT_ROUTER|NO_ORACLE>\", suggested_specialist: \"\u003Cname|null>\", note: \"\u003Cone sentence for the orchestrator>\"}\n```\n\nOn KEEP, control passes to Phase I (Inventory). No other state from Gauge enters\nInventory except the frozen authority table; Gauge is a one-shot gate.\n\n---\n\n## Notes\n\n- **Triage cost ≈ 1 step.** Gauge must be cheap; do not invoke atlas-aci here — gather\n  happens in Inventory.\n- **Structural, not verbal.** KEEP iff the contract validates, fits no specialist, and\n  stays within the grantable ceiling. \"It looks doable\" is not a KEEP predicate.\n- **Specialist-preferring by construction.** When in doubt between KEEP and\n  `SPECIALIST_FIT`, prefer the specialist — the orchestrator can always re-route back.\n- **Deploy is a wall, not a slope.** No mission, no escalation, no operator override\n  reachable from within Gilgamesh grants deploy. Route it upward if it is truly needed.\n- **REFUSE is cheap and correct.** A fast REFUSE with a suggested specialist is more\n  valuable than a slow, out-of-scope grind.\n\n---\n\n*Gauge Skill — Gilgamesh Phase G intake, refusal, and authority instantiation*\n",{"name":5,"metadata":24,"description":7},{"phase":25,"methodology":26},"G","Gilgamesh","main","38c3a82583abf9806de764f89ac0099ad690933a",".eidolons\u002Fgilgamesh\u002Fskills\u002Fgauge",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 gilgamesh-gauge",{"tool":42,"command":43},"bunx","bunx skills add Rynaro\u002Fmagicite --skill gilgamesh-gauge",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Rynaro\u002Fmagicite --skill gilgamesh-gauge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fgilgamesh\u002Fskills\u002Fgauge\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",[],[]]