council-review
Multi-model validation council — auto-validate plans, architecture changes, and PRs via validate-plan/review before executing
What this skill does
# 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: ```bash ~/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: ```bash ~/bin/review --all "Review this architecture: <summary>" ``` ### PR Review (auto_review_prs) Before marking a PR as done, run: ```bash ~/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: 2` with 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 identifier - `cmd` — 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.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.