[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D80MB0REX1V2W28WKF85G8":3,"skill-same:01M7D80MB0REX1V2W28WKF85G8":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7D80MB0REX1V2W28WKF85G8","extract",null,"Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.","Mabbit143\u002FClaude-SKills","Mabbit143","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192994237?v=4","01M7D6X2W63K4T3N13CSVAKE3V","Mabbit Rountree","01M7D6X2WRPSZF8VMW9MW5ZP1X",0,"MIT","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Fextract\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"extract\"\ndescription: \"Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.\"\n---\n\n# \u002Fsi:extract — Create Skills from Patterns\n\nTransforms a recurring pattern or debugging solution into a standalone, portable skill that can be installed in any project.\n\n## Usage\n\n```\n\u002Fsi:extract \u003Cpattern description>                  # Interactive extraction\n\u002Fsi:extract \u003Cpattern> --name docker-m1-fixes       # Specify skill name\n\u002Fsi:extract \u003Cpattern> --output .\u002Fskills\u002F            # Custom output directory\n\u002Fsi:extract \u003Cpattern> --dry-run                     # Preview without creating files\n```\n\n## When to Extract\n\nA learning qualifies for skill extraction when ANY of these are true:\n\n| Criterion | Signal |\n|---|---|\n| **Recurring** | Same issue across 2+ projects |\n| **Non-obvious** | Required real debugging to discover |\n| **Broadly applicable** | Not tied to one specific codebase |\n| **Complex solution** | Multi-step fix that's easy to forget |\n| **User-flagged** | \"Save this as a skill\", \"I want to reuse this\" |\n\n## Workflow\n\n### Step 1: Identify the pattern\n\nRead the user's description. Search auto-memory for related entries:\n\n```bash\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\ngrep -rni \"\u003Ckeywords>\" \"$MEMORY_DIR\u002F\"\n```\n\nIf found in auto-memory, use those entries as source material. If not, use the user's description directly.\n\n### Step 2: Determine skill scope\n\nAsk (max 2 questions):\n- \"What problem does this solve?\" (if not clear)\n- \"Should this include code examples?\" (if applicable)\n\n### Step 3: Generate skill name\n\nRules for naming:\n- Lowercase, hyphens between words\n- Descriptive but concise (2-4 words)\n- Examples: `docker-m1-fixes`, `api-timeout-patterns`, `pnpm-workspace-setup`\n\n**Reserved fragments — must NOT appear in the skill name:**\n- `claude`\n- `anthropic`\n\nFor skills about Claude Code itself, use the `cc-` prefix instead:\n- ❌ `claude-code-settings` → ✅ `cc-settings`\n- ❌ `claude-code-maintenance` → ✅ `cc-maintenance`\n- ❌ `claude-mcp-tools` → ✅ `cc-mcp-tools`\n- ❌ `claude-plugin-development` → ✅ `cc-plugin-development`\n\nBefore writing the skill directory, check the proposed name against this list.\nIf a reserved fragment is present, transform it (drop the fragment or replace\nthe `claude*`\u002F`anthropic*` prefix with `cc-`) and confirm with the user.\n\n### Step 4: Create the skill files\n\n**Spawn the `skill-extractor` agent** for the actual file generation.\n\nThe agent creates:\n\n```\n\u003Cskill-name>\u002F\n├── SKILL.md            # Main skill file with frontmatter\n├── README.md           # Human-readable overview\n└── reference\u002F          # (optional) Supporting documentation\n    └── examples.md     # Concrete examples and edge cases\n```\n\n### Step 5: SKILL.md structure\n\nThe generated SKILL.md must follow this format:\n\n```markdown\n---\nname: \"skill-name\"\ndescription: \"\u003Cone-line description>. Use when: \u003Ctrigger conditions>.\"\n---\n\n# \u003CSkill Title>\n\n> One-line summary of what this skill solves.\n\n## Quick Reference\n\n| Problem | Solution |\n|---------|----------|\n| {{problem 1}} | {{solution 1}} |\n| {{problem 2}} | {{solution 2}} |\n\n## The Problem\n\n{{2-3 sentences explaining what goes wrong and why it's non-obvious.}}\n\n## Solutions\n\n### Option 1: {{Name}} (Recommended)\n\n{{Step-by-step with code examples.}}\n\n### Option 2: {{Alternative}}\n\n{{For when Option 1 doesn't apply.}}\n\n## Trade-offs\n\n| Approach | Pros | Cons |\n|----------|------|------|\n| Option 1 | {{pros}} | {{cons}} |\n| Option 2 | {{pros}} | {{cons}} |\n\n## Edge Cases\n\n- {{edge case 1 and how to handle it}}\n- {{edge case 2 and how to handle it}}\n```\n\n### Step 6: Quality gates\n\nBefore finalizing, verify:\n\n- [ ] SKILL.md has valid YAML frontmatter with `name` and `description`\n- [ ] `name` matches the folder name (lowercase, hyphens)\n- [ ] `name` does NOT contain reserved fragments `claude` or `anthropic` (use `cc-` prefix for Claude Code skills)\n- [ ] Description includes \"Use when:\" trigger conditions\n- [ ] Solutions are self-contained (no external context needed)\n- [ ] Code examples are complete and copy-pasteable\n- [ ] No project-specific hardcoded values (paths, URLs, credentials)\n- [ ] No unnecessary dependencies\n\n### Step 7: Report\n\n```\n✅ Skill extracted: {{skill-name}}\n\nFiles created:\n  {{path}}\u002FSKILL.md          ({{lines}} lines)\n  {{path}}\u002FREADME.md         ({{lines}} lines)\n  {{path}}\u002Freference\u002Fexamples.md  ({{lines}} lines)\n\nInstall: \u002Fplugin install (copy to your skills directory)\nPublish: clawhub publish {{path}}\n\nSource: MEMORY.md entries at lines {{n, m, ...}} (retained — the skill is portable, the memory is project-specific)\n```\n\n## Examples\n\n### Extracting a debugging pattern\n\n```\n\u002Fsi:extract \"Fix for Docker builds failing on Apple Silicon with platform mismatch\"\n```\n\nCreates `docker-m1-fixes\u002FSKILL.md` with:\n- The platform mismatch error message\n- Three solutions (build flag, Dockerfile, docker-compose)\n- Trade-offs table\n- Performance note about Rosetta 2 emulation\n\n### Extracting a workflow pattern\n\n```\n\u002Fsi:extract \"Always regenerate TypeScript API client after modifying OpenAPI spec\"\n```\n\nCreates `api-client-regen\u002FSKILL.md` with:\n- Why manual regen is needed\n- The exact command sequence\n- CI integration snippet\n- Common failure modes\n\n## Tips\n\n- Extract patterns that would save time in a *different* project\n- Keep skills focused — one problem per skill\n- Include the error messages people would search for\n- Test the skill by reading it without the original context — does it make sense?\n","# \u002Fsi:extract — Create Skills from Patterns\n\nTransforms a recurring pattern or debugging solution into a standalone, portable skill that can be installed in any project.\n\n## Usage\n\n```\n\u002Fsi:extract \u003Cpattern description>                  # Interactive extraction\n\u002Fsi:extract \u003Cpattern> --name docker-m1-fixes       # Specify skill name\n\u002Fsi:extract \u003Cpattern> --output .\u002Fskills\u002F            # Custom output directory\n\u002Fsi:extract \u003Cpattern> --dry-run                     # Preview without creating files\n```\n\n## When to Extract\n\nA learning qualifies for skill extraction when ANY of these are true:\n\n| Criterion | Signal |\n|---|---|\n| **Recurring** | Same issue across 2+ projects |\n| **Non-obvious** | Required real debugging to discover |\n| **Broadly applicable** | Not tied to one specific codebase |\n| **Complex solution** | Multi-step fix that's easy to forget |\n| **User-flagged** | \"Save this as a skill\", \"I want to reuse this\" |\n\n## Workflow\n\n### Step 1: Identify the pattern\n\nRead the user's description. Search auto-memory for related entries:\n\n```bash\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\ngrep -rni \"\u003Ckeywords>\" \"$MEMORY_DIR\u002F\"\n```\n\nIf found in auto-memory, use those entries as source material. If not, use the user's description directly.\n\n### Step 2: Determine skill scope\n\nAsk (max 2 questions):\n- \"What problem does this solve?\" (if not clear)\n- \"Should this include code examples?\" (if applicable)\n\n### Step 3: Generate skill name\n\nRules for naming:\n- Lowercase, hyphens between words\n- Descriptive but concise (2-4 words)\n- Examples: `docker-m1-fixes`, `api-timeout-patterns`, `pnpm-workspace-setup`\n\n**Reserved fragments — must NOT appear in the skill name:**\n- `claude`\n- `anthropic`\n\nFor skills about Claude Code itself, use the `cc-` prefix instead:\n- ❌ `claude-code-settings` → ✅ `cc-settings`\n- ❌ `claude-code-maintenance` → ✅ `cc-maintenance`\n- ❌ `claude-mcp-tools` → ✅ `cc-mcp-tools`\n- ❌ `claude-plugin-development` → ✅ `cc-plugin-development`\n\nBefore writing the skill directory, check the proposed name against this list.\nIf a reserved fragment is present, transform it (drop the fragment or replace\nthe `claude*`\u002F`anthropic*` prefix with `cc-`) and confirm with the user.\n\n### Step 4: Create the skill files\n\n**Spawn the `skill-extractor` agent** for the actual file generation.\n\nThe agent creates:\n\n```\n\u003Cskill-name>\u002F\n├── SKILL.md            # Main skill file with frontmatter\n├── README.md           # Human-readable overview\n└── reference\u002F          # (optional) Supporting documentation\n    └── examples.md     # Concrete examples and edge cases\n```\n\n### Step 5: SKILL.md structure\n\nThe generated SKILL.md must follow this format:\n\n```markdown\n---\nname: \"skill-name\"\ndescription: \"\u003Cone-line description>. Use when: \u003Ctrigger conditions>.\"\n---\n\n# \u003CSkill Title>\n\n> One-line summary of what this skill solves.\n\n## Quick Reference\n\n| Problem | Solution |\n|---------|----------|\n| {{problem 1}} | {{solution 1}} |\n| {{problem 2}} | {{solution 2}} |\n\n## The Problem\n\n{{2-3 sentences explaining what goes wrong and why it's non-obvious.}}\n\n## Solutions\n\n### Option 1: {{Name}} (Recommended)\n\n{{Step-by-step with code examples.}}\n\n### Option 2: {{Alternative}}\n\n{{For when Option 1 doesn't apply.}}\n\n## Trade-offs\n\n| Approach | Pros | Cons |\n|----------|------|------|\n| Option 1 | {{pros}} | {{cons}} |\n| Option 2 | {{pros}} | {{cons}} |\n\n## Edge Cases\n\n- {{edge case 1 and how to handle it}}\n- {{edge case 2 and how to handle it}}\n```\n\n### Step 6: Quality gates\n\nBefore finalizing, verify:\n\n- [ ] SKILL.md has valid YAML frontmatter with `name` and `description`\n- [ ] `name` matches the folder name (lowercase, hyphens)\n- [ ] `name` does NOT contain reserved fragments `claude` or `anthropic` (use `cc-` prefix for Claude Code skills)\n- [ ] Description includes \"Use when:\" trigger conditions\n- [ ] Solutions are self-contained (no external context needed)\n- [ ] Code examples are complete and copy-pasteable\n- [ ] No project-specific hardcoded values (paths, URLs, credentials)\n- [ ] No unnecessary dependencies\n\n### Step 7: Report\n\n```\n✅ Skill extracted: {{skill-name}}\n\nFiles created:\n  {{path}}\u002FSKILL.md          ({{lines}} lines)\n  {{path}}\u002FREADME.md         ({{lines}} lines)\n  {{path}}\u002Freference\u002Fexamples.md  ({{lines}} lines)\n\nInstall: \u002Fplugin install (copy to your skills directory)\nPublish: clawhub publish {{path}}\n\nSource: MEMORY.md entries at lines {{n, m, ...}} (retained — the skill is portable, the memory is project-specific)\n```\n\n## Examples\n\n### Extracting a debugging pattern\n\n```\n\u002Fsi:extract \"Fix for Docker builds failing on Apple Silicon with platform mismatch\"\n```\n\nCreates `docker-m1-fixes\u002FSKILL.md` with:\n- The platform mismatch error message\n- Three solutions (build flag, Dockerfile, docker-compose)\n- Trade-offs table\n- Performance note about Rosetta 2 emulation\n\n### Extracting a workflow pattern\n\n```\n\u002Fsi:extract \"Always regenerate TypeScript API client after modifying OpenAPI spec\"\n```\n\nCreates `api-client-regen\u002FSKILL.md` with:\n- Why manual regen is needed\n- The exact command sequence\n- CI integration snippet\n- Common failure modes\n\n## Tips\n\n- Extract patterns that would save time in a *different* project\n- Keep skills focused — one problem per skill\n- Include the error messages people would search for\n- Test the skill by reading it without the original context — does it make sense?\n",{"name":5,"description":7},"claude\u002Fregistry-repo-7lRiv","44e1a5b2d387b250bcd0794f7eb5e1228223d1e2","engineering-team\u002Fself-improving-agent\u002Fskills\u002Fextract","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills","https:\u002F\u002Fgithub.com\u002FMabbit143","I’m edgy and fun, probably too serious, but I love an adventure.","2026-09-22 07:56:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Mabbit143\u002FClaude-SKills --skill extract",{"tool":37,"command":38},"bunx","bunx skills add Mabbit143\u002FClaude-SKills --skill extract",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Mabbit143\u002FClaude-SKills --skill extract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Fextract\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7D99ZA4F916M5CM3K2EQFE8","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7D99ND4B38EG1BYQX722F5D","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7D999VS936SV9TX940A98AQ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D98XBECS6368GEJNG8C1Z1","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D98N2R7CA7RM00PNP4VV6C","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D98B1SCTS4RAWZFCF9QJ5M","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]