[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B070R2DA494PSR3C3WPYHH":3,"skill-same:01M7B070R2DA494PSR3C3WPYHH":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M7B070R2DA494PSR3C3WPYHH","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?'","Bhomik04\u002Fava-","Bhomik04","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F110253138?v=4","01M7AZ8PC968MDM5Y1W13JHHBN","bhomik goyal","01M7AZ8PDERKY1AFG9VZ8J0WSX",0,"MIT","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fscenario-war-room\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":15,"metadata":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29,"frameworks":30,"python-tools":31},"Alireza Rezvani","strategic-planning",1772668800000,"1.0.0","c-level","scenario-planning","scenario_modeler.py","main","decebbc662d2b278167b2a17d949479cf4cad66d","skills\u002Fimported\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fscenario-war-room","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-","https:\u002F\u002Fgithub.com\u002FBhomik04","2026-08-23 16:08:45",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Bhomik04\u002Fava- --skill scenario-war-room",{"tool":44,"command":45},"bunx","bunx skills add Bhomik04\u002Fava- --skill scenario-war-room",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Bhomik04\u002Fava- --skill scenario-war-room","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fscenario-war-room\u002FSKILL.md",true,[52,58],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fscenario-planning.md","REFERENCE","参考文档",8011,"https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fscenario-war-room\u002Freferences\u002Fscenario-planning.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"scripts\u002Fscenario_modeler.py","SCRIPT","脚本",17706,"https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fscenario-war-room\u002Fscripts\u002Fscenario_modeler.py",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7B1YZ6EW9K9QQX1VYBXKKWH","spotify-dj","Intelligent music DJ that curates playlists, selects tracks based on mood, analyzes genres, and manages playback queues.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fspotify-dj\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B1YWTNAF22PTEWNDGXQD9G","software-engineer","Autonomous software engineering, AST refactoring, Git worktree isolation, and self-healing test execution.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fsoftware-engineer\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B1YS4HDDEFEJXBB8KW4T3K","obsidian-curator","Curates, organizes, links, and summarizes notes and research in the local Obsidian vault.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fobsidian-curator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7B1YPJYQGB10P4EQ4SFEBFM","document-analysis","Parses, reads, extracts data, and summarizes multi-format documents (PDF, DOCX, Markdown, Text).","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fdocument-analysis\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7B1YJPE6J8PEWQRSRSHJ03C","docker-ops","Inspects, monitors, starts, stops, and diagnoses Docker containers and swarms via Named Pipe.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fdocker-ops\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7B1YEG3JESA4JPJNMVM1556","deep-research","Conducts multi-step autonomous research, source cross-verification, and structured literature synthesis.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fdeep-research\u002FSKILL.md",[],[]]