[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQAHYR31QEZTM2TM6TCW5Q":3,"skill-same:01M7BQAHYR31QEZTM2TM6TCW5Q":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BQAHYR31QEZTM2TM6TCW5Q","caio-review",null,"\u002Fcs:caio-review \u003Cplan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring. Use when shipping an AI feature without an eval set, choosing between API, fine-tune, and self-hosted, or classifying a use case under the EU AI Act.","devlify-marketplace\u002Fdevlify-skills","devlify-marketplace","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196752365?v=4","01M7BPJC94F4G2AG0T3N220BQ3","Sadiq Abdullahi","01M7BPJC9QENFCHFM5NEFAJR1Y",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fc-level-agents\u002Fskills\u002Fcaio-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"caio-review\"\ndescription: \"\u002Fcs:caio-review \u003Cplan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring. Use when shipping an AI feature without an eval set, choosing between API, fine-tune, and self-hosted, or classifying a use case under the EU AI Act.\"\n---\n\n# \u002Fcs:caio-review — CAIO Forcing Questions\n\n**Command:** `\u002Fcs:caio-review \u003Cplan>`\n\nThe eval-demanding CAIO pressure-tests any plan that involves AI. Six questions before any AI feature ships, any multi-year vendor commitment, or any AI team expansion.\n\n## When to Run\n\n- Before shipping any new AI-powered feature\n- Before signing a multi-year AI vendor contract (API or self-hosted infra)\n- Before EU launch of any AI feature\n- Before a major AI team hire (especially ML engineer or research scientist)\n- Before a fine-tuning project commitment\n- Before adopting AI in a regulated domain (employment, credit, healthcare, education, etc.)\n- When the founder uses the word \"AI\" near \"competitive advantage\" or \"moat\"\n\n## The Six CAIO Questions\n\n### 1. What does this AI need to be good at, and how would you measure it?\n**No eval set = no ship.** Before any AI feature deploys, define the eval criteria.\n- 50-100 representative inputs minimum\n- Expected outputs OR rubric for grading\n- Edge cases: ambiguous, adversarial, format-edge\n- If you can't write down what \"good\" looks like, you don't have a feature; you have a vibe.\n\n### 2. What's the SLO on hallucination \u002F error rate, and what's the fallback?\n**Every AI feature has a failure mode. Plan for it.**\n- Quantified SLO: \"\u003C5% hallucination on factual queries\"\n- Detection mechanism: monitoring, sampling, customer feedback loop\n- Fallback: human-in-loop review, lower-risk default response, refuse-to-answer\n- Blast radius if SLO breached: how many users affected, what is the cost?\n\n### 3. What's the risk tier under EU AI Act, and is conformity assessment required?\n**Run `ai_risk_classifier.py` if any EU residents are affected OR domain is regulated.**\n- PROHIBITED → cannot launch in EU; re-scope\n- HIGH → conformity assessment + EU DB registration + 10 Articles of obligations (3-12 months, $50-200K)\n- LIMITED → transparency obligations (chatbot disclosure, AI-generated content marking)\n- MINIMAL → no specific obligations; NIST AI RMF voluntary\n\n### 4. API, fine-tune, or build?\n**Run `model_buildvsbuy_calculator.py` for the specific use case.**\n- 80% of B2B SaaS use cases: API\n- 15%: fine-tune (when domain-specific behavior + labeled data + ML team + high volume)\n- \u003C1%: build from scratch\n- Decision must consider economic breakeven AND practical feasibility (data, team, compliance)\n\n### 5. What's the 12-month cost trajectory at expected scale?\n**Run `ai_cost_economics.py` for the workload.**\n- API: variable, scales linearly\n- Self-hosted: mostly fixed, breakeven typically 1-10B tokens\u002Fmonth for 70B-class\n- Hidden costs of self-hosted: ops, monitoring, model updates, capacity, failover, security\n- Hidden costs of API: vendor lock-in, capability drift, rate limits, data residency\n- Prompt caching is the most underrated lever; check provider support\n\n### 6. What role unblocks this — and have we hired prerequisites first?\n**Map AI capability to specific role. Founders confuse AI engineer \u002F ML engineer \u002F research scientist.**\n- AI engineer: applied + full-stack + prompts + evals + deployment (most startups need this)\n- ML engineer: fine-tuning + retraining infra (only after platform engineer + labeled data)\n- Research scientist: model invention (only if model IS the product)\n- Don't hire research scientist as first AI hire — they need infrastructure to be productive\n\n## Workflow\n\n```bash\n# 1. Model selection check\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-ai-officer-advisor\u002Fscripts\u002Fmodel_buildvsbuy_calculator.py use_case.json\n\n# 2. Regulatory classification\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-ai-officer-advisor\u002Fscripts\u002Fai_risk_classifier.py use_case.json\n\n# 3. Cost projection\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-ai-officer-advisor\u002Fscripts\u002Fai_cost_economics.py workload.json\n```\n\n## Output Format\n\n```markdown\n# CAIO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[one sentence — which CAIO decision: model selection | risk classification | economics | next hire]\n\n## Eval Discipline\n- Eval set committed: yes\u002Fno\n- SLO defined: \u003Cmetric> \u003C \u003Cthreshold>\n- Fallback behavior: \u003Cone line>\n\n## Model Selection (if applicable)\n- Recommended: API \u002F FINE_TUNE \u002F BUILD\n- 3-year TCO: $X (chosen path) vs $Y (alternatives)\n- Breakeven: \u003Cvolume>\n\n## Risk Classification (if applicable)\n- EU AI Act tier: PROHIBITED \u002F HIGH \u002F LIMITED \u002F MINIMAL\n- Conformity assessment required: yes\u002Fno\n- US state triggers: [list]\n- Required controls open: N\n\n## Cost Economics (if applicable)\n- Monthly cost at current volume: $X\n- Breakeven for self-hosted migration: \u003Cvolume>\n- Migration cost if applicable: $X (3-6 months)\n\n## Org (if applicable)\n- Next hire: \u003Crole>\n- Why this, not the alternative: \u003Cone line>\n- Prerequisite hires in place: yes\u002Fno\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:cdo-review` — for any training-data implications\n- `\u002Fcs:gc-review` — for AI vendor contracts, output liability, training-data licensing\n- `\u002Fcs:ciso-review` — for prompt injection \u002F jailbreak \u002F training-data poisoning threat model\n- `\u002Fcs:cfo-review` — for multi-year vendor or GPU commitment TCO\n- `cs-chro-advisor` agent — for AI team hires (comp, ladder, leveling)\n- `\u002Fcs:decide` — log the verdict\n- `\u002Fcs:freeze 60` — on multi-year AI commitments\n\n## Related\n\n- Agent: [`cs-caio-advisor`](..\u002F..\u002Fagents\u002Fcs-caio-advisor.md)\n- Skill: [`chief-ai-officer-advisor`](..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-ai-officer-advisor\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002F` (training data rights, data strategy)\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:caio-review — CAIO Forcing Questions\n\n**Command:** `\u002Fcs:caio-review \u003Cplan>`\n\nThe eval-demanding CAIO pressure-tests any plan that involves AI. Six questions before any AI feature ships, any multi-year vendor commitment, or any AI team expansion.\n\n## When to Run\n\n- Before shipping any new AI-powered feature\n- Before signing a multi-year AI vendor contract (API or self-hosted infra)\n- Before EU launch of any AI feature\n- Before a major AI team hire (especially ML engineer or research scientist)\n- Before a fine-tuning project commitment\n- Before adopting AI in a regulated domain (employment, credit, healthcare, education, etc.)\n- When the founder uses the word \"AI\" near \"competitive advantage\" or \"moat\"\n\n## The Six CAIO Questions\n\n### 1. What does this AI need to be good at, and how would you measure it?\n**No eval set = no ship.** Before any AI feature deploys, define the eval criteria.\n- 50-100 representative inputs minimum\n- Expected outputs OR rubric for grading\n- Edge cases: ambiguous, adversarial, format-edge\n- If you can't write down what \"good\" looks like, you don't have a feature; you have a vibe.\n\n### 2. What's the SLO on hallucination \u002F error rate, and what's the fallback?\n**Every AI feature has a failure mode. Plan for it.**\n- Quantified SLO: \"\u003C5% hallucination on factual queries\"\n- Detection mechanism: monitoring, sampling, customer feedback loop\n- Fallback: human-in-loop review, lower-risk default response, refuse-to-answer\n- Blast radius if SLO breached: how many users affected, what is the cost?\n\n### 3. What's the risk tier under EU AI Act, and is conformity assessment required?\n**Run `ai_risk_classifier.py` if any EU residents are affected OR domain is regulated.**\n- PROHIBITED → cannot launch in EU; re-scope\n- HIGH → conformity assessment + EU DB registration + 10 Articles of obligations (3-12 months, $50-200K)\n- LIMITED → transparency obligations (chatbot disclosure, AI-generated content marking)\n- MINIMAL → no specific obligations; NIST AI RMF voluntary\n\n### 4. API, fine-tune, or build?\n**Run `model_buildvsbuy_calculator.py` for the specific use case.**\n- 80% of B2B SaaS use cases: API\n- 15%: fine-tune (when domain-specific behavior + labeled data + ML team + high volume)\n- \u003C1%: build from scratch\n- Decision must consider economic breakeven AND practical feasibility (data, team, compliance)\n\n### 5. What's the 12-month cost trajectory at expected scale?\n**Run `ai_cost_economics.py` for the workload.**\n- API: variable, scales linearly\n- Self-hosted: mostly fixed, breakeven typically 1-10B tokens\u002Fmonth for 70B-class\n- Hidden costs of self-hosted: ops, monitoring, model updates, capacity, failover, security\n- Hidden costs of API: vendor lock-in, capability drift, rate limits, data residency\n- Prompt caching is the most underrated lever; check provider support\n\n### 6. What role unblocks this — and have we hired prerequisites first?\n**Map AI capability to specific role. Founders confuse AI engineer \u002F ML engineer \u002F research scientist.**\n- AI engineer: applied + full-stack + prompts + evals + deployment (most startups need this)\n- ML engineer: fine-tuning + retraining infra (only after platform engineer + labeled data)\n- Research scientist: model invention (only if model IS the product)\n- Don't hire research scientist as first AI hire — they need infrastructure to be productive\n\n## Workflow\n\n```bash\n# 1. Model selection check\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-ai-officer-advisor\u002Fscripts\u002Fmodel_buildvsbuy_calculator.py use_case.json\n\n# 2. Regulatory classification\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-ai-officer-advisor\u002Fscripts\u002Fai_risk_classifier.py use_case.json\n\n# 3. Cost projection\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-ai-officer-advisor\u002Fscripts\u002Fai_cost_economics.py workload.json\n```\n\n## Output Format\n\n```markdown\n# CAIO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[one sentence — which CAIO decision: model selection | risk classification | economics | next hire]\n\n## Eval Discipline\n- Eval set committed: yes\u002Fno\n- SLO defined: \u003Cmetric> \u003C \u003Cthreshold>\n- Fallback behavior: \u003Cone line>\n\n## Model Selection (if applicable)\n- Recommended: API \u002F FINE_TUNE \u002F BUILD\n- 3-year TCO: $X (chosen path) vs $Y (alternatives)\n- Breakeven: \u003Cvolume>\n\n## Risk Classification (if applicable)\n- EU AI Act tier: PROHIBITED \u002F HIGH \u002F LIMITED \u002F MINIMAL\n- Conformity assessment required: yes\u002Fno\n- US state triggers: [list]\n- Required controls open: N\n\n## Cost Economics (if applicable)\n- Monthly cost at current volume: $X\n- Breakeven for self-hosted migration: \u003Cvolume>\n- Migration cost if applicable: $X (3-6 months)\n\n## Org (if applicable)\n- Next hire: \u003Crole>\n- Why this, not the alternative: \u003Cone line>\n- Prerequisite hires in place: yes\u002Fno\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:cdo-review` — for any training-data implications\n- `\u002Fcs:gc-review` — for AI vendor contracts, output liability, training-data licensing\n- `\u002Fcs:ciso-review` — for prompt injection \u002F jailbreak \u002F training-data poisoning threat model\n- `\u002Fcs:cfo-review` — for multi-year vendor or GPU commitment TCO\n- `cs-chro-advisor` agent — for AI team hires (comp, ladder, leveling)\n- `\u002Fcs:decide` — log the verdict\n- `\u002Fcs:freeze 60` — on multi-year AI commitments\n\n## Related\n\n- Agent: [`cs-caio-advisor`](..\u002F..\u002Fagents\u002Fcs-caio-advisor.md)\n- Skill: [`chief-ai-officer-advisor`](..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-ai-officer-advisor\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-data-officer-advisor\u002F` (training data rights, data strategy)\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","7e219d4f922f94392cb65883ba910846c3c2e71b","c-level-agents\u002Fskills\u002Fcaio-review",0,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace","devlify.com.ng","Software Developer & full-stack dev building secure web and mobile applications, AI\u002FML solutions, and scalable digital products. Founder of Devlify ","2026-08-30 00:40:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add devlify-marketplace\u002Fdevlify-skills --skill caio-review",{"tool":39,"command":40},"bunx","bunx skills add devlify-marketplace\u002Fdevlify-skills --skill caio-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add devlify-marketplace\u002Fdevlify-skills --skill caio-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fc-level-agents\u002Fskills\u002Fcaio-review\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7BRV5Q3BJT22HG25WJFTKZN","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7BRTW6RRTHXT6SBE41AY5GD","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, deepread for evidence-first reading of supplied documents) 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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7BRTMK3PGPNH76R2HY57AKC","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7BRTAR0YJWNZ2AP3QTH39BW","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7BRT3J0V5A9V3VJ96G97AGW","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7BRSS7P0CJP7X9ERDFYN6GC","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]