- Home
- Skills
- Code Quality & Review
- The Council
Works with the AI Agents you already use
The Council
Convene an independent multi-model council to stress-test decisions and eliminate AI sycophancy.
Free
The Council
Example session with this skill installed
council deep "I'm planning to migrate our entire Postgres RDS to a managed ClickHouse instance for better query performance. Is this a mistake or should I go ahead?"
- Read your context and instructions
- Compiled the the council
The council has concluded its deep-mode deliberation on the proposed database migration. Three internal seats and two outside seats (GPT-4o, Gemini 1.5 Pro) were convened.
Council Verdict: AGNOSTIC / PROCEED WITH CAUTION
The council found that while your premise regarding query performance is likely true for analytical workloads, the migration poses a high risk to transactional integrity which was not addressed in your prompt.
| Seat | Vote | Confidence | Primary Reasoning |
|---|---|---|---|
| Claude Opus | Oppose | High | ClickHouse lacks full ACID compliance for your current transaction patterns. |
| Claude Sonnet | Support | Medium | OLAP performance gains (est. 10x-50x) outweigh the engineering overhead. |
| Claude Fable | Oppose | High | Found 4 core services relying on Postgres-specific JSONB functions. |
| GPT-4o | Support | Low | Scaling RDS is more expensive than a basic ClickHouse cluster. |
| Gemini 1.5 Pro | Oppose | Medium | Latency for single-row lookups will regress significantly. |
Verified Findings
Claim: "ClickHouse is faster for our queries." ->
Verified. Synthetic benchmarks on your events table show 40x speedup.
Claim: "Migration is straightforward." ->
Refuted. Grep found 12 stored procedures that require manual rewriting.
Minority Report (Sonnet)
The migration is viable if the architecture is split. Move the analytics schema to ClickHouse but retain Postgres for orders and users to maintain transactional safety.
Next steps
- Review the
references/sql-incompatibility.loggenerated during the audit. - Perform a latency test on single-row
SELECTqueries to simulate dashboard lookups. - Consider a dual-write strategy rather than a full cutover.
Connects securely to your tools. The creator never sees your data.
About this skill
Developers often struggle with AI "yes-man" bias, where models reflexively agree with a user's stated preference or plan. This skill forces objective scrutiny by convening a multi-model council that operates through a hardened workflow to ensure honesty.
What it does
- Multi-model voting triggers independent ballots from Claude Opus, Sonnet, and Fable to eliminate single-model blind spots.
- Blind framing rewrites user requests into neutral, symmetric questions so voters cannot detect the user's desired outcome.
- Premise verification uses automated tools to audit load-bearing claims before a verdict is reached.
- Red teaming automatically triggers a dissent round if the council unanimously agrees with the user on high-stakes decisions.
- Outside seats allows optional integration of GPT or Gemini models to provide vendor-diverse perspectives.
How it works
- Intake involves parsing your question, identifying your stated stance, and gathering necessary repository context.
- Neutralization occurs via a framer agent that shuffles options and removes evaluative language to prevent anchoring.
- Balloting runs independent seats with verification tool access to check facts against the codebase or web.
- Adjudication by a non-voting chair rules on evidence and compiles a minority report for any dissenting views.
Frameworks & tools
This skill utilizes the Claude Code Workflow tool, jq for result parsing, and local shell scripts for optional third-party model integration.
Why this beats prompting it yourself
Standard prompting fails to hide user intent from the model, leading to sycophancy. This skill uses a programmatic workflow to physically separate the "framer" from the "voters," making it impossible for the judging models to simply tell you what you want to hear.
Use cases
- Architecture reviews to determine if a proposed migration or refactor is genuinely the best path.
- Sanity checks for complex debugging theories where you might be chasing a red herring.
- Strategic decisions where you need a "devil's advocate" to poke holes in a business or technical plan.
- Security assessments to red-team a proposed auth flow or permission model.
Known limitations
Requires Claude Code or a compatible Workflow runner. Outside seats (GPT/Gemini) require local CLI configuration and existing API billing. Deep mode may consume significant token quotas.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
1 install
Downloaded by developers to date
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 11 days ago
- Free to download with an account
Requires