[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQAPCCYGCJD5PGMAQJCK87":3,"skill-same:01M7BQAPCCYGCJD5PGMAQJCK87":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},"01M7BQAPCCYGCJD5PGMAQJCK87","cco-review",null,"\u002Fcs:cco-review \u003Cplan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire.","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\u002Fcco-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"cco-review\"\ndescription: \"\u002Fcs:cco-review \u003Cplan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire.\"\n---\n\n# \u002Fcs:cco-review — CCO Forcing Questions\n\n**Command:** `\u002Fcs:cco-review \u003Cplan>`\n\nThe retention-obsessed CCO pressure-tests any plan that touches customer experience. Six questions before any retention claim, segmentation change, CS team expansion, or major CS hire.\n\n## When to Run\n\n- Before any board narrative that includes a retention number\n- Before approving a CS team headcount expansion\n- Before re-segmenting the customer base or changing tier definitions\n- Before launching a customer marketing or advocacy program\n- Before a major CS hire (CSM, AM, Implementation, Customer Marketing)\n- When NRR is \"great\" but churn complaints from CSMs are increasing\n- Before deciding whether to add an AM role separate from CSM\n\n## The Six CCO Questions\n\n### 1. What's the GROSS retention rate?\n**Not NRR. Gross.** NRR can hide a leaky bucket behind expansion.\n- GRR healthy ≥ 90% at growth stage, ≥ 95% at scale\n- If GRR \u003C 85% but NRR > 100%, the product is failing for 15%+ of customers; expansion is masking the failure\n- Run `retention_decomposition_analyzer.py`\n\n### 2. What's the #1 reason customers leave?\n**If you can't name it, you don't understand churn.**\n- 7-category taxonomy: product_fit \u002F competitor_loss \u002F no_value_realized \u002F pricing \u002F champion_left \u002F company_event \u002F tactical_failure\n- Preventable churn = product_fit + no_value_realized + tactical_failure\n- If preventable > 50%, CS has clear leverage; if \u003C 30%, churn is structural (ICP, market, competition)\n\n### 3. What's the median time-to-value (TTV) by segment?\n**Long TTV signals different problems by segment.**\n- Long TTV in low tier = ICP misfit; downgrade or kill\n- Long TTV in high tier = onboarding broken; fix the Implementation Manager handoff\n- TTV is a leading indicator of GRR\n\n### 4. Which customer would you fire today?\n**If \"none\" — your segmentation is broken.**\n- Some accounts cost more than they earn (support cost > 50% of ARR + low ICP fit)\n- Run `customer_segmentation_designer.py` to surface kill list\n- The 3 paths for kill candidates: non-renewal \u002F downgrade-to-tech-touch \u002F raise-price-to-cost-recover\n\n### 5. What's the ARR-per-CSM ratio, and is the model pooled or named?\n**Wrong model wastes capacity.**\n- Strategic: named + exec sponsor, $300K-$1M ARR\u002FCSM\n- Enterprise: named, $500K-$2M\n- Mid-market: pooled, $2M-$5M\n- SMB: tech-touch, $5M+\n- Run `cs_coverage_calculator.py` to size the team\n\n### 6. Is CS in your comp plan, and how is it different from Sales comp?\n**Misalignment is the leading indicator of CS failure.**\n- CS comp: 70\u002F30 base\u002Fvariable typical\n- Variable: 50% gross retention + 30% net retention + 20% activity\n- Anti-pattern: comp CSMs on NPS — they game it\n- Anti-pattern: comp CSMs same as Sales — they sell instead of serve\n\n## Workflow\n\n```bash\n# 1. Retention decomposition (always start here)\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fretention_decomposition_analyzer.py cohorts.json\n\n# 2. Segmentation audit\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fcustomer_segmentation_designer.py customers.json\n\n# 3. Coverage sizing (if making CS team changes)\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fcs_coverage_calculator.py book.json\n```\n\n## Output Format\n\n```markdown\n# CCO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[one sentence — retention | segmentation | coverage | next hire]\n\n## Retention (if applicable)\n- GRR: X% (vs vanity NRR of Y%)\n- Top churn driver: \u003Ccategory> at X% of churn\n- Preventable churn: X% (CS-controllable)\n- Leaky-bucket pattern? yes\u002Fno\n\n## Segmentation (if applicable)\n- Tier distribution: Strategic X \u002F Enterprise X \u002F Mid-market X \u002F SMB X\n- Kill list size: N customers (X% of customers, Y% of ARR)\n- Upgrade candidates: N\n\n## Coverage (if applicable)\n- Current CSMs: N | Required now: M | Required 12mo: P\n- Annual cost (12mo): $X\n- Manager trigger fired: yes\u002Fno\n\n## Org (if applicable)\n- Next hire: \u003CCSM | Support | AM | IM | CS Ops | Customer Marketing>\n- Why this, not the alternative: \u003Cone line>\n- Customer outcome unblocked: \u003Cspecific>\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:cpo-review` — if churn root cause is product_fit or no_value_realized\n- `\u002Fcs:cro-review` — if expansion math or comp alignment is in question\n- `\u002Fcs:cfo-review` — for CS cost commitments and retention-impact-on-revenue\n- `cs-chro-advisor` agent — for CS hires, comp, ladder\n- `\u002Fcs:decide` — log the verdict\n- `\u002Fcs:freeze 30` — on multi-year CS comp plan changes\n\n## Related\n\n- Agent: [`cs-cco-advisor`](..\u002F..\u002Fagents\u002Fcs-cco-advisor.md)\n- Skill: [`chief-customer-officer-advisor`](..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-customer-officer-advisor\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002F..\u002Fbusiness-growth\u002F` (tactical CS execution)\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:cco-review — CCO Forcing Questions\n\n**Command:** `\u002Fcs:cco-review \u003Cplan>`\n\nThe retention-obsessed CCO pressure-tests any plan that touches customer experience. Six questions before any retention claim, segmentation change, CS team expansion, or major CS hire.\n\n## When to Run\n\n- Before any board narrative that includes a retention number\n- Before approving a CS team headcount expansion\n- Before re-segmenting the customer base or changing tier definitions\n- Before launching a customer marketing or advocacy program\n- Before a major CS hire (CSM, AM, Implementation, Customer Marketing)\n- When NRR is \"great\" but churn complaints from CSMs are increasing\n- Before deciding whether to add an AM role separate from CSM\n\n## The Six CCO Questions\n\n### 1. What's the GROSS retention rate?\n**Not NRR. Gross.** NRR can hide a leaky bucket behind expansion.\n- GRR healthy ≥ 90% at growth stage, ≥ 95% at scale\n- If GRR \u003C 85% but NRR > 100%, the product is failing for 15%+ of customers; expansion is masking the failure\n- Run `retention_decomposition_analyzer.py`\n\n### 2. What's the #1 reason customers leave?\n**If you can't name it, you don't understand churn.**\n- 7-category taxonomy: product_fit \u002F competitor_loss \u002F no_value_realized \u002F pricing \u002F champion_left \u002F company_event \u002F tactical_failure\n- Preventable churn = product_fit + no_value_realized + tactical_failure\n- If preventable > 50%, CS has clear leverage; if \u003C 30%, churn is structural (ICP, market, competition)\n\n### 3. What's the median time-to-value (TTV) by segment?\n**Long TTV signals different problems by segment.**\n- Long TTV in low tier = ICP misfit; downgrade or kill\n- Long TTV in high tier = onboarding broken; fix the Implementation Manager handoff\n- TTV is a leading indicator of GRR\n\n### 4. Which customer would you fire today?\n**If \"none\" — your segmentation is broken.**\n- Some accounts cost more than they earn (support cost > 50% of ARR + low ICP fit)\n- Run `customer_segmentation_designer.py` to surface kill list\n- The 3 paths for kill candidates: non-renewal \u002F downgrade-to-tech-touch \u002F raise-price-to-cost-recover\n\n### 5. What's the ARR-per-CSM ratio, and is the model pooled or named?\n**Wrong model wastes capacity.**\n- Strategic: named + exec sponsor, $300K-$1M ARR\u002FCSM\n- Enterprise: named, $500K-$2M\n- Mid-market: pooled, $2M-$5M\n- SMB: tech-touch, $5M+\n- Run `cs_coverage_calculator.py` to size the team\n\n### 6. Is CS in your comp plan, and how is it different from Sales comp?\n**Misalignment is the leading indicator of CS failure.**\n- CS comp: 70\u002F30 base\u002Fvariable typical\n- Variable: 50% gross retention + 30% net retention + 20% activity\n- Anti-pattern: comp CSMs on NPS — they game it\n- Anti-pattern: comp CSMs same as Sales — they sell instead of serve\n\n## Workflow\n\n```bash\n# 1. Retention decomposition (always start here)\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fretention_decomposition_analyzer.py cohorts.json\n\n# 2. Segmentation audit\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fcustomer_segmentation_designer.py customers.json\n\n# 3. Coverage sizing (if making CS team changes)\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fcs_coverage_calculator.py book.json\n```\n\n## Output Format\n\n```markdown\n# CCO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[one sentence — retention | segmentation | coverage | next hire]\n\n## Retention (if applicable)\n- GRR: X% (vs vanity NRR of Y%)\n- Top churn driver: \u003Ccategory> at X% of churn\n- Preventable churn: X% (CS-controllable)\n- Leaky-bucket pattern? yes\u002Fno\n\n## Segmentation (if applicable)\n- Tier distribution: Strategic X \u002F Enterprise X \u002F Mid-market X \u002F SMB X\n- Kill list size: N customers (X% of customers, Y% of ARR)\n- Upgrade candidates: N\n\n## Coverage (if applicable)\n- Current CSMs: N | Required now: M | Required 12mo: P\n- Annual cost (12mo): $X\n- Manager trigger fired: yes\u002Fno\n\n## Org (if applicable)\n- Next hire: \u003CCSM | Support | AM | IM | CS Ops | Customer Marketing>\n- Why this, not the alternative: \u003Cone line>\n- Customer outcome unblocked: \u003Cspecific>\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:cpo-review` — if churn root cause is product_fit or no_value_realized\n- `\u002Fcs:cro-review` — if expansion math or comp alignment is in question\n- `\u002Fcs:cfo-review` — for CS cost commitments and retention-impact-on-revenue\n- `cs-chro-advisor` agent — for CS hires, comp, ladder\n- `\u002Fcs:decide` — log the verdict\n- `\u002Fcs:freeze 30` — on multi-year CS comp plan changes\n\n## Related\n\n- Agent: [`cs-cco-advisor`](..\u002F..\u002Fagents\u002Fcs-cco-advisor.md)\n- Skill: [`chief-customer-officer-advisor`](..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fchief-customer-officer-advisor\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002F..\u002Fbusiness-growth\u002F` (tactical CS execution)\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","7e219d4f922f94392cb65883ba910846c3c2e71b","c-level-agents\u002Fskills\u002Fcco-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 cco-review",{"tool":39,"command":40},"bunx","bunx skills add devlify-marketplace\u002Fdevlify-skills --skill cco-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add devlify-marketplace\u002Fdevlify-skills --skill cco-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fc-level-agents\u002Fskills\u002Fcco-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",[],[]]