IA / Agents~83 · IA en attente
Council — A skill that helps you make decisions about your project
r/ClaudeCodeu/mattalicious29 septembre 2026
Analyse IA en cours de préparation : les informations ci-dessous proviennent de la détection automatique.
Résumé
Inspired by Karpathy's LLM Council, I wanted a faster, inline version I could use directly in Codex and Claude Code with the benefit of all my repo's context. So I made Council, a skill that works great in any harness that supports subagents. Council spawns multiple subagents (you can specify the model and effort) in…
Afficher le post originalMasquer le post original
Inspired by Karpathy's LLM Council, I wanted a faster, inline version I could use directly in Codex and Claude Code with the benefit of all my repo's context. So I made Council, a skill that works great in any harness that supports subagents.
Council spawns multiple subagents (you can specify the model and effort) in parallel, gives them each only the relevant decision and context to conduct research and weigh in on, then synthesizes their perspectives into a clear recommendation.
Here's some things I've used it for:
• Architectural decisions. Should I replace Recharge with another Shopify app to manage my subscriptions?
• Naming things. What should I label this parameter in the UX so that it's clear to users?
• Comparing things. Compare OpenClaw to OpenAI's new Agents API. What would be best to integrate into this project?
Great for validating or challenging assumptions or for getting direction when you're unsure on something. Helps mitigate confirmation bias from your main agent. Sometimes I don't agree with the Council and it brings me back to the drawing board. That kind of pushback helps make projects better.
Try it out and let me know what you think.
codex plugin marketplace add mattakins/council codex plugin add council@mattakins
Or if you prefer using Skills:
npx skills add mattakins/council -g
