Multi-perspective deliberation using Agent Teams. Spawn 3-5 teammates with different viewpoints and optionally different models to debate decisions, evaluate specs, or explore trade-offs. Inspired by karpathy/llm-council.
Spawns a deliberation team with diverse perspectives to debate complex decisions and explore trade-offs.
npx claudepluginhub rbergman/dark-matter-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
When facing decisions where multiple valid perspectives exist, spawn a deliberation team rather than relying on a single viewpoint. Council is a premium tool — use it rarely, for decisions that warrant deep thought from multiple angles.
| Role | Purpose | Model |
|---|---|---|
| Advocate | Argues for the most promising approach | opus |
| Skeptic | Finds flaws, challenges assumptions | opus |
| Pragmatist | Focuses on practical constraints (time, complexity, maintenance) | opus |
| Domain Expert | Brings specialized knowledge relevant to the topic | opus |
| Lead (you) | Frames the question, moderates, synthesizes | opus |
3 perspectives minimum, 5 maximum. Tailor roles to the specific decision.
All councilors use opus for maximum depth of reasoning. The council is designed for quality over speed — if you need fast iteration, use dialectical-refinement instead.
Write the synthesis to history/ so it survives context loss:
# Ensure history/ exists and is gitignored
mkdir -p history
grep -qx 'history/' .gitignore 2>/dev/null || echo 'history/' >> .gitignore
File: history/council-<topic-slug>-<YYYY-MM-DD>.md
Contents: The full output format (see below) — question, perspectives, key debates, recommendation, dissenting views, confidence.
Why this is mandatory: Council deliberations are expensive (3-5 opus subagents). If the session runs out of context or crashes, the recommendation is lost and must be re-run. Writing to history/ makes recovery trivial — a fresh session reads the file and has the full council output.
Recovery: If a session finds history/council-*.md files, it can read them to recover prior deliberation results without re-running the council.
Council deliberations consume ~25-35k tokens of conversation history (subagent prompts + responses). If the session needs to act on the council's recommendation (implementation work), strongly recommend rotating first:
/rotate to snapshot the session/copy → /clear → paste snapshot into new sessionhistory/council-<topic>.md for the full recommendation (~2k tokens vs 25-35k in conversation)This prevents the #1 cause of council-related context overflow: running deliberation AND implementation in the same session.
Exception: If the council result is small and the follow-up work is trivial, skip the rotate.
Epistemic diversity comes from different analytical frames, not different models. All councilors run on opus for maximum reasoning depth. Diversity is achieved through:
Future option: cross-model councils (e.g., Codex, Gemini) via driver plugins could add genuine model diversity. Not yet implemented.
## Council Deliberation: [Topic]
### Question
[The specific question debated]
### Perspectives
- **[Role A]** ([model]): [1-2 sentence position summary]
- **[Role B]** ([model]): [1-2 sentence position summary]
- **[Role C]** ([model]): [1-2 sentence position summary]
### Key Debates
1. [Debate point] — [who argued what, resolution or ongoing disagreement]
2. [Debate point] — [...]
### Recommendation
[Lead's synthesized recommendation with reasoning]
### Dissenting Views
[Positions that lost but have merit — record for future reference]
### Confidence
[High/Medium/Low] — [why]
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.