[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J8ZSWQBH9AZ4BDPSW0GVCN":3,"skill-same:01M6J8ZSWQBH9AZ4BDPSW0GVCN":75},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":48,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":74},"01M6J8ZSWQBH9AZ4BDPSW0GVCN","devops-ensemble-solving",null,"Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.","Flissel\u002Fvibemind-os","Flissel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104565236?v=4","01M6J8Q88NWAJGKPC5TEG9YCNV","Felix Baumann","01M6J8Q8D7XAFY44P70XTJFZBW",1,"MIT","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fskills\u002Fdevops\u002Fensemble-solving\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"devops ensemble solving","ensemble solving","devops","use","solutions","alternatives","for","true","with","generation","imported","valid","behavior","decisions","repo","select","parallel","code","generate","tasks","architecture","2026-11-10 10:12:30",false,"---\nname: devops-ensemble-solving\ndescription: Generate multiple diverse solutions in parallel and select the best.\n  Use for architecture decisions, code generation with multiple valid approaches,\n  or creative tasks where exploring alternatives improves quality.\napp: devops\nrequires_approval: true\nagents:\n- '*'\ninputs: []\nexpected_state:\n  description: Imported skill — behavior matches source repo\n  verification_tool: none\nconfidence: 1.0\nattempts: 0\nsuccesses: 0\nlast_adjusted: '2026-05-11T21:21:56+00:00'\n---\n\n# Ensemble Problem Solving\n\nGenerate multiple solutions in parallel by spawning 3 subagents with different approaches, then evaluate and select the best result.\n\n## When to Use\n\n**Activation phrases:**\n- \"Give me options for...\"\n- \"What's the best way to...\"\n- \"Explore different approaches...\"\n- \"I want to see alternatives...\"\n- \"Compare approaches for...\"\n- \"Which approach should I use...\"\n\n**Good candidates:**\n- Architecture decisions with trade-offs\n- Code generation with multiple valid implementations\n- API design with different philosophies\n- Naming, branding, documentation style\n- Refactoring strategies\n- Algorithm selection\n\n**Skip ensemble for:**\n- Simple lookups or syntax questions\n- Single-cause bug fixes\n- File operations, git commands\n- Deterministic configuration changes\n- Tasks with one obvious solution\n\n## What It Does\n\n1. **Analyzes the task** to determine if ensemble approach is valuable\n2. **Generates 3 distinct prompts** using appropriate diversification strategy\n3. **Spawns 3 parallel subagents** to develop solutions independently\n4. **Evaluates all solutions** using weighted criteria\n5. **Returns the best solution** with explanation and alternatives summary\n\n## Approach\n\n### Step 1: Classify Task Type\n\nDetermine which category fits:\n- **Code Generation**: Functions, classes, APIs, algorithms\n- **Architecture\u002FDesign**: System design, data models, patterns\n- **Creative**: Writing, naming, documentation\n\n### Step 2: Invoke Ensemble Orchestrator\n\n```\nTask tool with:\n- subagent_type: 'ensemble-orchestrator'\n- description: 'Generate and evaluate 3 parallel solutions'\n- prompt: [User's original task with full context]\n```\n\nThe orchestrator handles:\n- Prompt diversification\n- Parallel execution\n- Solution evaluation\n- Winner selection\n\n### Step 3: Present Result\n\nThe orchestrator returns:\n- The winning solution (in full)\n- Evaluation scores for all 3 approaches\n- Why the winner was selected\n- When alternatives might be preferred\n\n## Diversification Strategies\n\n**For Code (Constraint Variation):**\n| Approach | Focus |\n|----------|-------|\n| Simplicity | Minimal code, maximum readability |\n| Performance | Efficient, optimized |\n| Extensibility | Clean abstractions, easy to extend |\n\n**For Architecture (Approach Variation):**\n| Approach | Focus |\n|----------|-------|\n| Top-down | Requirements → Interfaces → Implementation |\n| Bottom-up | Primitives → Composition → Structure |\n| Lateral | Analogies from other domains |\n\n**For Creative (Persona Variation):**\n| Approach | Focus |\n|----------|-------|\n| Expert | Technical precision, authoritative |\n| Pragmatic | Ship-focused, practical |\n| Innovative | Creative, unconventional |\n\n## Evaluation Rubric\n\n| Criterion | Base Weight | Description |\n|-----------|-------------|-------------|\n| Correctness | 30% | Solves the problem correctly |\n| Completeness | 20% | Addresses all requirements |\n| Quality | 20% | How well-crafted |\n| Clarity | 15% | How understandable |\n| Elegance | 15% | How simple\u002Fbeautiful |\n\nWeights adjust based on task type.\n\n## Example\n\n**User:** \"What's the best way to implement a rate limiter?\"\n\n**Skill:**\n1. Classifies as Code Generation\n2. Invokes ensemble-orchestrator\n3. Three approaches generated:\n   - Simple: Token bucket with in-memory counter\n   - Performance: Sliding window with atomic operations\n   - Extensible: Strategy pattern with pluggable backends\n4. Evaluation selects extensible approach (score 8.4)\n5. Returns full implementation with explanation\n\n**Output:**\n```\n## Selected Solution\n\n[Full rate limiter implementation with strategy pattern]\n\n## Why This Solution Won\n\nThe extensible approach scored highest (8.4) because it provides\na clean abstraction that works for both simple use cases and\ncomplex distributed scenarios. The strategy pattern allows\nswapping Redis\u002FMemcached backends without code changes.\n\n## Alternatives\n\n- **Simple approach**: Best if you just need basic in-memory\n  limiting and will never scale beyond one process.\n\n- **Performance approach**: Best for high-throughput scenarios\n  where every microsecond matters.\n```\n\n## Success Criteria\n\n- 3 genuinely different solutions generated\n- Clear evaluation rationale provided\n- Winner selected with confidence\n- Alternatives summarized with use cases\n- User understands trade-offs\n\n## Token Cost\n\n~4x overhead vs single attempt. Worth it for:\n- High-stakes architecture decisions\n- Creative work where first attempt rarely optimal\n- Learning scenarios where seeing alternatives is valuable\n- Code that will be maintained long-term\n\n## Integration\n\n- **feature-planning**: Can ensemble architecture decisions\n- **code-auditor**: Can ensemble analysis perspectives\n- **plan-implementer**: Executes the winning approach\n","# Ensemble Problem Solving\n\nGenerate multiple solutions in parallel by spawning 3 subagents with different approaches, then evaluate and select the best result.\n\n## When to Use\n\n**Activation phrases:**\n- \"Give me options for...\"\n- \"What's the best way to...\"\n- \"Explore different approaches...\"\n- \"I want to see alternatives...\"\n- \"Compare approaches for...\"\n- \"Which approach should I use...\"\n\n**Good candidates:**\n- Architecture decisions with trade-offs\n- Code generation with multiple valid implementations\n- API design with different philosophies\n- Naming, branding, documentation style\n- Refactoring strategies\n- Algorithm selection\n\n**Skip ensemble for:**\n- Simple lookups or syntax questions\n- Single-cause bug fixes\n- File operations, git commands\n- Deterministic configuration changes\n- Tasks with one obvious solution\n\n## What It Does\n\n1. **Analyzes the task** to determine if ensemble approach is valuable\n2. **Generates 3 distinct prompts** using appropriate diversification strategy\n3. **Spawns 3 parallel subagents** to develop solutions independently\n4. **Evaluates all solutions** using weighted criteria\n5. **Returns the best solution** with explanation and alternatives summary\n\n## Approach\n\n### Step 1: Classify Task Type\n\nDetermine which category fits:\n- **Code Generation**: Functions, classes, APIs, algorithms\n- **Architecture\u002FDesign**: System design, data models, patterns\n- **Creative**: Writing, naming, documentation\n\n### Step 2: Invoke Ensemble Orchestrator\n\n```\nTask tool with:\n- subagent_type: 'ensemble-orchestrator'\n- description: 'Generate and evaluate 3 parallel solutions'\n- prompt: [User's original task with full context]\n```\n\nThe orchestrator handles:\n- Prompt diversification\n- Parallel execution\n- Solution evaluation\n- Winner selection\n\n### Step 3: Present Result\n\nThe orchestrator returns:\n- The winning solution (in full)\n- Evaluation scores for all 3 approaches\n- Why the winner was selected\n- When alternatives might be preferred\n\n## Diversification Strategies\n\n**For Code (Constraint Variation):**\n| Approach | Focus |\n|----------|-------|\n| Simplicity | Minimal code, maximum readability |\n| Performance | Efficient, optimized |\n| Extensibility | Clean abstractions, easy to extend |\n\n**For Architecture (Approach Variation):**\n| Approach | Focus |\n|----------|-------|\n| Top-down | Requirements → Interfaces → Implementation |\n| Bottom-up | Primitives → Composition → Structure |\n| Lateral | Analogies from other domains |\n\n**For Creative (Persona Variation):**\n| Approach | Focus |\n|----------|-------|\n| Expert | Technical precision, authoritative |\n| Pragmatic | Ship-focused, practical |\n| Innovative | Creative, unconventional |\n\n## Evaluation Rubric\n\n| Criterion | Base Weight | Description |\n|-----------|-------------|-------------|\n| Correctness | 30% | Solves the problem correctly |\n| Completeness | 20% | Addresses all requirements |\n| Quality | 20% | How well-crafted |\n| Clarity | 15% | How understandable |\n| Elegance | 15% | How simple\u002Fbeautiful |\n\nWeights adjust based on task type.\n\n## Example\n\n**User:** \"What's the best way to implement a rate limiter?\"\n\n**Skill:**\n1. Classifies as Code Generation\n2. Invokes ensemble-orchestrator\n3. Three approaches generated:\n   - Simple: Token bucket with in-memory counter\n   - Performance: Sliding window with atomic operations\n   - Extensible: Strategy pattern with pluggable backends\n4. Evaluation selects extensible approach (score 8.4)\n5. Returns full implementation with explanation\n\n**Output:**\n```\n## Selected Solution\n\n[Full rate limiter implementation with strategy pattern]\n\n## Why This Solution Won\n\nThe extensible approach scored highest (8.4) because it provides\na clean abstraction that works for both simple use cases and\ncomplex distributed scenarios. The strategy pattern allows\nswapping Redis\u002FMemcached backends without code changes.\n\n## Alternatives\n\n- **Simple approach**: Best if you just need basic in-memory\n  limiting and will never scale beyond one process.\n\n- **Performance approach**: Best for high-throughput scenarios\n  where every microsecond matters.\n```\n\n## Success Criteria\n\n- 3 genuinely different solutions generated\n- Clear evaluation rationale provided\n- Winner selected with confidence\n- Alternatives summarized with use cases\n- User understands trade-offs\n\n## Token Cost\n\n~4x overhead vs single attempt. Worth it for:\n- High-stakes architecture decisions\n- Creative work where first attempt rarely optimal\n- Learning scenarios where seeing alternatives is valuable\n- Code that will be maintained long-term\n\n## Integration\n\n- **feature-planning**: Can ensemble architecture decisions\n- **code-auditor**: Can ensemble analysis perspectives\n- **plan-implementer**: Executes the winning approach\n",{"app":21,"name":5,"agents":45,"inputs":47,"attempts":48,"successes":48,"confidence":14,"description":7,"last_adjusted":49,"expected_state":50,"requires_approval":53},[46],"*",[],0,"2026-05-11T21:21:56+00:00",{"description":51,"verification_tool":52},"Imported skill — behavior matches source repo","none",true,"master","5f13b5d2b532c0ab6f847e3aa24d4bfe66f7d461","skills\u002Fdevops\u002Fensemble-solving","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os","https:\u002F\u002Fgithub.com\u002FFlissel","https:\u002F\u002Fvibemind.space","Co-founder & CTO, VibeMind - a voice-first agentic OS for non-technical founders. Agents that do the work, not describe it.","2026-11-12 01:01:00",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":53},[64,67,70],{"tool":65,"command":66},"npx","npx skills add Flissel\u002Fvibemind-os --skill devops-ensemble-solving",{"tool":68,"command":69},"bunx","bunx skills add Flissel\u002Fvibemind-os --skill devops-ensemble-solving",{"tool":71,"command":72},"pnpm","pnpm dlx skills add Flissel\u002Fvibemind-os --skill devops-ensemble-solving","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fskills\u002Fdevops\u002Fensemble-solving\u002FSKILL.md",[],[76,84,91,119,127,141],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":40},"01M6JAA67M92TRE7GWDJDBTA9T","review","Review a change.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Frowboat\u002Frowboat\u002Fpackages\u002Fopenai-plugin-runtime\u002Ftest\u002Ffixtures\u002Fcomplete-plugin\u002Fskills\u002Freview\u002FSKILL.md",[],[78,83],"change",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":40},"01M6JAA3DZR55G8ZY493BE9NBB","triage","Triage a change.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Frowboat\u002Frowboat\u002Fpackages\u002Fopenai-plugin-runtime\u002Ftest\u002Ffixtures\u002Fcomplete-plugin\u002Fskills\u002Fgroup\u002Ftriage\u002FSKILL.md",[],[86,83],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":40},"01M6JA9XPVHENK0FQN7HBK54NV","zentrale-werkzeuge","Werkzeuge der Zentrale – nutzen bei GitHub-Fragen (Projekte updaten, Repos, Issues, PRs, Commits, CI\u002FActions-Status, README), bei Fragen zum eigenen Gitea (Sicherung\u002FSpiegel, Repos, Issues, Commits), wenn neueste Docs\u002FDoku zu einer Bibliothek oder einem Dienst geholt werden sollen, wenn ein Dashboard aus meinen Daten gebaut werden soll und wenn ich sage 'auf meinem PC suchen' oder 'such auf dem Rechner nach …'.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Frowboat\u002Fdeploy\u002Fheadless\u002Fskills\u002Fzentrale-werkzeuge\u002FSKILL.md",[],[98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"zentrale werkzeuge","grep","file","README","list","fetch","todo","gitea","add","URL","mkdir","prs","commits","ci","actions","issues","status","repos","dashboard","github","docs",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":40},"01M6JA9SQPX187CVC148SQT1SP","wissen-suchen","Bedeutungssuche im Rowboat-Wissen – IMMER zuerst nutzen, wenn nach Kunden, Kontakten, Themen, Interessen, Notizen oder 'was wissen wir über …' gefragt wird, besonders wenn die genauen Wörter unklar sind.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Frowboat\u002Fdeploy\u002Fheadless\u002Fskills\u002Fwissen-suchen\u002FSKILL.md",[],[126],"wissen suchen",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":40},"01M6JA9P6GNFPE21101SDZS3BT","reel-aus-material","Reel aus vorhandenen Laura-Videos: passende Stellen im Transkript finden; spricht dort eine Person, bleibt ihr Originalton (mit Untertiteln aus dem Transkript), sonst trägt ein eingesprochener Satz den Clip. Bei Aufträgen der Art 'material'.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Fmarketing\u002Fvideo_claw\u002Fskills\u002Freel-aus-material\u002FSKILL.md",[],[134,135,136,137,138,139,140],"material","reel","reel aus material","person","videos","Art","clip",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":40},"01M6JA9KSATRT42ACWT66514ZP","reel-aus-bildern","Reel ohne Filmmaterial: Titelkarte, 3–5 Markenbilder mit wechselnder Bewegung, Schlusskarte mit Handlung; Farben und Logo der Firma. Bei Aufträgen der Art 'bilder'.","https:\u002F\u002Fgithub.com\u002FFlissel\u002Fvibemind-os\u002Fblob\u002Fmaster\u002Fspaces\u002Fmarketing\u002Fvideo_claw\u002Fskills\u002Freel-aus-bildern\u002FSKILL.md",[],[135,148,149,139],"reel aus bildern","logo"]