返回技能列表

coordinate-swarm

pjt222
更新于 2 days ago
5 次查看
17
2
17
在 GitHub 上查看
automationdesign

关于

The coordinate-swarm skill provides patterns like stigmergy and quorum sensing for building distributed systems that self-coordinate without central control. It helps developers design resilient, event-driven architectures by focusing on signal design, agent autonomy, and tuning emergent behavior. Use it when you need to eliminate coordination bottlenecks or replace fragile orchestration with decentralized coordination.

快速安装

Claude Code

推荐
主要方式
npx skills add pjt222/agent-almanac -a claude-code
插件命令备选方式
/plugin add https://github.com/pjt222/agent-almanac
Git 克隆备选方式
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/coordinate-swarm

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

Coordinate Swarm

Stigmergy + local rules + quorum → coherent collective, no central ctrl.

Use When

  • Distributed sys → no central bottleneck
  • Self-coord teams → no mgr overhead
  • Event-driven arch → shared state, not direct msg
  • Works @3 agents → breaks @30 → scale
  • Bootstrap new swarm domain (forage-resources, build-consensus)
  • Replace fragile central orch → resilient emergent

In

  • Required: Agents desc (workers, services, team)
  • Required: Collective goal / target behavior
  • Optional: Current coord + fail modes
  • Optional: Agent count → pattern choice
  • Optional: Latency tolerance (realtime vs eventual)
  • Optional: Env constraints (shared state, bandwidth)

Do

Step 1: Classify Problem

  1. Map: who agents, what do, where coord breaks
  2. Classify:
    • Foraging → search distributed res (forage-resources)
    • Consensus → agree collective decision (build-consensus)
    • Construction → build shared structure
    • Defense → detect threats (defend-colony)
    • Division of labor → self-organize roles
  3. Fail mode:
    • Single point fail (central ctrl)
    • Comm bottleneck (too many msg)
    • Coherence loss (drift, no feedback)
    • Rigidity (no adapt)

→ Clear class + fail mode → pattern choice.

If err: no single class → composite → decompose. Heterogeneous → layered coord (homogeneous clusters + inter-cluster stigmergy).

Step 2: Design Signals

Indirect comm channels.

  1. Shared env (DB, queue, FS, board)
  2. Signal types:
    • Trail: accumulate on success paths (ant pheromone)
    • Threshold: counter → behavior switch
    • Inhibition: repel from exhausted areas
  3. Props:
    • Decay: fade rate → no stale dominance
    • Reinforce: success strengthens
    • Radius: propagation range
  4. Signal → behavior map:
    • Signal X > T → action A
    • A done → deposit Y
    • No signal → default explore
Signal Design Template:
┌──────────────┬───────────────────┬──────────────┬────────────────────┐
│ Signal Name  │ Deposited When    │ Decay Rate   │ Agent Response     │
├──────────────┼───────────────────┼──────────────┼────────────────────┤
│ success-trail│ Task completed OK │ 50% per hour │ Follow toward      │
│ busy-marker  │ Agent starts task │ On completion│ Avoid / pick other │
│ help-signal  │ Agent stuck >5min │ 25% per hour │ Assist if nearby   │
│ danger-flag  │ Error detected    │ 10% per hour │ Retreat & report   │
└──────────────┴───────────────────┴──────────────┴────────────────────┘

→ Signal table: deposit conds + decay + responses. Simple + composable.

If err: too complex → 2 signals (attract/repel). Add nuance after basic works.

Step 3: Local Rules

Simple rules, local info only.

  1. Perception radius (what sense?)
  2. 3-7 rules, priority order:
    • Rule 1 (safety): danger-flag → flee
    • Rule 2 (response): help-signal + idle → move toward
    • Rule 3 (exploit): success-trail → follow strongest
    • Rule 4 (explore): no signal → random + unexplored bias
    • Rule 5 (deposit): task done → deposit success-trail
  3. Each rule:
    • Local: only what agent perceives
    • Simple: one if-then
    • Stateless (pref): no past mem
  4. Mental test → does collective behavior emerge?

→ Prioritized rules, independent exec → target behavior emerges.

If err: no emergence → feedback loop needed. Add signal for collective state + adjust rule.

Step 4: Quorum Thresholds

Trigger collective changes when enough agree.

  1. Collective decisions:
    • Explore → exploit mode
    • New worksite commit / abandon
    • Normal → emergency
  2. Per decision:
    • Threshold: # / % agents agreeing
    • Window: signal count period
    • Hysteresis: different on/off thresh → no osc
  3. Quorum = signal accumulation:
    • Fav agent → vote-signal
    • Votes > thresh in window → activate
    • Votes < deact thresh → reverse

→ Leaderless decisions. Hysteresis gap → no rapid osc.

If err: oscillation → widen hyst gap (70/30). Never reaches quorum → lower thresh / widen window. Too slow → shrink window (beware premature).

Step 5: Test + Tune

  1. Pilot 5-10 agents
  2. Observe:
    • Converges on behavior?
    • How long?
    • Conditions change mid-task → what?
    • Agents fail / added → what?
  3. Tune params:
    • Decay: fast → no memory; slow → stale dominates
    • Quorum: low → premature; high → paralysis
    • Explore/exploit balance: too explore → inefficient; too exploit → local optima
  4. Stress:
    • Remove 30% agents → recover?
    • Double count → still coord?
    • Conflict signals → resolve / deadlock?

→ Tuned params, self-organizes, recovers, scales.

If err: stress fails → too tightly coupled. Simplify: fewer signals, faster decay, robust default. Swarm w/ zero-signal default > signal-dependent swarm.

Check

  • Problem classified (foraging / consensus / construction / defense / labor)
  • Signal table: deposit + decay + response
  • Rules simple + local + prioritized (3-7)
  • Quorum w/ hysteresis → no osc
  • Small test → emergent behavior matches goal
  • Stress test → graceful degradation

Traps

  • Signal bloat: Too many types → confusion. Start 2 (attract/repel)
  • Fake local: Rule needs global state → not local. Refactor
  • No decay: Fossilized coord state. Half-life per task scale
  • Zero hysteresis: Rapid osc. Deact < act always
  • Homogeneity assumed: Diff caps → role-diff rules (scale-colony)

  • forage-resources — res search + explore-exploit
  • build-consensus — distrib agreement deep-dive
  • defend-colony — collective defense on signal framework
  • scale-colony — scaling past initial coord
  • adapt-architecture — morphic arch transform
  • deploy-to-kubernetes — distrib sys deploy
  • plan-capacity — capacity + swarm scaling
  • coordinate-reasoning — AI self-variant; stigmergy → ctx mgmt

GitHub 仓库

pjt222/agent-almanac
路径: i18n/caveman-ultra/skills/coordinate-swarm
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

相关推荐技能

content-collections

Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。

查看技能

polymarket

这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。

查看技能

creating-opencode-plugins

该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。

查看技能

sglang

SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。

查看技能