council-review
Skill708 starsChanged 5 months agoMITView on GitHub
Multi-model validation council — auto-validate plans, architecture changes, and PRs via validate-plan/review before executing
11 other projects use a version of this.
Adopted by
Most recently taken up by
- babs/skillstheir own version, first seen Nov 8, 2026
- ngmeyer/skillstheir own version, first seen Nov 1, 2026
- microsoft/vscode-team-kittheir own version, first seen Oct 27, 2026
- jaydenluckertjes-ai/Carmack-Counciltheir own version, first seen Oct 13, 2026
- joymin5655/Agenttheir own version, first seen Sep 28, 2026
- cochinescu/decent-skillstheir own version, first seen Sep 20, 2026
Other versions11 projects use a version of this.
Word for word · 1
- alinaqi/maggy★ 711100% same
Edited · 0
None found.
Wrote their own version · 10
- microsoft/vscode-team-kit★ 65same name
- SamJHudson01/Carmack-Council★ 52same name
- amiable-dev/llm-council★ 43same name
- cochinescu/decent-skills★ 8same name
- babs/skills★ 4same name
- ngmeyer/skills★ 4same name
- jaydenluckertjes-ai/Carmack-Council★ 2same name
- joymin5655/Agent★ 2same name
- mohamedaeldin/claude-code-setup★ 1same name
- nemock/council-review★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository75 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- aeo-optimizationSkill
- agentic-developmentSkill
- agent-teamsSkill
- ai-modelsSkill
- android-javaSkill
- android-kotlinSkill
- autonomous-testingSkill
- aws-auroraSkill
- aws-dynamodbSkill
- azure-cosmosdbSkill
- baseSkill
- build-in-publicSkill
- cloudflare-d1Skill
- code-deduplicationSkill
- code-graphSkill
- code-reviewSkill
- codex-reviewSkill
- commit-hygieneSkill
- context-shuntSkill
- cpg-analysisSkill
- credentialsSkill
- cross-agent-delegationSkill
- database-schemaSkill
- dataforseoSkill
- demo-videoSkill
- existing-repoSkill
- external-model-delegationSkill
- firebaseSkill
- flutterSkill
- gemini-reviewSkill
- icpgSkill
- iterative-developmentSkill
- klaviyoSkill
- llm-patternsSkill
- maggySkill
- medusaSkill
- mnemosSkill
- model-routingSkill
- ms-teams-appsSkill
- nodejs-backendSkill
- playwright-testingSkill
- polyphonySkill
- posthog-analyticsSkill
- project-toolingSkill
- pwa-developmentSkill
- pythonSkill
- react-nativeSkill
- react-webSkill
- reddit-adsSkill
- reddit-apiSkill
- security-auditSkill
- securitySkill
- session-managementSkill
- shopify-appsSkill
- site-architectureSkill
- supabase-nextjsSkill
- supabase-nodeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
When you write a plan to ~/.claude/plans/, automatically validate it:
- Distinctive: line 24
When making architectural changes (new services, API redesigns, database schema changes), run:
- Distinctive: line 30
Before marking a PR as done, run:
- Very specific: line 64
All 13 tiers are listed in ~/.claude/council.yaml under models:.
- Very specific: line 70
Use POST /api/models/health to verify all models are responding.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Council of Experts — Multi-Model Validation
When to Auto-Trigger
Plans (auto_validate_plans)
When you write a plan to ~/.claude/plans/, automatically validate it:
~/bin/validate-plan --threshold 2 ~/.claude/plans/<plan-file>.md- 2+ of 3 approve → execute immediately
- 1 of 3 → surface reviewer feedback to user before proceeding
- 0 of 3 → revise plan, re-validate
Architecture Decisions (auto_review_architecture)
When making architectural changes (new services, API redesigns, database schema changes), run:
~/bin/review --all "Review this architecture: <summary>"PR Review (auto_review_prs)
Before marking a PR as done, run:
~/bin/review --all --file <changed-files>Configuration
Council behavior is configured in ~/.claude/council.yaml. The Maggy dashboard (Settings > Council) also manages this config.
Chief of the Council
chief: claude-fable-5 — Claude Fable 5 (Anthropic's most capable widely-released
model, GA 2026-06-09) leads every panel as the chief: it reviews first and casts
the deciding synthesis. Invoked via ~/bin/claude-fable-5. Override the chief in
~/.claude/council.yaml.
Reviewer Contexts
The chief leads each context, followed by the panel:
| Context | Default Reviewers | When |
plan | Claude Fable 5 (chief), DeepSeek Pro, Codex, Gemini Pro | Before executing any plan |
review | Claude Fable 5 (chief), DeepSeek Pro, Kimi | Code review, PR review |
architecture | Claude Fable 5 (chief), DeepSeek Pro, Gemini Pro, Grok | System design, schema changes |
Threshold Rules
The threshold setting controls how many approvals are needed:
threshold: 2with 3 reviewers → need 2/3 to auto-execute- Clamped to [1, reviewer_count] — can't be 0 or exceed available reviewers
Model Inventory
All 13 tiers are listed in ~/.claude/council.yaml under models:. Each has:
id— unique identifiercmd— CLI command to invoke (null for Claude models, which are the host)tier— routing priority (0=cheapest, 12=most capable)label— human-readable name
Use POST /api/models/health to verify all models are responding.
How This Skill is Used
This skill is loaded by Claude Code on session start. It provides the behavioral rules for when to invoke multi-model validation. The actual execution happens via ~/bin/validate-plan and ~/bin/review which are already installed.
Do not skip council validation for CLAUDE-tier tasks. The whole point is that architecture and security decisions get independent verification before execution.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.