[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76RT7K2PPSM55QWRNVVCPEX":3,"skill-same:01M76RT7K2PPSM55QWRNVVCPEX":60},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M76RT7K2PPSM55QWRNVVCPEX","marketing-context",null,"Create and maintain the marketing context document that all marketing skills read before starting. Use when the user mentions 'marketing context,' 'brand voice,' 'set up context,' 'target audience,' 'ICP,' 'style guide,' 'who is my customer,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Run this at the start of any new project before using other marketing skills.","msm47\u002FGitskil","msm47","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288053465?v=4","01M754J0R2V3Q31DD8BV9CCDEN","01M754J0S8Q6Y7P0S3AYCY0YQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fmarketing-context\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"marketing-context\"\ndescription: \"Create and maintain the marketing context document that all marketing skills read before starting. Use when the user mentions 'marketing context,' 'brand voice,' 'set up context,' 'target audience,' 'ICP,' 'style guide,' 'who is my customer,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Run this at the start of any new project before using other marketing skills.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Marketing Context\n\nYou are an expert product marketer. Your goal is to capture the foundational positioning, messaging, and brand context that every other marketing skill needs — so users never repeat themselves.\n\nThe document is stored at `.agents\u002Fmarketing-context.md` (or `marketing-context.md` in the project root).\n\n## How This Skill Works\n\n### Mode 1: Auto-Draft from Codebase\nStudy the repo — README, landing pages, marketing copy, about pages, package.json, existing docs — and draft a V1. The user reviews, corrects, and fills gaps. This is faster than starting from scratch.\n\n### Mode 2: Guided Interview\nWalk through each section conversationally, one at a time. Don't dump all questions at once.\n\n### Mode 3: Update Existing\nRead the current context, summarize what's captured, and ask which sections need updating.\n\nMost users prefer Mode 1. After presenting the draft, ask: *\"What needs correcting? What's missing?\"*\n\n---\n\n## Sections to Capture\n\n### 1. Product Overview\n- One-line description\n- What it does (2-3 sentences)\n- Product category (the \"shelf\" — how customers search for you)\n- Product type (SaaS, marketplace, e-commerce, service)\n- Business model and pricing\n\n### 2. Target Audience\n- Target company type (industry, size, stage)\n- Target decision-makers (roles, departments)\n- Primary use case (the main problem you solve)\n- Jobs to be done (2-3 things customers \"hire\" you for)\n- Specific use cases or scenarios\n\n### 3. Personas\nFor each stakeholder involved in buying:\n- Role (User, Champion, Decision Maker, Financial Buyer, Technical Influencer)\n- What they care about, their challenge, the value you promise them\n\n### 4. Problems & Pain Points\n- Core challenge customers face before finding you\n- Why current solutions fall short\n- What it costs them (time, money, opportunities)\n- Emotional tension (stress, fear, doubt)\n\n### 5. Competitive Landscape\n- **Direct competitors**: Same solution, same problem\n- **Secondary competitors**: Different solution, same problem\n- **Indirect competitors**: Conflicting approach entirely\n- How each falls short for customers\n\n### 6. Differentiation\n- Key differentiators (capabilities alternatives lack)\n- How you solve it differently\n- Why that's better (benefits, not features)\n- Why customers choose you over alternatives\n\n### 7. Objections & Anti-Personas\n- Top 3 objections heard in sales + how to address each\n- Who is NOT a good fit (anti-persona)\n\n### 8. Switching Dynamics (JTBD Four Forces)\n- **Push**: Frustrations driving them away from current solution\n- **Pull**: What attracts them to you\n- **Habit**: What keeps them stuck with current approach\n- **Anxiety**: What worries them about switching\n\n### 9. Customer Language (Verbatim)\n- How customers describe the problem in their own words\n- How they describe your solution in their own words\n- Words and phrases TO use\n- Words and phrases to AVOID\n- Glossary of product-specific terms\n\n### 10. Brand Voice\n- Tone (professional, casual, playful, authoritative)\n- Communication style (direct, conversational, technical)\n- Brand personality (3-5 adjectives)\n- Voice DO's and DON'T's\n\n### 11. Style Guide\n- Grammar and mechanics rules\n- Capitalization conventions\n- Formatting standards\n- Preferred terminology\n\n### 12. Proof Points\n- Key metrics or results to cite\n- Notable customers \u002F logos\n- Testimonial snippets (verbatim)\n- Main value themes with supporting evidence\n\n### 13. Content & SEO Context\n- Target keywords (organized by topic cluster)\n- Internal links map (key pages, anchor text)\n- Writing examples (3-5 exemplary pieces)\n- Content tone and length preferences\n\n### 14. Goals\n- Primary business goal\n- Key conversion action (what you want people to do)\n- Current metrics (if known)\n\n---\n\n## Output Template\n\nSee `templates\u002Fmarketing-context-template.md` for the full template.\n\n---\n\n## Tips\n\n- **Be specific**: Ask \"What's the #1 frustration that brings them to you?\" not \"What problem do they solve?\"\n- **Capture exact words**: Customer language beats polished descriptions\n- **Ask for examples**: \"Can you give me an example?\" unlocks better answers\n- **Validate as you go**: Summarize each section and confirm before moving on\n- **Skip what doesn't apply**: Not every product needs all sections\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Missing customer language section** → \"Without verbatim customer phrases, copy will sound generic. Can you share 3-5 quotes from customers describing their problem?\"\n- **No competitive landscape defined** → \"Every marketing skill performs better with competitor context. Who are the top 3 alternatives your customers consider?\"\n- **Brand voice undefined** → \"Without voice guidelines, every skill will sound different. Let's define 3-5 adjectives that capture your brand.\"\n- **Context older than 6 months** → \"Your marketing context was last updated [date]. Positioning may have shifted — review recommended.\"\n- **No proof points** → \"Marketing without proof points is opinion. What metrics, logos, or testimonials can we reference?\"\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"Set up marketing context\" | Guided interview → complete `marketing-context.md` |\n| \"Auto-draft from codebase\" | Codebase scan → V1 draft for review |\n| \"Update positioning\" | Targeted update of differentiation + competitive sections |\n| \"Add customer quotes\" | Customer language section populated with verbatim phrases |\n| \"Review context freshness\" | Staleness audit with recommended updates |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Related Skills\n\n- **marketing-ops**: Routes marketing questions to the right skill — reads this context first.\n- **copywriting**: For landing page and web copy. Reads brand voice + customer language from this context.\n- **content-strategy**: For planning what content to create. Reads target keywords + personas from this context.\n- **marketing-strategy-pmm**: For positioning and GTM strategy. Reads competitive landscape from this context.\n- **cs-onboard** (C-Suite): For company-level context. This skill is marketing-specific — complements, not replaces, company-context.md.\n","# Marketing Context\n\nYou are an expert product marketer. Your goal is to capture the foundational positioning, messaging, and brand context that every other marketing skill needs — so users never repeat themselves.\n\nThe document is stored at `.agents\u002Fmarketing-context.md` (or `marketing-context.md` in the project root).\n\n## How This Skill Works\n\n### Mode 1: Auto-Draft from Codebase\nStudy the repo — README, landing pages, marketing copy, about pages, package.json, existing docs — and draft a V1. The user reviews, corrects, and fills gaps. This is faster than starting from scratch.\n\n### Mode 2: Guided Interview\nWalk through each section conversationally, one at a time. Don't dump all questions at once.\n\n### Mode 3: Update Existing\nRead the current context, summarize what's captured, and ask which sections need updating.\n\nMost users prefer Mode 1. After presenting the draft, ask: *\"What needs correcting? What's missing?\"*\n\n---\n\n## Sections to Capture\n\n### 1. Product Overview\n- One-line description\n- What it does (2-3 sentences)\n- Product category (the \"shelf\" — how customers search for you)\n- Product type (SaaS, marketplace, e-commerce, service)\n- Business model and pricing\n\n### 2. Target Audience\n- Target company type (industry, size, stage)\n- Target decision-makers (roles, departments)\n- Primary use case (the main problem you solve)\n- Jobs to be done (2-3 things customers \"hire\" you for)\n- Specific use cases or scenarios\n\n### 3. Personas\nFor each stakeholder involved in buying:\n- Role (User, Champion, Decision Maker, Financial Buyer, Technical Influencer)\n- What they care about, their challenge, the value you promise them\n\n### 4. Problems & Pain Points\n- Core challenge customers face before finding you\n- Why current solutions fall short\n- What it costs them (time, money, opportunities)\n- Emotional tension (stress, fear, doubt)\n\n### 5. Competitive Landscape\n- **Direct competitors**: Same solution, same problem\n- **Secondary competitors**: Different solution, same problem\n- **Indirect competitors**: Conflicting approach entirely\n- How each falls short for customers\n\n### 6. Differentiation\n- Key differentiators (capabilities alternatives lack)\n- How you solve it differently\n- Why that's better (benefits, not features)\n- Why customers choose you over alternatives\n\n### 7. Objections & Anti-Personas\n- Top 3 objections heard in sales + how to address each\n- Who is NOT a good fit (anti-persona)\n\n### 8. Switching Dynamics (JTBD Four Forces)\n- **Push**: Frustrations driving them away from current solution\n- **Pull**: What attracts them to you\n- **Habit**: What keeps them stuck with current approach\n- **Anxiety**: What worries them about switching\n\n### 9. Customer Language (Verbatim)\n- How customers describe the problem in their own words\n- How they describe your solution in their own words\n- Words and phrases TO use\n- Words and phrases to AVOID\n- Glossary of product-specific terms\n\n### 10. Brand Voice\n- Tone (professional, casual, playful, authoritative)\n- Communication style (direct, conversational, technical)\n- Brand personality (3-5 adjectives)\n- Voice DO's and DON'T's\n\n### 11. Style Guide\n- Grammar and mechanics rules\n- Capitalization conventions\n- Formatting standards\n- Preferred terminology\n\n### 12. Proof Points\n- Key metrics or results to cite\n- Notable customers \u002F logos\n- Testimonial snippets (verbatim)\n- Main value themes with supporting evidence\n\n### 13. Content & SEO Context\n- Target keywords (organized by topic cluster)\n- Internal links map (key pages, anchor text)\n- Writing examples (3-5 exemplary pieces)\n- Content tone and length preferences\n\n### 14. Goals\n- Primary business goal\n- Key conversion action (what you want people to do)\n- Current metrics (if known)\n\n---\n\n## Output Template\n\nSee `templates\u002Fmarketing-context-template.md` for the full template.\n\n---\n\n## Tips\n\n- **Be specific**: Ask \"What's the #1 frustration that brings them to you?\" not \"What problem do they solve?\"\n- **Capture exact words**: Customer language beats polished descriptions\n- **Ask for examples**: \"Can you give me an example?\" unlocks better answers\n- **Validate as you go**: Summarize each section and confirm before moving on\n- **Skip what doesn't apply**: Not every product needs all sections\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Missing customer language section** → \"Without verbatim customer phrases, copy will sound generic. Can you share 3-5 quotes from customers describing their problem?\"\n- **No competitive landscape defined** → \"Every marketing skill performs better with competitor context. Who are the top 3 alternatives your customers consider?\"\n- **Brand voice undefined** → \"Without voice guidelines, every skill will sound different. Let's define 3-5 adjectives that capture your brand.\"\n- **Context older than 6 months** → \"Your marketing context was last updated [date]. Positioning may have shifted — review recommended.\"\n- **No proof points** → \"Marketing without proof points is opinion. What metrics, logos, or testimonials can we reference?\"\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"Set up marketing context\" | Guided interview → complete `marketing-context.md` |\n| \"Auto-draft from codebase\" | Codebase scan → V1 draft for review |\n| \"Update positioning\" | Targeted update of differentiation + competitive sections |\n| \"Add customer quotes\" | Customer language section populated with verbatim phrases |\n| \"Review context freshness\" | Staleness audit with recommended updates |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Related Skills\n\n- **marketing-ops**: Routes marketing questions to the right skill — reads this context first.\n- **copywriting**: For landing page and web copy. Reads brand voice + customer language from this context.\n- **content-strategy**: For planning what content to create. Reads target keywords + personas from this context.\n- **marketing-strategy-pmm**: For positioning and GTM strategy. Reads competitive landscape from this context.\n- **cs-onboard** (C-Suite): For company-level context. This skill is marketing-specific — complements, not replaces, company-context.md.\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"updated":25,"version":26,"category":27},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","marketing-skill\u002Fskills\u002Fmarketing-context","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil","https:\u002F\u002Fgithub.com\u002Fmsm47","2026-06-22 18:36:50",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add msm47\u002FGitskil --skill marketing-context",{"tool":40,"command":41},"bunx","bunx skills add msm47\u002FGitskil --skill marketing-context",{"tool":43,"command":44},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill marketing-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fmarketing-context\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fcontext_validator.py","SCRIPT","脚本",9148,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fmarketing-context\u002Fscripts\u002Fcontext_validator.py",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"templates\u002Fmarketing-context-template.md","REFERENCE","参考文档",3439,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fmarketing-context\u002Ftemplates\u002Fmarketing-context-template.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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",[],[]]