[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7852S1T6MEB5DVJC03KX72K":3,"skill-same:01M7852S1T6MEB5DVJC03KX72K":50},{"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":6,"updatedAt":29,"install":30,"resources":43},"01M7852S1T6MEB5DVJC03KX72K","deep-research",null,"Run a disciplined, multi-source research investigation for a high-stakes question or decision — fan-out web search across many channels, parallel sub-agents, source triangulation (each claim backed by ≥3 independent sources), an adversarial review pass, and every source saved to its own file with verbatim quotes for reuse. Use when a low-quality answer is expensive: strategy work, comparing N products\u002Fmethods\u002Fmarkets, validating a hypothesis with external data, or mapping how a field works. NOT for quick fact-checks (answer directly), structured 12-dimension competitor scoring (use competitive-teardown), or fast topic overviews where the decision risk is low (use the research router instead).","motivatedc-creator\u002FSaafy","motivatedc-creator","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250662783?v=4","01M782H2D8C7XJGXMJC3YHQAWK","Happy Haris","01M782H2ERMBYEM1NSPPPC06S0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fdeep-research\u002Fskills\u002Fdeep-research\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"deep-research\"\ndescription: \"Run a disciplined, multi-source research investigation for a high-stakes question or decision — fan-out web search across many channels, parallel sub-agents, source triangulation (each claim backed by ≥3 independent sources), an adversarial review pass, and every source saved to its own file with verbatim quotes for reuse. Use when a low-quality answer is expensive: strategy work, comparing N products\u002Fmethods\u002Fmarkets, validating a hypothesis with external data, or mapping how a field works. NOT for quick fact-checks (answer directly), structured 12-dimension competitor scoring (use competitive-teardown), or fast topic overviews where the decision risk is low (use the research router instead).\"\n---\n\n# Deep Research — Disciplined Meta-Research\n\nTurn \"research this topic\" into an auditable, reusable investigation instead of a one-shot wall of text. The output is a folder you can return to in a month: every claim traces to a specific source file, the plan documents *why* each choice was made, and a refresh protocol lets you update it later without re-running everything.\n\n**This is the heavy, methodical end of research.** It is not a fast overview — it is the workflow you reach for when getting the answer *wrong* costs more than the tokens spent getting it right.\n\n## How it differs from a quick research router\n\nA router-style research skill (keyword-classify → delegate → short sequential search → markdown brief) is optimal when you need an answer fast and the decision risk is low. `deep-research` is the opposite trade: it pays for rigor. Use it when the answer feeds a strategy, an irreversible decision, a published artifact, or a hypothesis you need to actually test — situations where a shallow fallback would be a liability.\n\nConcretely, `deep-research` adds what a fast overview does not: falsifiable hypotheses up front, parallel sub-agent fan-out across many channels, triangulation with explicit source-type diversity, a mandatory adversarial pass, per-source files with verbatim quotes, and a `refresh_targets.md` for delta-updates later.\n\n## The pipeline (9 phases)\n\nDepth scales with the task — `shallow` runs the core phases inline; `medium`\u002F`deep` add capability discovery, verification, and refresh targets.\n\n| # | Phase | What it does |\n|---|-------|--------------|\n| 1 | **Reframe** | Rewrite the question, fix the underlying decision, state 2–4 *falsifiable* hypotheses |\n| 2 | **Genre & blocks** | Pick the report genre (qa \u002F explainer \u002F decision \u002F landscape \u002F validation \u002F custom) and its building blocks |\n| 3 | **Plan** | Write `plan.md`: scope, structure, sourcing strategy, opposition queries, risk register, stop-criteria |\n| 3.5 | **Capability discovery** | Audit available API keys\u002Fchannels in the environment; map subtopics to sources; fall back to HTML where needed |\n| 4 | **Search** (loop) | Dispatch sources → launch sub-agents in parallel → fetch & dedup → save each to `sources\u002FNN.md`; re-evaluate between rounds |\n| 5 | **Score & triangulate** | Rate every source on Credibility \u002F Recency \u002F Bias; require ≥3 independent, differently-typed sources per thesis |\n| 6 | **Synthesize + adversarial** | Assemble the report from blocks, run 4 self-critique questions, add steel-manned counter-arguments |\n| 6.5 | **Verify** | Lightweight citation check before closing |\n| 7 | **Refresh targets** | Extract entities \u002F numbers \u002F hypotheses into `refresh_targets.md` — the entry point for future updates |\n\n## Core mechanisms\n\nThese are what separate a documented investigation from a confident guess:\n\n- **Triangulation.** Every thesis must be backed by ≥3 independent sources of *different types* (primary \u002F academic \u002F industry \u002F discussion). A claim with fewer is flagged \"insufficient evidence,\" not stated as fact.\n- **Source-grounding.** Each source becomes its own `sources\u002FNN_slug.md` with metadata, verbatim quotes, and scores. No dangling claim — every assertion links back to a specific file. An empty fetch produces an empty claim, never a fabricated citation.\n- **Adversarial pass.** Phase 6 always runs the strongest available reasoning: 4 self-critique questions plus an active search for counter-arguments and disconfirming evidence.\n- **Falsifiable hypotheses.** Phase 1 commits to 2–4 hypotheses; Phases 5–6 explicitly confirm or refute each against the evidence, or mark it under-determined.\n- **Parallel sub-agents.** Phase 4 launches search sub-agents concurrently (cheap models for broad web sweeps, stronger ones for reasoning-heavy subtopics) — never one-at-a-time.\n- **Refresh protocol.** Phase 7 emits `refresh_targets.md`; an `update \u003Cslug>` run produces a delta (new entrants, entity changes, refreshed numbers, adversarial triggers) instead of replaying the whole investigation.\n- **Atomic findings.** Reusable theses in `findings\u002FFN.md` plus a `sources.csv` index — research compounds across questions instead of starting from zero each time.\n\n## Output structure\n\n```\n\u003Croot>\u002F\u003Cslug>\u002F\n├── plan.md                  # scope, sourcing strategy, risk register, changelog\n├── sources.csv              # index of every source with scores\n├── sources\u002F\n│   ├── 01_\u003Cslug>.md         # one file = one source (metadata + verbatim quotes)\n│   └── ...\n├── findings\u002F                # atomic, reusable theses (larger investigations)\n│   └── F1_\u003Cshort>.md\n├── refresh_targets.md       # what to watch on update (medium\u002Fdeep)\n├── diffs\u002F\n│   └── YYYY-MM-DD_delta.md   # delta from an `update \u003Cslug>` run\n└── YYYY-MM-DD_\u003Cgenre>.md     # final report\n```\n\n## When to use\n\n- A low-quality answer is expensive: strategy, business plan, report, or article groundwork.\n- Comparing N institutions, products, methodologies, or markets and you need defensible reasoning.\n- Validating a hypothesis or a decision against external data.\n- Meta-research: \"understand how X works,\" \"map the landscape of Y,\" answering a connected series of questions.\n\n## Anti-Patterns\n\n- **Don't skip the existing-work check.** Before searching, see whether the answer is already in the project or in a prior research folder — you risk re-researching something you already have.\n- **Don't skip reframing**, even when the request \"seems clear.\" The decision behind the question usually changes the search.\n- **Don't output to chat only.** Always persist sources and the report to files — the reuse value is in the folder, not the transcript.\n- **Don't fabricate citations.** If a fetch returns nothing, the claim is empty — never invent a plausible URL. Bind every claim to a saved verbatim quote.\n- **Don't build conclusions on a thin corpus.** Too few sources, or sources that all share one type, means triangulation hasn't happened — say so rather than overstating confidence.\n- **Don't skip the adversarial pass** on medium\u002Fdeep investigations. Confirmation-only research is the failure mode this skill exists to prevent.\n- **Don't run sub-agents sequentially.** Fan-out in parallel; serial search wastes the wall-clock advantage.\n- **Don't collapse `sources\u002F` into one file.** Per-source files are what make findings searchable and reusable across investigations.\n- **Don't pick the heaviest model for everything.** Match model to subtask — cheap for broad sweeps, strong for synthesis and the adversarial pass.\n\n## Cross-References\n\n- **research router** — for fast topic overviews where decision risk is low; `deep-research` is the heavyweight alternative when rigor matters more than speed.\n- **competitive-teardown** — for comparing N competitors on a structured 12-dimension matrix.\n- **litreview \u002F dossier \u002F patent** — domain specialists when the investigation is narrowly academic, person\u002Fcompany-focused, or patent-focused.\n","# Deep Research — Disciplined Meta-Research\n\nTurn \"research this topic\" into an auditable, reusable investigation instead of a one-shot wall of text. The output is a folder you can return to in a month: every claim traces to a specific source file, the plan documents *why* each choice was made, and a refresh protocol lets you update it later without re-running everything.\n\n**This is the heavy, methodical end of research.** It is not a fast overview — it is the workflow you reach for when getting the answer *wrong* costs more than the tokens spent getting it right.\n\n## How it differs from a quick research router\n\nA router-style research skill (keyword-classify → delegate → short sequential search → markdown brief) is optimal when you need an answer fast and the decision risk is low. `deep-research` is the opposite trade: it pays for rigor. Use it when the answer feeds a strategy, an irreversible decision, a published artifact, or a hypothesis you need to actually test — situations where a shallow fallback would be a liability.\n\nConcretely, `deep-research` adds what a fast overview does not: falsifiable hypotheses up front, parallel sub-agent fan-out across many channels, triangulation with explicit source-type diversity, a mandatory adversarial pass, per-source files with verbatim quotes, and a `refresh_targets.md` for delta-updates later.\n\n## The pipeline (9 phases)\n\nDepth scales with the task — `shallow` runs the core phases inline; `medium`\u002F`deep` add capability discovery, verification, and refresh targets.\n\n| # | Phase | What it does |\n|---|-------|--------------|\n| 1 | **Reframe** | Rewrite the question, fix the underlying decision, state 2–4 *falsifiable* hypotheses |\n| 2 | **Genre & blocks** | Pick the report genre (qa \u002F explainer \u002F decision \u002F landscape \u002F validation \u002F custom) and its building blocks |\n| 3 | **Plan** | Write `plan.md`: scope, structure, sourcing strategy, opposition queries, risk register, stop-criteria |\n| 3.5 | **Capability discovery** | Audit available API keys\u002Fchannels in the environment; map subtopics to sources; fall back to HTML where needed |\n| 4 | **Search** (loop) | Dispatch sources → launch sub-agents in parallel → fetch & dedup → save each to `sources\u002FNN.md`; re-evaluate between rounds |\n| 5 | **Score & triangulate** | Rate every source on Credibility \u002F Recency \u002F Bias; require ≥3 independent, differently-typed sources per thesis |\n| 6 | **Synthesize + adversarial** | Assemble the report from blocks, run 4 self-critique questions, add steel-manned counter-arguments |\n| 6.5 | **Verify** | Lightweight citation check before closing |\n| 7 | **Refresh targets** | Extract entities \u002F numbers \u002F hypotheses into `refresh_targets.md` — the entry point for future updates |\n\n## Core mechanisms\n\nThese are what separate a documented investigation from a confident guess:\n\n- **Triangulation.** Every thesis must be backed by ≥3 independent sources of *different types* (primary \u002F academic \u002F industry \u002F discussion). A claim with fewer is flagged \"insufficient evidence,\" not stated as fact.\n- **Source-grounding.** Each source becomes its own `sources\u002FNN_slug.md` with metadata, verbatim quotes, and scores. No dangling claim — every assertion links back to a specific file. An empty fetch produces an empty claim, never a fabricated citation.\n- **Adversarial pass.** Phase 6 always runs the strongest available reasoning: 4 self-critique questions plus an active search for counter-arguments and disconfirming evidence.\n- **Falsifiable hypotheses.** Phase 1 commits to 2–4 hypotheses; Phases 5–6 explicitly confirm or refute each against the evidence, or mark it under-determined.\n- **Parallel sub-agents.** Phase 4 launches search sub-agents concurrently (cheap models for broad web sweeps, stronger ones for reasoning-heavy subtopics) — never one-at-a-time.\n- **Refresh protocol.** Phase 7 emits `refresh_targets.md`; an `update \u003Cslug>` run produces a delta (new entrants, entity changes, refreshed numbers, adversarial triggers) instead of replaying the whole investigation.\n- **Atomic findings.** Reusable theses in `findings\u002FFN.md` plus a `sources.csv` index — research compounds across questions instead of starting from zero each time.\n\n## Output structure\n\n```\n\u003Croot>\u002F\u003Cslug>\u002F\n├── plan.md                  # scope, sourcing strategy, risk register, changelog\n├── sources.csv              # index of every source with scores\n├── sources\u002F\n│   ├── 01_\u003Cslug>.md         # one file = one source (metadata + verbatim quotes)\n│   └── ...\n├── findings\u002F                # atomic, reusable theses (larger investigations)\n│   └── F1_\u003Cshort>.md\n├── refresh_targets.md       # what to watch on update (medium\u002Fdeep)\n├── diffs\u002F\n│   └── YYYY-MM-DD_delta.md   # delta from an `update \u003Cslug>` run\n└── YYYY-MM-DD_\u003Cgenre>.md     # final report\n```\n\n## When to use\n\n- A low-quality answer is expensive: strategy, business plan, report, or article groundwork.\n- Comparing N institutions, products, methodologies, or markets and you need defensible reasoning.\n- Validating a hypothesis or a decision against external data.\n- Meta-research: \"understand how X works,\" \"map the landscape of Y,\" answering a connected series of questions.\n\n## Anti-Patterns\n\n- **Don't skip the existing-work check.** Before searching, see whether the answer is already in the project or in a prior research folder — you risk re-researching something you already have.\n- **Don't skip reframing**, even when the request \"seems clear.\" The decision behind the question usually changes the search.\n- **Don't output to chat only.** Always persist sources and the report to files — the reuse value is in the folder, not the transcript.\n- **Don't fabricate citations.** If a fetch returns nothing, the claim is empty — never invent a plausible URL. Bind every claim to a saved verbatim quote.\n- **Don't build conclusions on a thin corpus.** Too few sources, or sources that all share one type, means triangulation hasn't happened — say so rather than overstating confidence.\n- **Don't skip the adversarial pass** on medium\u002Fdeep investigations. Confirmation-only research is the failure mode this skill exists to prevent.\n- **Don't run sub-agents sequentially.** Fan-out in parallel; serial search wastes the wall-clock advantage.\n- **Don't collapse `sources\u002F` into one file.** Per-source files are what make findings searchable and reusable across investigations.\n- **Don't pick the heaviest model for everything.** Match model to subtask — cheap for broad sweeps, strong for synthesis and the adversarial pass.\n\n## Cross-References\n\n- **research router** — for fast topic overviews where decision risk is low; `deep-research` is the heavyweight alternative when rigor matters more than speed.\n- **competitive-teardown** — for comparing N competitors on a structured 12-dimension matrix.\n- **litreview \u002F dossier \u002F patent** — domain specialists when the investigation is narrowly academic, person\u002Fcompany-focused, or patent-focused.\n",{"name":5,"description":7},"main","55ae24ca5523c0499dd70b2874ef674a0e66a85b","research\u002Fdeep-research\u002Fskills\u002Fdeep-research","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator","2026-07-04 02:45:55",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add motivatedc-creator\u002FSaafy --skill deep-research",{"tool":36,"command":37},"bunx","bunx skills add motivatedc-creator\u002FSaafy --skill deep-research",{"tool":39,"command":40},"pnpm","pnpm dlx skills add motivatedc-creator\u002FSaafy --skill deep-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fdeep-research\u002Fskills\u002Fdeep-research\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Ffull-catalog.md","REFERENCE","参考文档",980,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fdeep-research\u002Fskills\u002Fdeep-research\u002Freferences\u002Ffull-catalog.md",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M78558T3RQ22S1B5H0FJAY1Y","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. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7854YEAAV883M2PKS04TQEK","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. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"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]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7854NCGDBQ6Q0QG2YY4VHSX","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. Use when the user requests multi-source recency intelligence on a topic (e.g., '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]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M78549YZMPYGC1F6S7ZJ4VF8","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. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). 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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M78541PWEQMBPN91PEZZK8H7","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7853P7CWJNW5G0Z99YB6H5D","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.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' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., '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 use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]