[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQ1TBP9SMDX3KYRS84P8SD":3,"skill-same:01M7AQ1TBP9SMDX3KYRS84P8SD":51},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7AQ1TBP9SMDX3KYRS84P8SD","vigil-isolate",null,"Phase I (Isolate) — narrows the fault surface to ≤8 candidate nodes via delta-debugging-style reduction. Preserves failure throughout reduction; records ruled-out evidence. Use after `reproduction.md` is stable and `DETERMINISM_VERDICT ≠ intermittent`, before the Graph phase.","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\u002Fisolate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vigil-isolate\ndescription: Phase I (Isolate) — narrows the fault surface to ≤8 candidate nodes via delta-debugging-style reduction. Preserves failure throughout reduction; records ruled-out evidence. Use after `reproduction.md` is stable and `DETERMINISM_VERDICT ≠ intermittent`, before the Graph phase.\nallowed-tools: git_bisect, git_log, view_file, search_symbol, search_text, run_test, dep_graph_query\nmetadata:\n  methodology: VIGIL\n  phase: I\n---\n\n# SKILL: Isolate — narrow the fault surface\n\n## When to use\n\nLoad when `reproduction.md` is schema-valid and stable. Unload when `fault-surface.md` has ≤8 candidates with evidence anchors.\n\n> **Memory check:** if `recall` fired in Phase V, its results are already in\n> context — consult them when building the initial suspect set. Procedural\n> memories from prior missions on similar error classes can shortcut Source 2\n> (recent churn) and Source 3 (scope bounds) below. If `mcp__crystalium__*`\n> tools are unavailable, proceed without memory — never hard-fail.\n\n---\n\n## Contract\n\n| Field | Value |\n|-------|-------|\n| LLM calls permitted | For classifying candidates and reading source |\n| Tool budget | ≤25% of mission budget |\n| Output | `fault-surface.md` — schema-valid per `schemas\u002Ffault-surface.v1.json` |\n| Hard cap | ≤8 candidates. If more survive reduction, narrow scope; if fewer than 1 survives, escalate. |\n\n---\n\n## The Suspect Set — Where to Look First\n\nBuild the initial suspect set from three deterministic sources. Do not enumerate the entire codebase.\n\n### Source 1 — Stack trace closure\n\nEvery file referenced in the failing stack trace (from `reproduction.md`) is a suspect. For each frame:\n\n- The file itself → suspect\n- Files it imports → secondary suspects if the failure is a `RUNTIME_ERROR` or `INTEGRATION_ERROR`\n- Call-graph ancestors (who calls this) → tertiary suspects for `LOGIC_ERROR`\n\n### Source 2 — Recent churn\n\nFor the commit at which the failure reproduces:\n\n```\ngit log --since=\"30 days ago\" --oneline --name-only\n```\n\nCross-reference churn with Source 1. Files that are **both** in the stack trace AND recently modified are the highest-priority suspects.\n\nFor `REGRESSION` category: add `git bisect` to identify the introducing commit. Files touched by that commit become top suspects.\n\n### Source 3 — Scope bounds from upstream\n\nIf upstream artifact (APIVR-Δ `repair-failed-report.md`, spec, or scout-report from ATLAS) declared a scope, respect it. Candidates outside the declared scope require explicit justification (e.g., \"symptom traces cross the boundary because of [evidence]\").\n\n---\n\n## Reduction Techniques (Category-Specific)\n\n### `REGRESSION` — use git bisect\n\nBisect between last known good commit and current. Each iteration:\n\n1. Check out midpoint\n2. Run reproduction command\n3. Record `PASS` or `FAIL_MATCH`\n4. Narrow\n\nTerminates at the introducing commit. The diff of that commit is the highest-priority candidate set.\n\n### `LOGIC_ERROR`, `TYPE_ERROR`, `RUNTIME_ERROR` — use dependency walk\n\nStarting from the failing assertion's location:\n\n1. Identify all variables\u002Ffunctions read in the failing code path\n2. For each, identify its origin (where it's assigned, returned from, passed in)\n3. Walk backward until you hit a boundary — user input, IO, constant, or unmodified upstream code\n4. Each node in this walk is a candidate\n\n### `INTEGRATION_ERROR` — use contract comparison\n\nThe failure is at a component boundary. Candidates are:\n\n- The producer's output schema\u002Fcontract (actual vs declared)\n- The consumer's input expectations (actual vs declared)\n- Any serialization layer between them\n\n### `BUILD_ERROR`, `LINT_VIOLATION` — direct diagnosis\n\nThe tooling has already identified the file:line. The \"isolation\" is trivial. Proceed to Graph with the tooling-reported location as the single candidate.\n\n### `HEISENBUG` — use timing\u002Fstate differential\n\nWith statistical-mode reproduction, run 5× with increased logging. Compare state at key checkpoints across runs:\n\n- What differs between failing and passing runs?\n- Are there race windows? Shared state mutations? External clock\u002Frandom dependencies?\n\nCandidates are the loci where observable state diverges between passing and failing runs.\n\n### `COMPOUND` — accept >1 root candidate\n\nCompound failures have multiple independent roots. Do not force reduction below 2 candidates. Mark them for the Graph phase to confirm independence.\n\n### `SPEC_DEFECT` — validate test intent\n\nDoes the test assert the correct thing? Compare test expectation to:\n\n- The spec (if available — from SPECTRA handoff or issue tracker)\n- Other tests covering the same behavior\n- Recent spec changes\n\nIf the test is wrong, the \"fix\" routes to SPECTRA, not APIVR-Δ.\n\n---\n\n## Ruled-Out Trail — First-Class Evidence\n\nFor every candidate you **remove** from the suspect set, record why. This is not noise — it's the most important output of Phase I.\n\nRequired ruled-out records:\n\n```yaml\nruled_out:\n  - candidate: \"app\u002Fflows\u002Fauth.rb:120-180\"\n    reason: \"Not in stack trace; not modified in last 90 days; called from unrelated path.\"\n    evidence_source: \"git log + stack trace\"\n  - candidate: \"lib\u002Futils\u002Fclock.rb:*\"\n    reason: \"Failing test uses frozen time via test helper; clock utility not reached.\"\n    evidence_source: \"test_helper.rb:12; dep_graph_query(callers_of: Clock.now)\"\n```\n\nMinimum: 3 ruled-out entries per mission. Missions with fewer suggest lazy reduction; harness flags for review.\n\n---\n\n## Writing `fault-surface.md`\n\n```yaml\nmission_id: VIGIL-YYYYMMDD-NNN\nupstream_reproduction: \u003Cref>\nsuspect_set_sources:\n  - stack_trace_closure\n  - recent_churn\n  - scope_bounds\ncandidates:\n  - id: C-001\n    path: \"app\u002Fflows\u002Fvote_casting\u002Frecord_vote.rb\"\n    lines: \"42-78\"\n    kind: code            # code | test | config | schema | data | env\n    suspicion_rank: 1     # 1 = highest\n    rationale: \"Top of failing stack; modified 3 days ago in commit abc123; writes the asserted-against column\"\n  - id: C-002\n    path: \"app\u002Fpolicies\u002Fvoting_authorizer.rb\"\n    lines: \"12-40\"\n    kind: code\n    suspicion_rank: 2\n    rationale: \"Delegate target of C-001; recently modified; appears in stack frame 2\"\nreduction_trail:\n  - step: \"Stack trace closure produced 17 suspects\"\n  - step: \"Churn filter reduced to 8\"\n  - step: \"Scope bounds (auth module only) reduced to 5\"\n  - step: \"Dependency walk confirmed 2 additional candidates outside initial stack\"\nruled_out:\n  - \u003Cas above, minimum 3 entries>\nscope_bounds:\n  include: [\"app\u002Fflows\u002F**\", \"app\u002Fpolicies\u002F**\"]\n  exclude: [\"spec\u002F**\", \"lib\u002Flegacy\u002F**\"]\n```\n\n---\n\n## Anti-patterns\n\n- **Reading entire files.** Windowed reads only, after narrowing by symbol or graph query.\n- **Inferring candidates.** Every candidate needs a path:lines anchor and a traceable reason.\n- **Cascading reduction too aggressively.** If you're down to 0 candidates, you reduced wrong — escalate.\n- **Chasing a candidate because it \"looks suspicious.\"** Anchor the suspicion in stack trace, churn, or dep graph. Vibes are not evidence.\n- **Skipping ruled-out records.** The next VIGIL mission on related code will thank you.\n\n---\n\n*VIGIL Phase I — reduction with evidence, ≤8 candidates to Graph*\n","# SKILL: Isolate — narrow the fault surface\n\n## When to use\n\nLoad when `reproduction.md` is schema-valid and stable. Unload when `fault-surface.md` has ≤8 candidates with evidence anchors.\n\n> **Memory check:** if `recall` fired in Phase V, its results are already in\n> context — consult them when building the initial suspect set. Procedural\n> memories from prior missions on similar error classes can shortcut Source 2\n> (recent churn) and Source 3 (scope bounds) below. If `mcp__crystalium__*`\n> tools are unavailable, proceed without memory — never hard-fail.\n\n---\n\n## Contract\n\n| Field | Value |\n|-------|-------|\n| LLM calls permitted | For classifying candidates and reading source |\n| Tool budget | ≤25% of mission budget |\n| Output | `fault-surface.md` — schema-valid per `schemas\u002Ffault-surface.v1.json` |\n| Hard cap | ≤8 candidates. If more survive reduction, narrow scope; if fewer than 1 survives, escalate. |\n\n---\n\n## The Suspect Set — Where to Look First\n\nBuild the initial suspect set from three deterministic sources. Do not enumerate the entire codebase.\n\n### Source 1 — Stack trace closure\n\nEvery file referenced in the failing stack trace (from `reproduction.md`) is a suspect. For each frame:\n\n- The file itself → suspect\n- Files it imports → secondary suspects if the failure is a `RUNTIME_ERROR` or `INTEGRATION_ERROR`\n- Call-graph ancestors (who calls this) → tertiary suspects for `LOGIC_ERROR`\n\n### Source 2 — Recent churn\n\nFor the commit at which the failure reproduces:\n\n```\ngit log --since=\"30 days ago\" --oneline --name-only\n```\n\nCross-reference churn with Source 1. Files that are **both** in the stack trace AND recently modified are the highest-priority suspects.\n\nFor `REGRESSION` category: add `git bisect` to identify the introducing commit. Files touched by that commit become top suspects.\n\n### Source 3 — Scope bounds from upstream\n\nIf upstream artifact (APIVR-Δ `repair-failed-report.md`, spec, or scout-report from ATLAS) declared a scope, respect it. Candidates outside the declared scope require explicit justification (e.g., \"symptom traces cross the boundary because of [evidence]\").\n\n---\n\n## Reduction Techniques (Category-Specific)\n\n### `REGRESSION` — use git bisect\n\nBisect between last known good commit and current. Each iteration:\n\n1. Check out midpoint\n2. Run reproduction command\n3. Record `PASS` or `FAIL_MATCH`\n4. Narrow\n\nTerminates at the introducing commit. The diff of that commit is the highest-priority candidate set.\n\n### `LOGIC_ERROR`, `TYPE_ERROR`, `RUNTIME_ERROR` — use dependency walk\n\nStarting from the failing assertion's location:\n\n1. Identify all variables\u002Ffunctions read in the failing code path\n2. For each, identify its origin (where it's assigned, returned from, passed in)\n3. Walk backward until you hit a boundary — user input, IO, constant, or unmodified upstream code\n4. Each node in this walk is a candidate\n\n### `INTEGRATION_ERROR` — use contract comparison\n\nThe failure is at a component boundary. Candidates are:\n\n- The producer's output schema\u002Fcontract (actual vs declared)\n- The consumer's input expectations (actual vs declared)\n- Any serialization layer between them\n\n### `BUILD_ERROR`, `LINT_VIOLATION` — direct diagnosis\n\nThe tooling has already identified the file:line. The \"isolation\" is trivial. Proceed to Graph with the tooling-reported location as the single candidate.\n\n### `HEISENBUG` — use timing\u002Fstate differential\n\nWith statistical-mode reproduction, run 5× with increased logging. Compare state at key checkpoints across runs:\n\n- What differs between failing and passing runs?\n- Are there race windows? Shared state mutations? External clock\u002Frandom dependencies?\n\nCandidates are the loci where observable state diverges between passing and failing runs.\n\n### `COMPOUND` — accept >1 root candidate\n\nCompound failures have multiple independent roots. Do not force reduction below 2 candidates. Mark them for the Graph phase to confirm independence.\n\n### `SPEC_DEFECT` — validate test intent\n\nDoes the test assert the correct thing? Compare test expectation to:\n\n- The spec (if available — from SPECTRA handoff or issue tracker)\n- Other tests covering the same behavior\n- Recent spec changes\n\nIf the test is wrong, the \"fix\" routes to SPECTRA, not APIVR-Δ.\n\n---\n\n## Ruled-Out Trail — First-Class Evidence\n\nFor every candidate you **remove** from the suspect set, record why. This is not noise — it's the most important output of Phase I.\n\nRequired ruled-out records:\n\n```yaml\nruled_out:\n  - candidate: \"app\u002Fflows\u002Fauth.rb:120-180\"\n    reason: \"Not in stack trace; not modified in last 90 days; called from unrelated path.\"\n    evidence_source: \"git log + stack trace\"\n  - candidate: \"lib\u002Futils\u002Fclock.rb:*\"\n    reason: \"Failing test uses frozen time via test helper; clock utility not reached.\"\n    evidence_source: \"test_helper.rb:12; dep_graph_query(callers_of: Clock.now)\"\n```\n\nMinimum: 3 ruled-out entries per mission. Missions with fewer suggest lazy reduction; harness flags for review.\n\n---\n\n## Writing `fault-surface.md`\n\n```yaml\nmission_id: VIGIL-YYYYMMDD-NNN\nupstream_reproduction: \u003Cref>\nsuspect_set_sources:\n  - stack_trace_closure\n  - recent_churn\n  - scope_bounds\ncandidates:\n  - id: C-001\n    path: \"app\u002Fflows\u002Fvote_casting\u002Frecord_vote.rb\"\n    lines: \"42-78\"\n    kind: code            # code | test | config | schema | data | env\n    suspicion_rank: 1     # 1 = highest\n    rationale: \"Top of failing stack; modified 3 days ago in commit abc123; writes the asserted-against column\"\n  - id: C-002\n    path: \"app\u002Fpolicies\u002Fvoting_authorizer.rb\"\n    lines: \"12-40\"\n    kind: code\n    suspicion_rank: 2\n    rationale: \"Delegate target of C-001; recently modified; appears in stack frame 2\"\nreduction_trail:\n  - step: \"Stack trace closure produced 17 suspects\"\n  - step: \"Churn filter reduced to 8\"\n  - step: \"Scope bounds (auth module only) reduced to 5\"\n  - step: \"Dependency walk confirmed 2 additional candidates outside initial stack\"\nruled_out:\n  - \u003Cas above, minimum 3 entries>\nscope_bounds:\n  include: [\"app\u002Fflows\u002F**\", \"app\u002Fpolicies\u002F**\"]\n  exclude: [\"spec\u002F**\", \"lib\u002Flegacy\u002F**\"]\n```\n\n---\n\n## Anti-patterns\n\n- **Reading entire files.** Windowed reads only, after narrowing by symbol or graph query.\n- **Inferring candidates.** Every candidate needs a path:lines anchor and a traceable reason.\n- **Cascading reduction too aggressively.** If you're down to 0 candidates, you reduced wrong — escalate.\n- **Chasing a candidate because it \"looks suspicious.\"** Anchor the suspicion in stack trace, churn, or dep graph. Vibes are not evidence.\n- **Skipping ruled-out records.** The next VIGIL mission on related code will thank you.\n\n---\n\n*VIGIL Phase I — reduction with evidence, ≤8 candidates to Graph*\n",{"name":5,"metadata":24,"description":7,"allowed-tools":27},{"phase":25,"methodology":26},"I","VIGIL","git_bisect, git_log, view_file, search_symbol, search_text, run_test, dep_graph_query","main","38c3a82583abf9806de764f89ac0099ad690933a",".eidolons\u002Fvigil\u002Fskills\u002Fisolate",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Rynaro\u002Fmagicite --skill vigil-isolate",{"tool":43,"command":44},"bunx","bunx skills add Rynaro\u002Fmagicite --skill vigil-isolate",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Rynaro\u002Fmagicite --skill vigil-isolate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRynaro\u002Fmagicite\u002Fblob\u002Fmain\u002F.eidolons\u002Fvigil\u002Fskills\u002Fisolate\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]