‹ 首页

ablation-brainstorm

@yogsoth-ai · 收录于 5 天前 · 上游提交 2 周前

Remove components one by one, observe system changes to reveal hidden dependencies and generate ideas from structural gaps.

适合你,如果需要在复杂系统中找出隐藏的依赖关系并优化结构

/ 通过 npx 安装 校验哈希
npx oh-my-skill add yogsoth-ai/de-anthropocentric-research-engine/ablation-brainstorm
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- yogsoth-ai/de-anthropocentric-research-engine/ablation-brainstorm
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify yogsoth-ai/de-anthropocentric-research-engine/ablation-brainstorm
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
388GitHub stars
~506上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 59ace64 · 表述以原文为准
它做什么

Claude会逐步移除系统组件,观察每次移除后的变化,从而发现组件间的依赖关系,并利用这些洞察生成新想法。

什么时候触发

当需要分析复杂系统的内部依赖关系,或者基于结构空白进行头脑风暴时。

装好后可以这样说
触发组件移除流程。
运行依赖识别。
合成分析报告。
技能原文 SKILL.md作者撰写 · Apache-2.0 · 59ace64

Ablation Brainstorm

Systematically remove components from a system one by one, observe what changes, and use the resulting insights to generate novel ideas.

State Ledger

| Resource | Target | Current | % | |----------|--------|---------|---| | web-search | 20 | 0 | 0% | | web-research | 5 | 0 | 0% | | paper-overview | 20 | 0 | 0% | | paper-search | 12 | 0 | 0% | | paper-research | 5 | 0 | 0% |

HARD-GATE

Cannot exit strategy until ≥80% of each budget line is consumed OR yield targets are met with justification for remaining budget.

Available Tactics

| Tactic | Role | |--------|------| | coverage-analysis | Ensure all components are ablated | | evaluation-filtering | Score and filter ablation-derived ideas |

Available SOPs

| SOP | Role | |-----|------| | ablation-execution | Remove components one by one, record responses | | dependency-identification | Extract dependency graph from ablation results | | enumeration-synthesis | Synthesize ablation insights into idea report |

Execution Guidance
  1. Decompose: List all components of the target system
  2. Ablate: Run ablation-execution — remove each component, record effects
  3. Analyze: Run dependency-identification to find critical dependencies
  4. Ideate: For each critical dependency, ask "what if this were replaced/eliminated/redesigned?"
  5. Filter: Apply evaluation-filtering to rank generated ideas
  6. Synthesize: Produce structured report via enumeration-synthesis

<!-- BEGIN available-tables (generated) -->

Available Tactics

Optional, no fixed order; the final leaf is always a sop.

| Tactic | When to use | | --- | --- | | coverage-analysis | Systematic coverage evaluation pipeline — benchmark inventory, method-problem crossing, and intersection evaluation to map explored vs unexplored solution space. |

Available SOPs

Optional, no fixed order; the final leaf is always a sop.

| SOP | When to use | | --- | --- | | ablation-execution | Remove components one by one from a system, record the response/impact of each removal. | | dependency-identification | Identify critical dependencies from ablation results, producing a dependency graph and highlighting critical components. | | enumeration-synthesis | Synthesize all systematic enumeration outputs into a structured idea report with prioritized recommendations. |

<!-- END available-tables (generated) -->

按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。