[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CS0JTWJN9YA84PTXG22P7":3,"skill-same:01M71CS0JTWJN9YA84PTXG22P7":117},{"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":37,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":71,"commitSha":72,"skillDirectory":73,"forksCount":14,"repositoryHtmlUrl":74,"repositoryHomepageUrl":6,"ownerHtmlUrl":75,"ownerBlogUrl":76,"ownerDescription":77,"updatedAt":78,"install":79,"resources":92},"01M71CS0JTWJN9YA84PTXG22P7","cmo-advisor",null,"Marketing leadership for scaling companies. Brand positioning, growth model design, marketing budget allocation, and marketing org design. Use when designing brand strategy, selecting growth models (PLG vs sales-led vs community-led), allocating marketing budgets, building marketing teams, or when user mentions CMO, brand strategy, growth model, CAC, LTV, channel mix, or marketing ROI.","agency-black\u002FSkills","agency-black","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234862658?v=4","01M6HWVFPNGNR5N2CX9ECSAD57","agencia.black","01M719WF77BF3HN0N9FK1APEFY",0,"MIT","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcmo-advisor\u002FSKILL.md",[18,23,26,31,34],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销",{"categoryNo":35,"categoryName":36,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000040","财务",[38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"cmo advisor","cmo","advisor","org","brand strategy","marketing","allocation","Budget","2026","org design","leadership","when","positioning","growth model","design","mix","model","plg","scaling","community","2026-11-10 10:12:30",false,"---\nname: \"cmo-advisor\"\ndescription: \"Marketing leadership for scaling companies. Brand positioning, growth model design, marketing budget allocation, and marketing org design. Use when designing brand strategy, selecting growth models (PLG vs sales-led vs community-led), allocating marketing budgets, building marketing teams, or when user mentions CMO, brand strategy, growth model, CAC, LTV, channel mix, or marketing ROI.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: cmo-leadership\n  updated: 2026-03-05\n  python-tools: marketing_budget_modeler.py, growth_model_simulator.py\n  frameworks: brand-positioning, growth-frameworks, marketing-org\n---\n\n# CMO Advisor\n\nStrategic marketing leadership — brand positioning, growth model design, budget allocation, and org design. Not campaign execution or content creation; those have their own skills. This is the engine.\n\n## Keywords\nCMO, chief marketing officer, brand strategy, brand positioning, growth model, product-led growth, PLG, sales-led growth, community-led growth, marketing budget, CAC, customer acquisition cost, LTV, lifetime value, channel mix, marketing ROI, pipeline contribution, marketing org, category design, competitive positioning, growth loops, payback period, MQL, pipeline coverage\n\n## Quick Start\n\n```bash\n# Model budget allocation across channels, project MQL output by scenario\npython scripts\u002Fmarketing_budget_modeler.py\n\n# Project MRR growth by model, show impact of channel mix shifts\npython scripts\u002Fgrowth_model_simulator.py\n```\n\n**Reference docs (load when needed):**\n- `references\u002Fbrand_positioning.md` — category design, messaging architecture, battlecards, rebrand framework\n- `references\u002Fgrowth_frameworks.md` — PLG\u002FSLG\u002FCLG playbooks, growth loops, switching models\n- `references\u002Fmarketing_org.md` — team structure by stage, hiring sequence, agency vs. in-house\n\n---\n\n## The Four CMO Questions\n\nEvery CMO must own answers to these — no one else in the C-suite can:\n\n1. **Who are we for?** — ICP, positioning, category\n2. **Why do they choose us?** — Differentiation, messaging, brand\n3. **How do they find us?** — Growth model, channel mix, demand gen\n4. **Is it working?** — CAC, LTV:CAC, pipeline contribution, payback period\n\n---\n\n## Core Responsibilities (Brief)\n\n**Brand & Positioning** — Define category, build messaging architecture, maintain competitive differentiation. Details → `references\u002Fbrand_positioning.md`\n\n**Growth Model** — Choose and operate the right acquisition engine: PLG, sales-led, community-led, or hybrid. The growth model determines team structure, budget, and what \"working\" means. Details → `references\u002Fgrowth_frameworks.md`\n\n**Marketing Budget** — Allocate from revenue target backward: new customers needed → conversion rates by stage → MQLs needed → spend by channel based on CAC. Run `marketing_budget_modeler.py` for scenarios.\n\n**Marketing Org** — Structure follows growth model. Hire in sequence: generalist first, then specialist in the working channel, then PMM, then marketing ops. Details → `references\u002Fmarketing_org.md`\n\n**Channel Mix** — Audit quarterly: MQLs, cost, CAC, payback, trend. Scale what's improving. Cut what's worsening. Don't optimize a channel that isn't in the strategy.\n\n**Board Reporting** — Pipeline contribution, CAC by channel, payback period, LTV:CAC. Not impressions. Not MQLs in isolation.\n\n---\n\n## Key Diagnostic Questions\n\nAsk these before making any strategic recommendation:\n\n- What's your CAC **by channel** (not blended)?\n- What's the payback period on your largest channel?\n- What's your LTV:CAC ratio?\n- What % of pipeline is marketing-sourced vs. sales-sourced?\n- Where do your **best customers** (highest LTV, lowest churn) come from?\n- What's your MQL → Opportunity conversion rate? (proxy for lead quality)\n- Is this brand work or performance marketing? (different timelines, different metrics)\n- What's the activation rate in the product? (PLG signal)\n- If a prospect doesn't buy, why not? (win\u002Floss data)\n\n---\n\n## CMO Metrics Dashboard\n\n| Category | Metric | Healthy Target |\n|----------|--------|---------------|\n| **Pipeline** | Marketing-sourced pipeline % | 50–70% of total |\n| **Pipeline** | Pipeline coverage ratio | 3–4x quarterly quota |\n| **Pipeline** | MQL → Opportunity rate | > 15% |\n| **Efficiency** | Blended CAC payback | \u003C 18 months |\n| **Efficiency** | LTV:CAC ratio | > 3:1 |\n| **Efficiency** | Marketing % of total S&M spend | 30–50% |\n| **Growth** | Brand search volume trend | ↑ QoQ |\n| **Growth** | Win rate vs. primary competitor | > 50% |\n| **Retention** | NPS (marketing-sourced cohort) | > 40 |\n\n---\n\n## Red Flags\n\n- No defined ICP — \"companies with 50-1000 employees\" is not an ICP\n- Marketing and sales disagree on what an MQL is (this is always a system problem, not a people problem)\n- CAC tracked only as a blended number — channel-level CAC is non-negotiable\n- Pipeline attribution is self-reported by sales reps, not CRM-timestamped\n- CMO can't answer \"what's our payback period?\" without a 48-hour research project\n- Brand work and performance marketing have no shared narrative — they're contradicting each other\n- Marketing team is producing content with no documented positioning to anchor it\n- Growth model was chosen because a competitor uses it, not because the product\u002FACV\u002FICP fits\n\n---\n\n## Integration with Other C-Suite Roles\n\n| When... | CMO works with... | To... |\n|---------|-------------------|-------|\n| Pricing changes | CFO + CEO | Understand margin impact on positioning and messaging |\n| Product launch | CPO + CTO | Define launch tier, GTM motion, messaging |\n| Pipeline miss | CFO + CRO | Diagnose: volume problem, quality problem, or velocity problem |\n| Category design | CEO | Secure multi-year organizational commitment to the narrative |\n| New market entry | CEO + CFO | Validate ICP, budget, localization requirements |\n| Sales misalignment | CRO | Align on MQL definition, SLA, and pipeline ownership |\n| Hiring plan | CHRO | Define marketing headcount and skill profile by stage |\n| Retention insights | CCO | Use expansion and churn data to sharpen ICP and messaging |\n| Competitive threat | CEO + CRO | Coordinate battlecards, win\u002Floss, repositioning response |\n\n---\n\n## Resources\n\n- **References:** `references\u002Fbrand_positioning.md`, `references\u002Fgrowth_frameworks.md`, `references\u002Fmarketing_org.md`\n- **Scripts:** `scripts\u002Fmarketing_budget_modeler.py`, `scripts\u002Fgrowth_model_simulator.py`\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- CAC rising quarter over quarter → channel efficiency declining, investigate\n- No brand positioning documented → messaging inconsistent across channels\n- Marketing budget allocation hasn't changed in 6+ months → market changed, budget didn't\n- Competitor launched major campaign → flag for competitive response\n- Pipeline contribution from marketing unclear → measurement gap, fix before spending more\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Plan our marketing budget\" | Channel allocation model with CAC targets per channel |\n| \"Position us vs competitors\" | Positioning map + messaging framework + proof points |\n| \"Design our growth model\" | Growth projection with channel mix scenarios |\n| \"Build the marketing team\" | Hiring plan with sequence, roles, agency vs in-house |\n| \"Marketing board section\" | Pipeline contribution report with channel ROI |\n\n## Reasoning Technique: Recursion of Thought\n\nDraft a marketing strategy, then critique it from the customer's perspective. Refine based on the critique. Repeat until the strategy survives scrutiny.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n","# CMO Advisor\n\nStrategic marketing leadership — brand positioning, growth model design, budget allocation, and org design. Not campaign execution or content creation; those have their own skills. This is the engine.\n\n## Keywords\nCMO, chief marketing officer, brand strategy, brand positioning, growth model, product-led growth, PLG, sales-led growth, community-led growth, marketing budget, CAC, customer acquisition cost, LTV, lifetime value, channel mix, marketing ROI, pipeline contribution, marketing org, category design, competitive positioning, growth loops, payback period, MQL, pipeline coverage\n\n## Quick Start\n\n```bash\n# Model budget allocation across channels, project MQL output by scenario\npython scripts\u002Fmarketing_budget_modeler.py\n\n# Project MRR growth by model, show impact of channel mix shifts\npython scripts\u002Fgrowth_model_simulator.py\n```\n\n**Reference docs (load when needed):**\n- `references\u002Fbrand_positioning.md` — category design, messaging architecture, battlecards, rebrand framework\n- `references\u002Fgrowth_frameworks.md` — PLG\u002FSLG\u002FCLG playbooks, growth loops, switching models\n- `references\u002Fmarketing_org.md` — team structure by stage, hiring sequence, agency vs. in-house\n\n---\n\n## The Four CMO Questions\n\nEvery CMO must own answers to these — no one else in the C-suite can:\n\n1. **Who are we for?** — ICP, positioning, category\n2. **Why do they choose us?** — Differentiation, messaging, brand\n3. **How do they find us?** — Growth model, channel mix, demand gen\n4. **Is it working?** — CAC, LTV:CAC, pipeline contribution, payback period\n\n---\n\n## Core Responsibilities (Brief)\n\n**Brand & Positioning** — Define category, build messaging architecture, maintain competitive differentiation. Details → `references\u002Fbrand_positioning.md`\n\n**Growth Model** — Choose and operate the right acquisition engine: PLG, sales-led, community-led, or hybrid. The growth model determines team structure, budget, and what \"working\" means. Details → `references\u002Fgrowth_frameworks.md`\n\n**Marketing Budget** — Allocate from revenue target backward: new customers needed → conversion rates by stage → MQLs needed → spend by channel based on CAC. Run `marketing_budget_modeler.py` for scenarios.\n\n**Marketing Org** — Structure follows growth model. Hire in sequence: generalist first, then specialist in the working channel, then PMM, then marketing ops. Details → `references\u002Fmarketing_org.md`\n\n**Channel Mix** — Audit quarterly: MQLs, cost, CAC, payback, trend. Scale what's improving. Cut what's worsening. Don't optimize a channel that isn't in the strategy.\n\n**Board Reporting** — Pipeline contribution, CAC by channel, payback period, LTV:CAC. Not impressions. Not MQLs in isolation.\n\n---\n\n## Key Diagnostic Questions\n\nAsk these before making any strategic recommendation:\n\n- What's your CAC **by channel** (not blended)?\n- What's the payback period on your largest channel?\n- What's your LTV:CAC ratio?\n- What % of pipeline is marketing-sourced vs. sales-sourced?\n- Where do your **best customers** (highest LTV, lowest churn) come from?\n- What's your MQL → Opportunity conversion rate? (proxy for lead quality)\n- Is this brand work or performance marketing? (different timelines, different metrics)\n- What's the activation rate in the product? (PLG signal)\n- If a prospect doesn't buy, why not? (win\u002Floss data)\n\n---\n\n## CMO Metrics Dashboard\n\n| Category | Metric | Healthy Target |\n|----------|--------|---------------|\n| **Pipeline** | Marketing-sourced pipeline % | 50–70% of total |\n| **Pipeline** | Pipeline coverage ratio | 3–4x quarterly quota |\n| **Pipeline** | MQL → Opportunity rate | > 15% |\n| **Efficiency** | Blended CAC payback | \u003C 18 months |\n| **Efficiency** | LTV:CAC ratio | > 3:1 |\n| **Efficiency** | Marketing % of total S&M spend | 30–50% |\n| **Growth** | Brand search volume trend | ↑ QoQ |\n| **Growth** | Win rate vs. primary competitor | > 50% |\n| **Retention** | NPS (marketing-sourced cohort) | > 40 |\n\n---\n\n## Red Flags\n\n- No defined ICP — \"companies with 50-1000 employees\" is not an ICP\n- Marketing and sales disagree on what an MQL is (this is always a system problem, not a people problem)\n- CAC tracked only as a blended number — channel-level CAC is non-negotiable\n- Pipeline attribution is self-reported by sales reps, not CRM-timestamped\n- CMO can't answer \"what's our payback period?\" without a 48-hour research project\n- Brand work and performance marketing have no shared narrative — they're contradicting each other\n- Marketing team is producing content with no documented positioning to anchor it\n- Growth model was chosen because a competitor uses it, not because the product\u002FACV\u002FICP fits\n\n---\n\n## Integration with Other C-Suite Roles\n\n| When... | CMO works with... | To... |\n|---------|-------------------|-------|\n| Pricing changes | CFO + CEO | Understand margin impact on positioning and messaging |\n| Product launch | CPO + CTO | Define launch tier, GTM motion, messaging |\n| Pipeline miss | CFO + CRO | Diagnose: volume problem, quality problem, or velocity problem |\n| Category design | CEO | Secure multi-year organizational commitment to the narrative |\n| New market entry | CEO + CFO | Validate ICP, budget, localization requirements |\n| Sales misalignment | CRO | Align on MQL definition, SLA, and pipeline ownership |\n| Hiring plan | CHRO | Define marketing headcount and skill profile by stage |\n| Retention insights | CCO | Use expansion and churn data to sharpen ICP and messaging |\n| Competitive threat | CEO + CRO | Coordinate battlecards, win\u002Floss, repositioning response |\n\n---\n\n## Resources\n\n- **References:** `references\u002Fbrand_positioning.md`, `references\u002Fgrowth_frameworks.md`, `references\u002Fmarketing_org.md`\n- **Scripts:** `scripts\u002Fmarketing_budget_modeler.py`, `scripts\u002Fgrowth_model_simulator.py`\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- CAC rising quarter over quarter → channel efficiency declining, investigate\n- No brand positioning documented → messaging inconsistent across channels\n- Marketing budget allocation hasn't changed in 6+ months → market changed, budget didn't\n- Competitor launched major campaign → flag for competitive response\n- Pipeline contribution from marketing unclear → measurement gap, fix before spending more\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Plan our marketing budget\" | Channel allocation model with CAC targets per channel |\n| \"Position us vs competitors\" | Positioning map + messaging framework + proof points |\n| \"Design our growth model\" | Growth projection with channel mix scenarios |\n| \"Build the marketing team\" | Hiring plan with sequence, roles, agency vs in-house |\n| \"Marketing board section\" | Pipeline contribution report with channel ROI |\n\n## Reasoning Technique: Recursion of Thought\n\nDraft a marketing strategy, then critique it from the customer's perspective. Refine based on the critique. Repeat until the strategy survives scrutiny.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n",{"name":5,"license":15,"metadata":63,"description":7},{"author":64,"domain":65,"updated":66,"version":67,"category":68,"frameworks":69,"python-tools":70},"Alireza Rezvani","cmo-leadership",1772668800000,"1.0.0","c-level","brand-positioning, growth-frameworks, marketing-org","marketing_budget_modeler.py, growth_model_simulator.py","main","681496e0662f4c45c4758fae9d4510ae87311bf2","c-level-advisor\u002Fskills\u002Fcmo-advisor","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills","https:\u002F\u002Fgithub.com\u002Fagency-black","http:\u002F\u002Fwww.dogma.black","Las grandes ideas merecen una ejecución impecable. Construimos plataformas web, aplicaciones y ecosistemas digitales completos. Esta Trinidad es nuestro dogma.","2026-05-29 16:13:55",{"source":8,"skillName":5,"commands":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add agency-black\u002FSkills --skill cmo-advisor",{"tool":85,"command":86},"bunx","bunx skills add agency-black\u002FSkills --skill cmo-advisor",{"tool":88,"command":89},"pnpm","pnpm dlx skills add agency-black\u002FSkills --skill cmo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcmo-advisor\u002FSKILL.md",true,[93,99,103,107,113],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fbrand_positioning.md","REFERENCE","参考文档",16585,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcmo-advisor\u002Freferences\u002Fbrand_positioning.md",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fgrowth_frameworks.md",18927,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcmo-advisor\u002Freferences\u002Fgrowth_frameworks.md",{"path":104,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fmarketing_org.md",11595,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcmo-advisor\u002Freferences\u002Fmarketing_org.md",{"path":108,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002Fgrowth_model_simulator.py","SCRIPT","脚本",16870,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcmo-advisor\u002Fscripts\u002Fgrowth_model_simulator.py",{"path":114,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fmarketing_budget_modeler.py",15511,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcmo-advisor\u002Fscripts\u002Fmarketing_budget_modeler.py",[118,145,172,202,227,251],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":58},"01M71JZVZ0TVW7Z5DQBRWSBG8A","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fzarr-python\u002FSKILL.md",[],[125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144],"zarr python","python","zarr","arrays","Cloud Storage","remote","workflows","scientific","read","write","edit","parallel","dask","for","s3fs","use","numpy","s3","scientific computing","scale",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":58},"01M71JYXC5VAEJT8KXN5GRK32S","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[156,157,158,159,160,57,161,126,162,131,163,164,165,166,167,168,169,170,171,46],"xvary","stock","research","xvary stock research","sec edgar","equity","thesis","analysis","code","Market","compare","market data","analyze","with","codex","cursor",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":176,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":186,"publishedAt":58},"01M71JVSDPDQ5040YBN6J1ASKY","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[180,183],{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[187,188,189,138,190,191,192,193,194,195,196,169,197,198,199,200,201],"webapp","testing","webapp testing","applications","local","frontend","debugging","toolkit","logs","browser","playwright","web","behavior","ui","screenshots",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":176,"licenseFileUrl":206,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":58},"01M71JV64CW7R6FYYK9JWWGW0X","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[209],{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},[211,212,213,198,214,215,216,138,217,218,192,219,140,220,221,222,223,224,225,226],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","file","components","react","multi","state","routing","state management",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":234,"publishedAt":58},"01M71JS4X2FRY41DE84DEP06MN","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-view-transitions\u002FSKILL.md",[233],{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},[222,235,236,237,238,239,240,241,242,216,243,244,245,246,49,221,247,248,249,250],"vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","types","states","element","implementing","api","route","create","libraries",{"skillNo":252,"name":253,"nameZh":6,"description":254,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":255,"categories":256,"keywords":258,"publishedAt":58},"01M71JS1WZ1J4F9YVC2203JBJW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-native-skills\u002FSKILL.md",[257],{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},[238,259,222,260,261,262,263,264,265,138,266,246,267,140,268,269,49,270,271,221],"vercel react native skills","react native","native","react native skills","modules","platform","animations","performance","triggers","react native components","apps","best practices","tasks"]