[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGWKX7CXEP2RK1JNSMN7FH":3,"skill-same:01M6MGWKX7CXEP2RK1JNSMN7FH":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},"01M6MGWKX7CXEP2RK1JNSMN7FH","scenario-war-room",null,"Cross-functional what-if modeling for cascading multi-variable scenarios. Unlike single-assumption stress testing, this models compound adversity across all business functions simultaneously. Use when facing complex risk scenarios, strategic decisions with major downside, or when the user asks 'what if X AND Y both happen?'","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-scenario-war-room-skill-ddbede5d\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"war room","scenario war room","scenario","across","for","with","strategic","functional","multi","stress","modeling","testing","compound","functions","use","business","decisions","risk","planning","stress testing","2026-11-10 10:12:30",false,"---\nname: \"scenario-war-room\"\ndescription: \"Cross-functional what-if modeling for cascading multi-variable scenarios. Unlike single-assumption stress testing, this models compound adversity across all business functions simultaneously. Use when facing complex risk scenarios, strategic decisions with major downside, or when the user asks 'what if X AND Y both happen?'\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: strategic-planning\n  updated: 2026-03-05\n  python-tools: scenario_modeler.py\n  frameworks: scenario-planning\n---\n\n# Scenario War Room\n\nModel cascading what-if scenarios across all business functions. Not single-assumption stress tests — compound adversity that shows how one problem creates the next.\n\n## Keywords\nscenario planning, war room, what-if analysis, risk modeling, cascading effects, compound risk, adversity planning, contingency planning, stress test, crisis planning, multi-variable scenario, pre-mortem\n\n## Quick Start\n\n```bash\npython scripts\u002Fscenario_modeler.py   # Interactive scenario builder with cascade modeling\n```\n\nOr describe the scenario in natural language:\n\n> \"What if we lose our top customer AND miss the Q3 fundraise?\"\n> \"What if 3 engineers quit AND we need to ship by Q3?\"\n> \"What if our market shrinks 30% AND a competitor raises $50M?\"\n\n## What This Is Not\n\n- **Not** a single-assumption stress test (that's `\u002Fem:stress-test`)\n- **Not** financial modeling only — every function gets modeled\n- **Not** worst-case-only — models 3 severity levels\n- **Not** paralysis by analysis — outputs concrete hedges and triggers\n\n## Framework: 6-Step Cascade Model\n\n### Step 1: Define Scenario Variables (max 3)\nState each variable with:\n- **What changes** — specific, quantified if possible\n- **Probability** — your best estimate\n- **Timeline** — when it hits\n\n```\nVariable A: Top customer (28% ARR) gives 60-day termination notice\n  Probability: 15% | Timeline: Within 90 days\n\nVariable B: Series A fundraise delayed 6 months beyond target close\n  Probability: 25% | Timeline: Q3\n\nVariable C: Lead engineer resigns\n  Probability: 20% | Timeline: Unknown\n```\n\n### Step 2: Domain Impact Mapping\n\nFor each variable, each relevant role models impact:\n\n| Domain | Owner | Models |\n|--------|-------|--------|\n| Cash & runway | CFO | Burn impact, runway change, bridge options |\n| Revenue | CRO | ARR gap, churn cascade risk, pipeline |\n| Product | CPO | Roadmap impact, PMF risk |\n| Engineering | CTO | Velocity impact, key person risk |\n| People | CHRO | Attrition cascade, hiring freeze implications |\n| Operations | COO | Capacity, OKR impact, process risk |\n| Security | CISO | Compliance timeline risk |\n| Market | CMO | CAC impact, competitive exposure |\n\n### Step 3: Cascade Effect Mapping\n\nThis is the core. Show how Variable A triggers consequences in domains that trigger Variable B's effects:\n\n```\nTRIGGER: Customer churn ($560K ARR)\n  ↓\nCFO: Runway drops 14 → 8 months\n  ↓\nCHRO: Hiring freeze; retention risk increases (morale hit)\n  ↓\nCTO: 3 open engineering reqs frozen; roadmap slips\n  ↓\nCPO: Q4 feature launch delayed → customer retention risk\n  ↓\nCRO: NRR drops; existing accounts see reduced velocity → more churn risk\n  ↓\nCFO: [Secondary cascade — potential death spiral if not interrupted]\n```\n\nName the cascade explicitly. Show where it can be interrupted.\n\n### Step 4: Severity Matrix\n\nModel three scenarios:\n\n| Scenario | Definition | Recovery |\n|----------|------------|---------|\n| **Base** | One variable hits; others don't | Manageable with plan |\n| **Stress** | Two variables hit simultaneously | Requires significant response |\n| **Severe** | All variables hit; full cascade | Existential; requires board intervention |\n\nFor each severity level:\n- Runway impact\n- ARR impact\n- Headcount impact\n- Timeline to unacceptable state (trigger point)\n\n### Step 5: Trigger Points (Early Warning Signals)\n\nDefine the measurable signal that tells you a scenario is unfolding **before** it's confirmed:\n\n```\nTrigger for Customer Churn Risk:\n  - Sponsor goes dark for >3 weeks\n  - Usage drops >25% MoM\n  - No Q1 QBR confirmed by Dec 1\n\nTrigger for Fundraise Delay:\n  - \u003C3 term sheets after 60 days of process\n  - Lead investor requests >30-day extension on DD\n  - Competitor raises at lower valuation (market signal)\n\nTrigger for Engineering Attrition:\n  - Glassdoor activity from engineering team\n  - 2+ referral interview requests from engineers\n  - Above-market offer counter-required in last 3 months\n```\n\n### Step 6: Hedging Strategies\n\nFor each scenario: actions to take **now** (before the scenario materializes) that reduce impact if it does.\n\n| Hedge | Cost | Impact | Owner | Deadline |\n|-------|------|--------|-------|---------|\n| Establish $500K credit line | $5K\u002Fyear | Buys 3 months if churn hits | CFO | 60 days |\n| 12-month retention bonus for 3 key engineers | $90K | Locks team through fundraise | CHRO | 30 days |\n| Diversify to \u003C20% revenue concentration per customer | Sales effort | Reduces single-customer risk | CRO | 2 quarters |\n| Compress fundraise timeline, start parallel process | CEO time | Closes before runways merge | CEO | Immediate |\n\n---\n\n## Output Format\n\nEvery war room session produces:\n\n```\nSCENARIO: [Name]\nVariables: [A, B, C]\nMost likely path: [which combination actually plays out, with probability]\n\nSEVERITY LEVELS\nBase (A only): [runway\u002FARR impact] — recovery: [X actions]\nStress (A+B): [runway\u002FARR impact] — recovery: [X actions]\nSevere (A+B+C): [runway\u002FARR impact] — existential risk: [yes\u002Fno]\n\nCASCADE MAP\n[A → domain impact → B trigger → domain impact → end state]\n\nEARLY WARNING SIGNALS\n- [Signal 1 → which scenario it indicates]\n- [Signal 2 → which scenario it indicates]\n- [Signal 3 → which scenario it indicates]\n\nHEDGES (take these actions now)\n1. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n2. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n3. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n\nRECOMMENDED DECISION\n[One paragraph. What to do, in what order, and why.]\n```\n\n---\n\n## Rules for Good War Room Sessions\n\n**Max 3 variables per scenario.** More than 3 is noise — you can't meaningfully prepare for 5-variable collapse. Model the 3 that actually worry you.\n\n**Quantify or estimate.** \"Revenue drops\" is not useful. \"$420K ARR at risk over 60 days\" is. Use ranges if uncertain.\n\n**Don't stop at first-order effects.** The damage is always in the cascade, not the initial hit.\n\n**Model recovery, not just impact.** Every scenario should have a \"what we do\" path.\n\n**Separate base case from sensitivity.** Don't conflate \"what probably happens\" with \"what could happen.\"\n\n**Don't over-model.** 3-4 scenarios per planning cycle is the right number. More creates analysis paralysis.\n\n---\n\n## Common Scenarios by Stage\n\n**Seed:**\n- Co-founder leaves + product misses launch\n- Funding runs out + bridge terms unfavorable\n\n**Series A:**\n- Miss ARR target + fundraise delayed\n- Key customer churns + competitor raises\n\n**Series B:**\n- Market contraction + burn multiple spikes\n- Lead investor wants pivot + team resists\n\n## Integration with C-Suite Roles\n\n| Scenario Type | Primary Roles | Cascade To |\n|--------------|---------------|------------|\n| Revenue miss | CRO, CFO | CMO (pipeline), COO (cuts), CHRO (layoffs) |\n| Key person departure | CHRO, COO | CTO (if eng), CRO (if sales) |\n| Fundraise failure | CFO, CEO | COO (runway extension), CHRO (hiring freeze) |\n| Security breach | CISO, CTO | CEO (comms), CFO (cost), CRO (customer impact) |\n| Market shift | CEO, CPO | CMO (repositioning), CRO (new segments) |\n| Competitor move | CMO, CRO | CPO (roadmap response), CEO (strategy) |\n\n## References\n- `references\u002Fscenario-planning.md` — Shell methodology, pre-mortem, Monte Carlo, cascade frameworks\n- `scripts\u002Fscenario_modeler.py` — CLI tool for structured scenario modeling\n","# Scenario War Room\n\nModel cascading what-if scenarios across all business functions. Not single-assumption stress tests — compound adversity that shows how one problem creates the next.\n\n## Keywords\nscenario planning, war room, what-if analysis, risk modeling, cascading effects, compound risk, adversity planning, contingency planning, stress test, crisis planning, multi-variable scenario, pre-mortem\n\n## Quick Start\n\n```bash\npython scripts\u002Fscenario_modeler.py   # Interactive scenario builder with cascade modeling\n```\n\nOr describe the scenario in natural language:\n\n> \"What if we lose our top customer AND miss the Q3 fundraise?\"\n> \"What if 3 engineers quit AND we need to ship by Q3?\"\n> \"What if our market shrinks 30% AND a competitor raises $50M?\"\n\n## What This Is Not\n\n- **Not** a single-assumption stress test (that's `\u002Fem:stress-test`)\n- **Not** financial modeling only — every function gets modeled\n- **Not** worst-case-only — models 3 severity levels\n- **Not** paralysis by analysis — outputs concrete hedges and triggers\n\n## Framework: 6-Step Cascade Model\n\n### Step 1: Define Scenario Variables (max 3)\nState each variable with:\n- **What changes** — specific, quantified if possible\n- **Probability** — your best estimate\n- **Timeline** — when it hits\n\n```\nVariable A: Top customer (28% ARR) gives 60-day termination notice\n  Probability: 15% | Timeline: Within 90 days\n\nVariable B: Series A fundraise delayed 6 months beyond target close\n  Probability: 25% | Timeline: Q3\n\nVariable C: Lead engineer resigns\n  Probability: 20% | Timeline: Unknown\n```\n\n### Step 2: Domain Impact Mapping\n\nFor each variable, each relevant role models impact:\n\n| Domain | Owner | Models |\n|--------|-------|--------|\n| Cash & runway | CFO | Burn impact, runway change, bridge options |\n| Revenue | CRO | ARR gap, churn cascade risk, pipeline |\n| Product | CPO | Roadmap impact, PMF risk |\n| Engineering | CTO | Velocity impact, key person risk |\n| People | CHRO | Attrition cascade, hiring freeze implications |\n| Operations | COO | Capacity, OKR impact, process risk |\n| Security | CISO | Compliance timeline risk |\n| Market | CMO | CAC impact, competitive exposure |\n\n### Step 3: Cascade Effect Mapping\n\nThis is the core. Show how Variable A triggers consequences in domains that trigger Variable B's effects:\n\n```\nTRIGGER: Customer churn ($560K ARR)\n  ↓\nCFO: Runway drops 14 → 8 months\n  ↓\nCHRO: Hiring freeze; retention risk increases (morale hit)\n  ↓\nCTO: 3 open engineering reqs frozen; roadmap slips\n  ↓\nCPO: Q4 feature launch delayed → customer retention risk\n  ↓\nCRO: NRR drops; existing accounts see reduced velocity → more churn risk\n  ↓\nCFO: [Secondary cascade — potential death spiral if not interrupted]\n```\n\nName the cascade explicitly. Show where it can be interrupted.\n\n### Step 4: Severity Matrix\n\nModel three scenarios:\n\n| Scenario | Definition | Recovery |\n|----------|------------|---------|\n| **Base** | One variable hits; others don't | Manageable with plan |\n| **Stress** | Two variables hit simultaneously | Requires significant response |\n| **Severe** | All variables hit; full cascade | Existential; requires board intervention |\n\nFor each severity level:\n- Runway impact\n- ARR impact\n- Headcount impact\n- Timeline to unacceptable state (trigger point)\n\n### Step 5: Trigger Points (Early Warning Signals)\n\nDefine the measurable signal that tells you a scenario is unfolding **before** it's confirmed:\n\n```\nTrigger for Customer Churn Risk:\n  - Sponsor goes dark for >3 weeks\n  - Usage drops >25% MoM\n  - No Q1 QBR confirmed by Dec 1\n\nTrigger for Fundraise Delay:\n  - \u003C3 term sheets after 60 days of process\n  - Lead investor requests >30-day extension on DD\n  - Competitor raises at lower valuation (market signal)\n\nTrigger for Engineering Attrition:\n  - Glassdoor activity from engineering team\n  - 2+ referral interview requests from engineers\n  - Above-market offer counter-required in last 3 months\n```\n\n### Step 6: Hedging Strategies\n\nFor each scenario: actions to take **now** (before the scenario materializes) that reduce impact if it does.\n\n| Hedge | Cost | Impact | Owner | Deadline |\n|-------|------|--------|-------|---------|\n| Establish $500K credit line | $5K\u002Fyear | Buys 3 months if churn hits | CFO | 60 days |\n| 12-month retention bonus for 3 key engineers | $90K | Locks team through fundraise | CHRO | 30 days |\n| Diversify to \u003C20% revenue concentration per customer | Sales effort | Reduces single-customer risk | CRO | 2 quarters |\n| Compress fundraise timeline, start parallel process | CEO time | Closes before runways merge | CEO | Immediate |\n\n---\n\n## Output Format\n\nEvery war room session produces:\n\n```\nSCENARIO: [Name]\nVariables: [A, B, C]\nMost likely path: [which combination actually plays out, with probability]\n\nSEVERITY LEVELS\nBase (A only): [runway\u002FARR impact] — recovery: [X actions]\nStress (A+B): [runway\u002FARR impact] — recovery: [X actions]\nSevere (A+B+C): [runway\u002FARR impact] — existential risk: [yes\u002Fno]\n\nCASCADE MAP\n[A → domain impact → B trigger → domain impact → end state]\n\nEARLY WARNING SIGNALS\n- [Signal 1 → which scenario it indicates]\n- [Signal 2 → which scenario it indicates]\n- [Signal 3 → which scenario it indicates]\n\nHEDGES (take these actions now)\n1. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n2. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n3. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n\nRECOMMENDED DECISION\n[One paragraph. What to do, in what order, and why.]\n```\n\n---\n\n## Rules for Good War Room Sessions\n\n**Max 3 variables per scenario.** More than 3 is noise — you can't meaningfully prepare for 5-variable collapse. Model the 3 that actually worry you.\n\n**Quantify or estimate.** \"Revenue drops\" is not useful. \"$420K ARR at risk over 60 days\" is. Use ranges if uncertain.\n\n**Don't stop at first-order effects.** The damage is always in the cascade, not the initial hit.\n\n**Model recovery, not just impact.** Every scenario should have a \"what we do\" path.\n\n**Separate base case from sensitivity.** Don't conflate \"what probably happens\" with \"what could happen.\"\n\n**Don't over-model.** 3-4 scenarios per planning cycle is the right number. More creates analysis paralysis.\n\n---\n\n## Common Scenarios by Stage\n\n**Seed:**\n- Co-founder leaves + product misses launch\n- Funding runs out + bridge terms unfavorable\n\n**Series A:**\n- Miss ARR target + fundraise delayed\n- Key customer churns + competitor raises\n\n**Series B:**\n- Market contraction + burn multiple spikes\n- Lead investor wants pivot + team resists\n\n## Integration with C-Suite Roles\n\n| Scenario Type | Primary Roles | Cascade To |\n|--------------|---------------|------------|\n| Revenue miss | CRO, CFO | CMO (pipeline), COO (cuts), CHRO (layoffs) |\n| Key person departure | CHRO, COO | CTO (if eng), CRO (if sales) |\n| Fundraise failure | CFO, CEO | COO (runway extension), CHRO (hiring freeze) |\n| Security breach | CISO, CTO | CEO (comms), CFO (cost), CRO (customer impact) |\n| Market shift | CEO, CPO | CMO (repositioning), CRO (new segments) |\n| Competitor move | CMO, CRO | CPO (roadmap response), CEO (strategy) |\n\n## References\n- `references\u002Fscenario-planning.md` — Shell methodology, pre-mortem, Monte Carlo, cascade frameworks\n- `scripts\u002Fscenario_modeler.py` — CLI tool for structured scenario modeling\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","strategic-planning",1772668800000,"1.0.0","c-level","scenario-planning","scenario_modeler.py","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-scenario-war-room-skill-ddbede5d","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 scenario-war-room",{"tool":63,"command":64},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill scenario-war-room",{"tool":66,"command":67},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill scenario-war-room","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-scenario-war-room-skill-ddbede5d\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,32,91,92,93,94,22,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,32,152,153,154,155,22,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,32,176,177,178,179,180,181,182,183,184,22],"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,32,212,213,214,215,216,217,218,22,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,32,216,233,234,235,236,237,238,239,240,241,22,242],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]