agentleFS
Jawahars07Jawahars07/ballast/skills/council/SKILL.md

council

Skill1 starsChanged 2 months agoMITView on GitHub

Run a structured decision council across five perspectives - strategy, execution, finance, risk, and contrarian - then anonymise the outputs and synthesise them into a single verdict with consensus level, key tension, and flagged blind spots. Use for consequential decisions where one perspective is not enough.

143 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-payment-x402, motion-advanced and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TironFoxSkill

    agent-payment-x402

    Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.

    Also in 5 projects that use this

  • renepfSkill

    motion-advanced

    Advanced motion patterns for React / Next.js — drag & drop, gestures, text animations, SVG path drawing, custom hooks, imperative sequences (useAnimate), loaders, and the full API decision tree. Requires motion-foundations.

    Also in 4 projects that use this

  • RojiosSkill

    defi-amm-security

    Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math.

    Also in 6 projects that use this

  • scottwaterSkill

    modernize

    Rebase an aging PR onto its current base and decide whether it should be modernized, reworked, or closed. Use when asked to rebase, update, or modernize an old PR.

    Also in 7 projects that use this

  • RojiosSkill

    dart-flutter-patterns

    Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.

    Also in 5 projects that use this

  • scottwaterSkill

    leaving-pr-comments

    Format comments an agent posts on GitHub on the user's behalf. Use whenever leaving a PR comment, review comment, or reply.

    Also in 6 projects that use this

  • +1 more from scottwater
  • +1 more from Rojios

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 128 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    "Divided" is a real and useful outcome: Do not manufacture consensus that is not there.

    line 69
  2. Distinctive:

    Use the blind spot section as the reality check: If the contrarian read lands, reconsider — that section is the highest-value output and …

    line 84

“Common” is measured: kept by at least 6 in 10 of the 128 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Council

Five advisors evaluate your question independently and in parallel. Their outputs are stripped of identity and shuffled. An anonymous judge then synthesises them into one verdict.

The anonymisation is the point. A judge that knows which advisor said what will weight by persona rather than by argument.

Usage

/council "Should we launch in France before India?"
/council "What price point maximises adoption?"
/council --quick "Is this partnership worth pursuing?"

--quick runs three advisors instead of five (strategy, finance, risk). Use it when the decision is real but not existential.

The five advisors

AdvisorLensAsks
VishwamitraStrategyLong-range positioning, moats, what this makes possible in three years
ChanakyaExecutionTactical feasibility, stakeholder dynamics, resource reality
LakshmiFinanceUnit economics, ROI, pricing power, capital efficiency
KaliRiskDownside scenarios, failure modes, what kills this
NaradaContrarianBlind spots, the unfashionable read, what everyone in the room is missing

Each is spawned as a parallel subagent receiving the exact question, its persona brief, and one instruction: output a 150-word perspective, do not reference other advisors, do not identify yourself.

How to run it

  1. Spawn all advisors in parallel. Independence is the source of the signal — an advisor who has read another's output is no longer a second opinion.
  2. Anonymise before judging. Strip every identifier, relabel as "Advisor A", "Advisor B", and shuffle the order randomly.
  3. Judge the anonymised set. The judge receives the original question and the shuffled perspectives, and nothing else.

Output format

## Council Verdict

**Question:** [restated]
**Consensus:** Strong Proceed | Proceed with Caution | Divided | Do Not Proceed

### Where advisors agreed
- …

### Key tension
[The main disagreement, and what it implies for the decision]

### Blind spot flagged
[The most unexpected or contrarian point raised]

### Strategic next step
[One concrete action]

"Divided" is a real and useful outcome. Do not manufacture consensus that is not there. A council that always converges is not deliberating, and forcing agreement destroys exactly the information you convened it to get.

Reading the verdict

The council informs. It does not decide, and it does not override your judgement.

What it reliably surfaces:

  • Unstated assumptions in how the question was framed
  • Priorities that compete across domains, which one person rarely holds simultaneously
  • Risk scenarios that optimism skipped
  • Genuine consensus, where it exists

Use the blind spot section as the reality check. If the contrarian read lands, reconsider — that section is the highest-value output and the easiest to skim past.

Limits, stated honestly

  • Five perspectives from one model are five framings, not five independent minds. Correlated blind spots stay blind. This widens the aperture; it does not eliminate the shared bias.
  • The council is only as good as the question. A leading question produces a leading verdict. State the decision neutrally.
  • Everything stays local. Subagents only, no external services, and the full deliberation is visible in the transcript.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.