[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFC4V2FA3NRPZF3FHCNC2V":3,"skill-same:01M6MFC4V2FA3NRPZF3FHCNC2V":71},{"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":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6MFC4V2FA3NRPZF3FHCNC2V","ceo-advisor",null,"Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.","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-ceo-advisor-skill-226f5a21\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"ceo advisor","ceo","advisor","fundraising","executive strategy","for","updates","investors","strategic","strategic planning","scenario","leadership","decision-making","presentations","culture","use","strategy","decision","planning","development","2026-11-10 10:12:30",false,"---\nname: \"ceo-advisor\"\ndescription: \"Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.\"\nlicense: MIT\nmetadata:\n  version: 2.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: ceo-leadership\n  updated: 2026-03-05\n  python-tools: strategy_analyzer.py, financial_scenario_analyzer.py\n  frameworks: executive-decisions, board-governance, leadership-culture\n---\n\n# CEO Advisor\n\nStrategic leadership frameworks for vision, fundraising, board management, culture, and stakeholder alignment.\n\n## Keywords\nCEO, chief executive officer, strategy, strategic planning, fundraising, board management, investor relations, culture, organizational leadership, vision, mission, stakeholder management, capital allocation, crisis management, succession planning\n\n## Quick Start\n\n```bash\npython scripts\u002Fstrategy_analyzer.py          # Analyze strategic options with weighted scoring\npython scripts\u002Ffinancial_scenario_analyzer.py # Model financial scenarios (base\u002Fbull\u002Fbear)\n```\n\n## Core Responsibilities\n\n### 1. Vision & Strategy\nSet the direction. Not a 50-page document — a clear, compelling answer to \"Where are we going and why?\"\n\n**Strategic planning cycle:**\n- Annual: 3-year vision refresh + 1-year strategic plan\n- Quarterly: OKR setting with C-suite (COO drives execution)\n- Monthly: strategy health check — are we still on track?\n\n**Stage-adaptive time horizons:**\n- Seed\u002FPre-PMF: 3-month \u002F 6-month \u002F 12-month\n- Series A: 6-month \u002F 1-year \u002F 2-year\n- Series B+: 1-year \u002F 3-year \u002F 5-year\n\nSee `references\u002Fexecutive_decision_framework.md` for the full Go\u002FNo-Go framework, crisis playbook, and capital allocation model.\n\n### 2. Capital & Resource Management\nYou're the chief allocator. Every dollar, every person, every hour of engineering time is a bet.\n\n**Capital allocation priorities:**\n1. Keep the lights on (operations, must-haves)\n2. Protect the core (retention, quality, security)\n3. Grow the core (expansion of what works)\n4. Fund new bets (innovation, new products\u002Fmarkets)\n\n**Fundraising:** Know your numbers cold. Timing matters more than valuation. See `references\u002Fboard_governance_investor_relations.md`.\n\n### 3. Stakeholder Leadership\nYou serve multiple masters. Priority order:\n1. Customers (they pay the bills)\n2. Team (they build the product)\n3. Board\u002FInvestors (they fund the mission)\n4. Partners (they extend your reach)\n\n### 4. Organizational Culture\nCulture is what people do when you're not in the room. It's your job to define it, model it, and enforce it.\n\nSee `references\u002Fleadership_organizational_culture.md` for culture development frameworks and the CEO learning agenda. Also see `culture-architect\u002F` for the operational culture toolkit.\n\n### 5. Board & Investor Management\nYour board can be your greatest asset or your biggest liability. The difference is how you manage them.\n\nSee `references\u002Fboard_governance_investor_relations.md` for board meeting prep, investor communication cadence, and managing difficult directors. Also see `board-deck-builder\u002F` for assembling the actual board deck.\n\n## Key Questions a CEO Asks\n\n- \"Can every person in this company explain our strategy in one sentence?\"\n- \"What's the one thing that, if it goes wrong, kills us?\"\n- \"Am I spending my time on the highest-leverage activity right now?\"\n- \"What decision am I avoiding? Why?\"\n- \"If we could only do one thing this quarter, what would it be?\"\n- \"Do our investors and our team hear the same story from me?\"\n- \"Who would replace me if I got hit by a bus tomorrow?\"\n\n## CEO Metrics Dashboard\n\n| Category | Metric | Target | Frequency |\n|----------|--------|--------|-----------|\n| **Strategy** | Annual goals hit rate | > 70% | Quarterly |\n| **Revenue** | ARR growth rate | Stage-dependent | Monthly |\n| **Capital** | Months of runway | > 12 months | Monthly |\n| **Capital** | Burn multiple | \u003C 2x | Monthly |\n| **Product** | NPS \u002F PMF score | > 40 NPS | Quarterly |\n| **People** | Regrettable attrition | \u003C 10% | Monthly |\n| **People** | Employee engagement | > 7\u002F10 | Quarterly |\n| **Board** | Board NPS (your relationship) | Positive trend | Quarterly |\n| **Personal** | % time on strategic work | > 40% | Weekly |\n\n## Red Flags\n\n- You're the bottleneck for more than 3 decisions per week\n- The board surprises you with questions you can't answer\n- Your calendar is 80%+ meetings with no strategic blocks\n- Key people are leaving and you didn't see it coming\n- You're fundraising reactively (runway \u003C 6 months, no plan)\n- Your team can't articulate the strategy without you in the room\n- You're avoiding a hard conversation (co-founder, investor, underperformer)\n\n## Integration with C-Suite Roles\n\n| When... | CEO works with... | To... |\n|---------|-------------------|-------|\n| Setting direction | COO | Translate vision into OKRs and execution plan |\n| Fundraising | CFO | Model scenarios, prep financials, negotiate terms |\n| Board meetings | All C-suite | Each role contributes their section |\n| Culture issues | CHRO | Diagnose and address people\u002Fculture problems |\n| Product vision | CPO | Align product strategy with company direction |\n| Market positioning | CMO | Ensure brand and messaging reflect strategy |\n| Revenue targets | CRO | Set realistic targets backed by pipeline data |\n| Security\u002Fcompliance | CISO | Understand risk posture for board reporting |\n| Technical strategy | CTO | Align tech investments with business priorities |\n| Hard decisions | Executive Mentor | Stress-test before committing |\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Runway \u003C 12 months with no fundraising plan → flag immediately\n- Strategy hasn't been reviewed in 2+ quarters → prompt refresh\n- Board meeting approaching with no prep → initiate board-prep flow\n- Founder spending \u003C 20% time on strategic work → raise it\n- Key exec departure risk visible → escalate to CHRO\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Help me think about strategy\" | Strategic options matrix with risk-adjusted scoring |\n| \"Prep me for the board\" | Board narrative + anticipated questions + data gaps |\n| \"Should we raise?\" | Fundraising readiness assessment with timeline |\n| \"We need to decide on X\" | Decision framework with options, trade-offs, recommendation |\n| \"How are we doing?\" | CEO scorecard with traffic-light metrics |\n\n## Reasoning Technique: Tree of Thought\n\nExplore multiple futures. For every strategic decision, generate at least 3 paths. Evaluate each path for upside, downside, reversibility, and second-order effects. Pick the path with the best risk-adjusted outcome.\n\n**Stage-adaptive horizons:**\n- Seed: project 3m\u002F6m\u002F12m\n- Series A: project 6m\u002F1y\u002F2y\n- Series B+: project 1y\u002F3y\u002F5y\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\n## Resources\n- `references\u002Fexecutive_decision_framework.md` — Go\u002FNo-Go framework, crisis playbook, capital allocation\n- `references\u002Fboard_governance_investor_relations.md` — Board management, investor communication, fundraising\n- `references\u002Fleadership_organizational_culture.md` — Culture development, CEO routines, succession planning\n","# CEO Advisor\n\nStrategic leadership frameworks for vision, fundraising, board management, culture, and stakeholder alignment.\n\n## Keywords\nCEO, chief executive officer, strategy, strategic planning, fundraising, board management, investor relations, culture, organizational leadership, vision, mission, stakeholder management, capital allocation, crisis management, succession planning\n\n## Quick Start\n\n```bash\npython scripts\u002Fstrategy_analyzer.py          # Analyze strategic options with weighted scoring\npython scripts\u002Ffinancial_scenario_analyzer.py # Model financial scenarios (base\u002Fbull\u002Fbear)\n```\n\n## Core Responsibilities\n\n### 1. Vision & Strategy\nSet the direction. Not a 50-page document — a clear, compelling answer to \"Where are we going and why?\"\n\n**Strategic planning cycle:**\n- Annual: 3-year vision refresh + 1-year strategic plan\n- Quarterly: OKR setting with C-suite (COO drives execution)\n- Monthly: strategy health check — are we still on track?\n\n**Stage-adaptive time horizons:**\n- Seed\u002FPre-PMF: 3-month \u002F 6-month \u002F 12-month\n- Series A: 6-month \u002F 1-year \u002F 2-year\n- Series B+: 1-year \u002F 3-year \u002F 5-year\n\nSee `references\u002Fexecutive_decision_framework.md` for the full Go\u002FNo-Go framework, crisis playbook, and capital allocation model.\n\n### 2. Capital & Resource Management\nYou're the chief allocator. Every dollar, every person, every hour of engineering time is a bet.\n\n**Capital allocation priorities:**\n1. Keep the lights on (operations, must-haves)\n2. Protect the core (retention, quality, security)\n3. Grow the core (expansion of what works)\n4. Fund new bets (innovation, new products\u002Fmarkets)\n\n**Fundraising:** Know your numbers cold. Timing matters more than valuation. See `references\u002Fboard_governance_investor_relations.md`.\n\n### 3. Stakeholder Leadership\nYou serve multiple masters. Priority order:\n1. Customers (they pay the bills)\n2. Team (they build the product)\n3. Board\u002FInvestors (they fund the mission)\n4. Partners (they extend your reach)\n\n### 4. Organizational Culture\nCulture is what people do when you're not in the room. It's your job to define it, model it, and enforce it.\n\nSee `references\u002Fleadership_organizational_culture.md` for culture development frameworks and the CEO learning agenda. Also see `culture-architect\u002F` for the operational culture toolkit.\n\n### 5. Board & Investor Management\nYour board can be your greatest asset or your biggest liability. The difference is how you manage them.\n\nSee `references\u002Fboard_governance_investor_relations.md` for board meeting prep, investor communication cadence, and managing difficult directors. Also see `board-deck-builder\u002F` for assembling the actual board deck.\n\n## Key Questions a CEO Asks\n\n- \"Can every person in this company explain our strategy in one sentence?\"\n- \"What's the one thing that, if it goes wrong, kills us?\"\n- \"Am I spending my time on the highest-leverage activity right now?\"\n- \"What decision am I avoiding? Why?\"\n- \"If we could only do one thing this quarter, what would it be?\"\n- \"Do our investors and our team hear the same story from me?\"\n- \"Who would replace me if I got hit by a bus tomorrow?\"\n\n## CEO Metrics Dashboard\n\n| Category | Metric | Target | Frequency |\n|----------|--------|--------|-----------|\n| **Strategy** | Annual goals hit rate | > 70% | Quarterly |\n| **Revenue** | ARR growth rate | Stage-dependent | Monthly |\n| **Capital** | Months of runway | > 12 months | Monthly |\n| **Capital** | Burn multiple | \u003C 2x | Monthly |\n| **Product** | NPS \u002F PMF score | > 40 NPS | Quarterly |\n| **People** | Regrettable attrition | \u003C 10% | Monthly |\n| **People** | Employee engagement | > 7\u002F10 | Quarterly |\n| **Board** | Board NPS (your relationship) | Positive trend | Quarterly |\n| **Personal** | % time on strategic work | > 40% | Weekly |\n\n## Red Flags\n\n- You're the bottleneck for more than 3 decisions per week\n- The board surprises you with questions you can't answer\n- Your calendar is 80%+ meetings with no strategic blocks\n- Key people are leaving and you didn't see it coming\n- You're fundraising reactively (runway \u003C 6 months, no plan)\n- Your team can't articulate the strategy without you in the room\n- You're avoiding a hard conversation (co-founder, investor, underperformer)\n\n## Integration with C-Suite Roles\n\n| When... | CEO works with... | To... |\n|---------|-------------------|-------|\n| Setting direction | COO | Translate vision into OKRs and execution plan |\n| Fundraising | CFO | Model scenarios, prep financials, negotiate terms |\n| Board meetings | All C-suite | Each role contributes their section |\n| Culture issues | CHRO | Diagnose and address people\u002Fculture problems |\n| Product vision | CPO | Align product strategy with company direction |\n| Market positioning | CMO | Ensure brand and messaging reflect strategy |\n| Revenue targets | CRO | Set realistic targets backed by pipeline data |\n| Security\u002Fcompliance | CISO | Understand risk posture for board reporting |\n| Technical strategy | CTO | Align tech investments with business priorities |\n| Hard decisions | Executive Mentor | Stress-test before committing |\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Runway \u003C 12 months with no fundraising plan → flag immediately\n- Strategy hasn't been reviewed in 2+ quarters → prompt refresh\n- Board meeting approaching with no prep → initiate board-prep flow\n- Founder spending \u003C 20% time on strategic work → raise it\n- Key exec departure risk visible → escalate to CHRO\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Help me think about strategy\" | Strategic options matrix with risk-adjusted scoring |\n| \"Prep me for the board\" | Board narrative + anticipated questions + data gaps |\n| \"Should we raise?\" | Fundraising readiness assessment with timeline |\n| \"We need to decide on X\" | Decision framework with options, trade-offs, recommendation |\n| \"How are we doing?\" | CEO scorecard with traffic-light metrics |\n\n## Reasoning Technique: Tree of Thought\n\nExplore multiple futures. For every strategic decision, generate at least 3 paths. Evaluate each path for upside, downside, reversibility, and second-order effects. Pick the path with the best risk-adjusted outcome.\n\n**Stage-adaptive horizons:**\n- Seed: project 3m\u002F6m\u002F12m\n- Series A: project 6m\u002F1y\u002F2y\n- Series B+: project 1y\u002F3y\u002F5y\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\n## Resources\n- `references\u002Fexecutive_decision_framework.md` — Go\u002FNo-Go framework, crisis playbook, capital allocation\n- `references\u002Fboard_governance_investor_relations.md` — Board management, investor communication, fundraising\n- `references\u002Fleadership_organizational_culture.md` — Culture development, CEO routines, succession planning\n",{"name":5,"license":14,"metadata":43,"description":7},{"author":44,"domain":45,"updated":46,"version":47,"category":48,"frameworks":49,"python-tools":50},"Alireza Rezvani","ceo-leadership",1772668800000,"2.0.0","c-level","executive-decisions, board-governance, leadership-culture","strategy_analyzer.py, financial_scenario_analyzer.py","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-ceo-advisor-skill-226f5a21","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill ceo-advisor",{"tool":63,"command":64},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill ceo-advisor",{"tool":66,"command":67},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill ceo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-ceo-advisor-skill-226f5a21\u002FSKILL.md",true,[],[72,96,124,157,185,220],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":38},"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",[],[74,79,80,81,82,83,84,85,86,87,88,89,90,33,91,92,93,94,23,95],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","scope","webmcp",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":38},"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",[],[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":138,"publishedAt":38},"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",[130,135],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":136,"categoryName":137,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000023","Skill与智能体开发",[139,140,141,142,143,144,145,146,147,148,149,150,151,33,152,153,154,155,23,156],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":38},"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",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000011","运维与部署",[167,168,169,170,171,172,173,174,175,33,176,177,178,179,180,181,182,183,184,23],"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":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":202,"publishedAt":38},"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",[191,194,199],{"categoryNo":192,"categoryName":193,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":195,"categoryName":196,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":200,"categoryName":201,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000038","人力资源",[203,204,205,206,207,208,209,210,105,211,33,212,213,214,215,216,217,218,23,219],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":226,"publishedAt":38},"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",[],[227,228,229,230,231,206,232,33,216,233,234,235,236,237,238,239,240,241,23,242],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]