[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71S1BAFCVE3TJBJARFJTDX3":3,"skill-same:01M71S1BAFCVE3TJBJARFJTDX3":75},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M71S1BAFCVE3TJBJARFJTDX3","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\u002Fprisma","Rynaro","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5271543?v=4","01M70CFYFMB316W23THVQAQ42M","Henrique A. Lavezzo","01M71RXA8ZHEPZR3GERY09ERGD",1,"MIT","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fprisma\u002Fblob\u002Fmain\u002F.eidolons\u002Fgilgamesh\u002Fskills\u002Fgauge\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"gilgamesh gauge","gauge","keep","specialist","phase","authority","mission","verified","at","lock","intake","scale","fit","contract","cycle","do","gate","use","inventory","start","2026-11-10 13:02:02",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":49,"description":7},{"phase":50,"methodology":51},"G","Gilgamesh","main","42ce382409178ece647a93f841a86119e8d74a65",".eidolons\u002Fgilgamesh\u002Fskills\u002Fgauge",0,"https:\u002F\u002Fgithub.com\u002FRynaro\u002Fprisma","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-18 20:39:25",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Rynaro\u002Fprisma --skill gilgamesh-gauge",{"tool":67,"command":68},"bunx","bunx skills add Rynaro\u002Fprisma --skill gilgamesh-gauge",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Rynaro\u002Fprisma --skill gilgamesh-gauge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRynaro\u002Fprisma\u002Fblob\u002Fmain\u002F.eidolons\u002Fgilgamesh\u002Fskills\u002Fgauge\u002FSKILL.md",true,[],[76,103,130,154,183,204],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":44},"01M71S3X05FSJA01D22MH39Y0W","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\u002Fprisma\u002Fblob\u002Fmain\u002F.eidolons\u002Fvivi\u002Fskills\u002Fverify-incoming\u002FSKILL.md",[],[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"verify","vivi verify incoming","verify incoming","run","sha-256","json","orchestrator","process","dispatch","back","message","upstream","id","receiver","block","ecl","hand","load","for","when",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":112,"publishedAt":44},"01M71S3S2E46S6AZEV07AJ75TK","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\u002Fprisma\u002Fblob\u002Fmain\u002F.eidolons\u002Fvivi\u002Fskills\u002Fparallel-tracks\u002FSKILL.md",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务",[113,114,115,116,117,118,119,120,121,122,123,124,125,100,126,127,128,129,28,102],"parallel","tracks","parallel tracks","vivi parallel tracks","file","only","reflection","clean","plan phase","as","verifier","form","multi","worktree isolation","track","gating","single",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":44},"01M71S3N09VY1H2QHXXP4SKY2X","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\u002Fprisma\u002Fblob\u002Fmain\u002F.eidolons\u002Fvivi\u002Fskills\u002Fmethodology\u002FSKILL.md",[],[137,138,139,140,141,41,142,143,144,145,38,146,147,148,149,150,151,152,153,102],"methodology","vivi methodology","planning","escalation","Rules","evidence","complexity","delta","task","feature implementation","brownfield","full","requirements","feature","complete","thresholds","you",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":165,"publishedAt":44},"01M71S3GT0M84EHZ2SJZKV61N9","vivi-memory-management","Load at Vivi session start, session end, or when you notice a repeating pattern across tasks. CRYSTALIUM-primary memory protocol: when mcp__crystalium__* tools are available, route ALL memory through CRYSTALIUM (recall\u002Fcommit\u002Fingest\u002Fplan_checkpoint\u002Fsession_end). The local agents\u002Fmemories\u002F*.md files are the standalone fallback for when CRYSTALIUM is absent — EIIS conformance. Never write both.","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fprisma\u002Fblob\u002Fmain\u002F.eidolons\u002Fvivi\u002Fskills\u002Fmemory-management\u002FSKILL.md",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":163,"taxonomyTypeDesc":164},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,153,182,32,102],"memory","management","memory management","vivi memory management","MCP","commit","tasks","plan","write","never","files","route","across","local","end","session start","standalone",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":44},"01M71S3E067YRRFH7304VYYF32","vivi-loop-native","Load in Vivi's V (Verify) phase. The core capability that distinguishes Vivi from its predecessor APIVR-Δ: drive the closed, autonomous, bounded edit-run-test loop (`eidolons sandbox loop`) as its `--fix-hook`, consuming localized feedback, retrying in fresh context, refusing to game the tests, and gating on pass^k. Use whenever the task has an executable test oracle and a loop-competent host.","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fprisma\u002Fblob\u002Fmain\u002F.eidolons\u002Fvivi\u002Fskills\u002Floop-native\u002FSKILL.md",[],[190,191,192,193,194,195,196,197,198,199,200,41,145,201,122,202,203,100,128,28],"loop","native","vivi loop native","oracle","sandbox","test","core","game","feedback","autonomous","fix","tests","fresh","host",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":210,"publishedAt":44},"01M71S3AEKYH0JD0CFJ4GHA98E","vivi-failure-recovery","Load when the Vivi Verify phase produces failures — test fails, lint error, build break, or three consecutive unsuccessful attempts at the same category. Provides the failure classification taxonomy, bounded debugging protocol, and escalation thresholds. Use to avoid the 'random retries' anti-pattern.","https:\u002F\u002Fgithub.com\u002FRynaro\u002Fprisma\u002Fblob\u002Fmain\u002F.eidolons\u002Fvivi\u002Fskills\u002Ffailure-recovery\u002FSKILL.md",[],[211,212,213,140,214,215,41,216,217,152,218,219,220,100,32,221,222,28,102,223],"recovery","vivi failure recovery","debugging","classification","taxonomy","three","pattern","error","retries","random","break","bounded","same"]