agentleFS
ghvinashvilighvinashvili/specagent/.claude/skills/council/SKILL.md

council

Skill7 starsChanged 16 days agoApache-2.0View on GitHub

Convene five independent advisors, a blind peer review and one verdict on a framed decision. Use for high-stakes, uncertain choices.

166 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, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 149 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the verdict gate passed, point the human to stages/verdict/output/verdict.md.

    line 14
  2. Distinctive:

    Never summarise the verdict from memory, never add your own position and never tell an advisor what another advisor wrote.

    line 16

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

Convene a council

Argument: $0 = slug of the decision.

  1. Check the three conditions before anything is launched. If the question has an answer in the repository or its documents, answer it or run a stage for it. If it is creative work, or the human has already decided, say that a council does not fit and stop.
  2. Ask the human at most one clarifying question. Then write <runs root>/_briefs/$0.md from templates/project-brief.md: the goal is the decision in neutral wording with no preferred option; the material is paths; the constraints name the perspectives (default: contrarian, first principles, expansionist, outsider, executor) and the cost (eight sessions). The human confirms the brief.
  3. uv run harness run --slug $0 --brief <runs root>/_briefs/$0.md --pipeline council, then launch frame with the run-stage skill and continue as docs/roles/MANAGER.md describes: advise (one shard per perspective), review, verdict.
  4. When the verdict gate passed, point the human to stages/verdict/output/verdict.md. The decision is theirs; harness approve records it.

Never summarise the verdict from memory, never add your own position and never tell an advisor what another advisor wrote.

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.