[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFG8JNFF4D6D8P91WNC6RN":3,"skill-same:01M6MFG8JNFF4D6D8P91WNC6RN":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":36,"publishedAt":57,"linkOnly":58,"markdownContent":59,"markdownBody":60,"frontMatter":61,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":13,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":75,"install":76,"resources":89},"01M6MFG8JNFF4D6D8P91WNC6RN","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.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-cmo-advisor-skill-02149af5\u002FSKILL.md",[17,22,25,30,33],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":31,"categoryName":32,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000035","市场营销",{"categoryNo":34,"categoryName":35,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000040","财务",[37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56],"cmo advisor","advisor","cmo","positioning","for","allocation","mix","org","plg","growth model","scaling","leadership","design","frameworks","brand strategy","community","brand","model","marketing","Budget","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 `..\u002Fagent-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 `..\u002Fagent-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":14,"metadata":62,"description":7},{"author":63,"domain":64,"updated":65,"version":66,"category":67,"frameworks":68,"python-tools":69},"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","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-cmo-advisor-skill-02149af5","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill cmo-advisor",{"tool":82,"command":83},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill cmo-advisor",{"tool":85,"command":86},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill cmo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-cmo-advisor-skill-02149af5\u002FSKILL.md",true,[],[91,116,144,175,203,236],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":57},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[93,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,41,115],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","webmcp",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":120,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":57},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":156,"publishedAt":57},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[150,153],{"categoryNo":151,"categoryName":152,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":154,"categoryName":155,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[157,158,159,160,161,162,163,164,165,166,167,168,169,110,170,171,172,173,41,174],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":184,"publishedAt":57},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[185,186,187,188,189,190,191,192,193,110,194,195,196,197,198,199,200,201,202,41],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":218,"publishedAt":57},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[209,212,215],{"categoryNo":210,"categoryName":211,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":213,"categoryName":214,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":216,"categoryName":217,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000038","人力资源",[219,220,221,222,223,224,225,226,125,227,110,228,229,230,231,232,233,234,41,235],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":242,"publishedAt":57},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[243,244,245,246,247,222,248,110,232,249,250,251,252,253,254,255,256,257,41,258],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]