[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M755WCC0RG6P8Y8CBY2J4MMR":3,"skill-same:01M755WCC0RG6P8Y8CBY2J4MMR":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M755WCC0RG6P8Y8CBY2J4MMR","code-tour",null,"Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.","msm47\u002FGitskil","msm47","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288053465?v=4","01M754J0R2V3Q31DD8BV9CCDEN","01M754J0S8Q6Y7P0S3AYCY0YQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fcode-tour\u002Fskills\u002Fcode-tour\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"code-tour\"\ndescription: \"Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.\"\n---\n\n# Code Tour\n\nCreate **CodeTour** files — persona-targeted, step-by-step walkthroughs of a codebase that link directly to files and line numbers. CodeTour files live in `.tours\u002F` and work with the [VS Code CodeTour extension](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour).\n\n## Overview\n\nA great tour is a **narrative** — a story told to a specific person about what matters, why it matters, and what to do next. Only create `.tour` JSON files. Never modify source code.\n\n## When to Use This Skill\n\n- User asks to create a code tour, onboarding tour, or architecture walkthrough\n- User says \"tour for this PR\", \"explain how X works\", \"vibe check\", \"RCA tour\"\n- User wants a contributor guide, security review, or bug investigation walkthrough\n- Any request for a structured walkthrough with file\u002Fline anchors\n\n## Core Workflow\n\n### 1. Discover the repo\n\nBefore asking anything, explore the codebase:\n\nIn parallel: list root directory, read README, check config files.\nThen: identify language(s), framework(s), project purpose. Map folder structure 1-2 levels deep. Find entry points — every path in the tour must be real.\n\nIf the repo has fewer than 5 source files, create a quick-depth tour regardless of persona — there's not enough to warrant a deep one.\n\n### 2. Infer the intent\n\nOne message should be enough. Infer persona, depth, and focus silently.\n\n| User says | Persona | Depth |\n|-----------|---------|-------|\n| \"tour for this PR\" | pr-reviewer | standard |\n| \"why did X break\" \u002F \"RCA\" | rca-investigator | standard |\n| \"onboarding\" \u002F \"new joiner\" | new-joiner | standard |\n| \"quick tour\" \u002F \"vibe check\" | vibecoder | quick |\n| \"architecture\" | architect | deep |\n| \"security\" \u002F \"auth review\" | security-reviewer | standard |\n| (no qualifier) | new-joiner | standard |\n\nWhen intent is ambiguous, default to **new-joiner** persona at **standard** depth — it's the most generally useful.\n\n### 3. Read actual files\n\n**Every file path and line number must be verified.** A tour pointing to the wrong line is worse than no tour.\n\n### 4. Write the tour\n\nSave to `.tours\u002F\u003Cpersona>-\u003Cfocus>.tour`.\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"Descriptive Title — Persona \u002F Goal\",\n  \"description\": \"Who this is for and what they'll understand after.\",\n  \"ref\": \"\u003Ccurrent-branch-or-commit>\",\n  \"steps\": []\n}\n```\n\n### Step types\n\n| Type | When to use | Example |\n|------|-------------|---------|\n| **Content** | Intro\u002Fclosing only (max 2) | `{ \"title\": \"Welcome\", \"description\": \"...\" }` |\n| **Directory** | Orient to a module | `{ \"directory\": \"src\u002Fservices\", \"title\": \"...\" }` |\n| **File + line** | The workhorse | `{ \"file\": \"src\u002Fauth.ts\", \"line\": 42, \"title\": \"...\" }` |\n| **Selection** | Highlight a code block | `{ \"file\": \"...\", \"selection\": {...}, \"title\": \"...\" }` |\n| **Pattern** | Regex match (volatile files) | `{ \"file\": \"...\", \"pattern\": \"class App\", \"title\": \"...\" }` |\n| **URI** | Link to PR, issue, doc | `{ \"uri\": \"https:\u002F\u002F...\", \"title\": \"...\" }` |\n\n### Step count\n\n| Depth | Steps | Use for |\n|-------|-------|---------|\n| Quick | 5-8 | Vibecoder, fast exploration |\n| Standard | 9-13 | Most personas |\n| Deep | 14-18 | Architect, RCA |\n\n### Writing descriptions — SMIG formula\n\n- **S — Situation**: What is the reader looking at?\n- **M — Mechanism**: How does this code work?\n- **I — Implication**: Why does this matter for this persona?\n- **G — Gotcha**: What would a smart person get wrong?\n\n### 5. Validate\n\n- [ ] Every `file` path relative to repo root (no leading `\u002F` or `.\u002F`)\n- [ ] Every `file` confirmed to exist\n- [ ] Every `line` verified by reading the file\n- [ ] First step has `file` or `directory` anchor\n- [ ] At most 2 content-only steps\n- [ ] `nextTour` matches another tour's `title` exactly if set\n\n## Personas\n\n| Persona | Goal | Must cover |\n|---------|------|------------|\n| **Vibecoder** | Get the vibe fast | Entry point, main modules. Max 8 steps. |\n| **New joiner** | Structured ramp-up | Directories, setup, business context |\n| **Bug fixer** | Root cause fast | Trigger -> fault points -> tests |\n| **RCA investigator** | Why did it fail | Causality chain, observability anchors |\n| **Feature explainer** | End-to-end | UI -> API -> backend -> storage |\n| **PR reviewer** | Review correctly | Change story, invariants, risky areas |\n| **Architect** | Shape and rationale | Boundaries, tradeoffs, extension points |\n| **Security reviewer** | Trust boundaries | Auth flow, validation, secret handling |\n| **Refactorer** | Safe restructuring | Seams, hidden deps, extraction order |\n| **External contributor** | Contribute safely | Safe areas, conventions, landmines |\n\n## Narrative Arc\n\n1. **Orientation** — `file` or `directory` step (never content-only first step — blank in VS Code)\n2. **High-level map** — 1-3 directory steps showing major modules\n3. **Core path** — file\u002Fline steps, the heart of the tour\n4. **Closing** — what the reader can now do, suggested follow-ups\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n|---|---|\n| **File listing** — \"this file contains the models\" | Tell a story. Each step depends on the previous. |\n| **Generic descriptions** | Name the specific pattern unique to this codebase. |\n| **Line number guessing** | Never write a line you didn't verify by reading. |\n| **Too many steps** for quick depth | Actually cut steps. |\n| **Hallucinated files** | If it doesn't exist, skip the step. |\n| **Recap closing** — \"we covered X, Y, Z\" | Tell the reader what they can now *do*. |\n| **Content-only first step** | Anchor step 1 to a file or directory. |\n\n## Cross-References\n\n- Related: `engineering\u002Fcodebase-onboarding` — for broader onboarding beyond tours\n- Related: `engineering\u002Fpr-review-expert` — for automated PR review workflows\n- CodeTour extension: [microsoft\u002Fcodetour](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour)\n- Real-world tours: [coder\u002Fcode-server](https:\u002F\u002Fgithub.com\u002Fcoder\u002Fcode-server\u002Fblob\u002Fmain\u002F.tours\u002Fcontributing.tour)\n","# Code Tour\n\nCreate **CodeTour** files — persona-targeted, step-by-step walkthroughs of a codebase that link directly to files and line numbers. CodeTour files live in `.tours\u002F` and work with the [VS Code CodeTour extension](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour).\n\n## Overview\n\nA great tour is a **narrative** — a story told to a specific person about what matters, why it matters, and what to do next. Only create `.tour` JSON files. Never modify source code.\n\n## When to Use This Skill\n\n- User asks to create a code tour, onboarding tour, or architecture walkthrough\n- User says \"tour for this PR\", \"explain how X works\", \"vibe check\", \"RCA tour\"\n- User wants a contributor guide, security review, or bug investigation walkthrough\n- Any request for a structured walkthrough with file\u002Fline anchors\n\n## Core Workflow\n\n### 1. Discover the repo\n\nBefore asking anything, explore the codebase:\n\nIn parallel: list root directory, read README, check config files.\nThen: identify language(s), framework(s), project purpose. Map folder structure 1-2 levels deep. Find entry points — every path in the tour must be real.\n\nIf the repo has fewer than 5 source files, create a quick-depth tour regardless of persona — there's not enough to warrant a deep one.\n\n### 2. Infer the intent\n\nOne message should be enough. Infer persona, depth, and focus silently.\n\n| User says | Persona | Depth |\n|-----------|---------|-------|\n| \"tour for this PR\" | pr-reviewer | standard |\n| \"why did X break\" \u002F \"RCA\" | rca-investigator | standard |\n| \"onboarding\" \u002F \"new joiner\" | new-joiner | standard |\n| \"quick tour\" \u002F \"vibe check\" | vibecoder | quick |\n| \"architecture\" | architect | deep |\n| \"security\" \u002F \"auth review\" | security-reviewer | standard |\n| (no qualifier) | new-joiner | standard |\n\nWhen intent is ambiguous, default to **new-joiner** persona at **standard** depth — it's the most generally useful.\n\n### 3. Read actual files\n\n**Every file path and line number must be verified.** A tour pointing to the wrong line is worse than no tour.\n\n### 4. Write the tour\n\nSave to `.tours\u002F\u003Cpersona>-\u003Cfocus>.tour`.\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"Descriptive Title — Persona \u002F Goal\",\n  \"description\": \"Who this is for and what they'll understand after.\",\n  \"ref\": \"\u003Ccurrent-branch-or-commit>\",\n  \"steps\": []\n}\n```\n\n### Step types\n\n| Type | When to use | Example |\n|------|-------------|---------|\n| **Content** | Intro\u002Fclosing only (max 2) | `{ \"title\": \"Welcome\", \"description\": \"...\" }` |\n| **Directory** | Orient to a module | `{ \"directory\": \"src\u002Fservices\", \"title\": \"...\" }` |\n| **File + line** | The workhorse | `{ \"file\": \"src\u002Fauth.ts\", \"line\": 42, \"title\": \"...\" }` |\n| **Selection** | Highlight a code block | `{ \"file\": \"...\", \"selection\": {...}, \"title\": \"...\" }` |\n| **Pattern** | Regex match (volatile files) | `{ \"file\": \"...\", \"pattern\": \"class App\", \"title\": \"...\" }` |\n| **URI** | Link to PR, issue, doc | `{ \"uri\": \"https:\u002F\u002F...\", \"title\": \"...\" }` |\n\n### Step count\n\n| Depth | Steps | Use for |\n|-------|-------|---------|\n| Quick | 5-8 | Vibecoder, fast exploration |\n| Standard | 9-13 | Most personas |\n| Deep | 14-18 | Architect, RCA |\n\n### Writing descriptions — SMIG formula\n\n- **S — Situation**: What is the reader looking at?\n- **M — Mechanism**: How does this code work?\n- **I — Implication**: Why does this matter for this persona?\n- **G — Gotcha**: What would a smart person get wrong?\n\n### 5. Validate\n\n- [ ] Every `file` path relative to repo root (no leading `\u002F` or `.\u002F`)\n- [ ] Every `file` confirmed to exist\n- [ ] Every `line` verified by reading the file\n- [ ] First step has `file` or `directory` anchor\n- [ ] At most 2 content-only steps\n- [ ] `nextTour` matches another tour's `title` exactly if set\n\n## Personas\n\n| Persona | Goal | Must cover |\n|---------|------|------------|\n| **Vibecoder** | Get the vibe fast | Entry point, main modules. Max 8 steps. |\n| **New joiner** | Structured ramp-up | Directories, setup, business context |\n| **Bug fixer** | Root cause fast | Trigger -> fault points -> tests |\n| **RCA investigator** | Why did it fail | Causality chain, observability anchors |\n| **Feature explainer** | End-to-end | UI -> API -> backend -> storage |\n| **PR reviewer** | Review correctly | Change story, invariants, risky areas |\n| **Architect** | Shape and rationale | Boundaries, tradeoffs, extension points |\n| **Security reviewer** | Trust boundaries | Auth flow, validation, secret handling |\n| **Refactorer** | Safe restructuring | Seams, hidden deps, extraction order |\n| **External contributor** | Contribute safely | Safe areas, conventions, landmines |\n\n## Narrative Arc\n\n1. **Orientation** — `file` or `directory` step (never content-only first step — blank in VS Code)\n2. **High-level map** — 1-3 directory steps showing major modules\n3. **Core path** — file\u002Fline steps, the heart of the tour\n4. **Closing** — what the reader can now do, suggested follow-ups\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n|---|---|\n| **File listing** — \"this file contains the models\" | Tell a story. Each step depends on the previous. |\n| **Generic descriptions** | Name the specific pattern unique to this codebase. |\n| **Line number guessing** | Never write a line you didn't verify by reading. |\n| **Too many steps** for quick depth | Actually cut steps. |\n| **Hallucinated files** | If it doesn't exist, skip the step. |\n| **Recap closing** — \"we covered X, Y, Z\" | Tell the reader what they can now *do*. |\n| **Content-only first step** | Anchor step 1 to a file or directory. |\n\n## Cross-References\n\n- Related: `engineering\u002Fcodebase-onboarding` — for broader onboarding beyond tours\n- Related: `engineering\u002Fpr-review-expert` — for automated PR review workflows\n- CodeTour extension: [microsoft\u002Fcodetour](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour)\n- Real-world tours: [coder\u002Fcode-server](https:\u002F\u002Fgithub.com\u002Fcoder\u002Fcode-server\u002Fblob\u002Fmain\u002F.tours\u002Fcontributing.tour)\n",{"name":5,"description":7},"main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","engineering\u002Fcode-tour\u002Fskills\u002Fcode-tour","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil","https:\u002F\u002Fgithub.com\u002Fmsm47","2026-06-22 18:36:50",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add msm47\u002FGitskil --skill code-tour",{"tool":35,"command":36},"bunx","bunx skills add msm47\u002FGitskil --skill code-tour",{"tool":38,"command":39},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill code-tour","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fcode-tour\u002Fskills\u002Fcode-tour\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M76S8VB9Q65XVZXC99QVF20M","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\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M76S8K8X17M3CV7RENS6KA32","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\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M76S8AZCNS7Q5M4G1SBQ8HDV","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\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M76S7YVS0NHD51AFTZM5965R","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\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M76S7MQDZR49Y3DRXF394R2F","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\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M76S78K1ZJ092YYRKX0KBTYJ","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\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]