agentleFS
Sign inStart free
niksavisniksavis/basicly/.claude/skills/council/SKILL.md

council

Skill2 starsChanged 7 days agoMITView on GitHub

Decides one closed question by independent votes of fresh agents with different stances, and reports the majority with the dissent. Use when asked to let a council, a panel or several agents vote on a choice.

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

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

  • 0

    Common

    Most of the 128 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Vote: Run the swarm steps Brief, Launch and Collect.

    line 17
  2. Very specific:

    Verify: When the winning reason rests on a number or a root cause, run falsify-first on it with an agent that did not vote.

    line 25
  3. Distinctive:

    When the options turn out wrong, change the question and vote again with fresh agents.

    line 31

“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
<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. -->

Council

Decide one closed question by independent votes. This skill uses the swarm steps; read that skill first.

The script is ${CLAUDE_SKILL_DIR}/../swarm/scripts/swarm.py, in the swarm skill folder beside this one. DIR is a new folder per council in the session scratchpad.

Steps

  1. Ask one question. Write the decision, 2 to 4 option labels and the facts with sources, as the question guide says. For an open question, run swarm on the goal with the lenses feasibility, spec and simplicity, and take its numbered decisions as the 2 to 4 labels. A closed question with no labels: ask the user for them.
  2. Pick voters. Choose 3 stances from stances, one voter each. Choose 5 when the decision is hard to undo.
  3. Vote. Run the swarm steps Brief, Launch and Collect; the tally replaces the swarm Check. Each brief carries the question, the exact labels and the stance as its lens. No voter sees another vote. Rerun once each voter that is not run.

  4. Tally. Run:

    python3 -B ${CLAUDE_SKILL_DIR}/../swarm/scripts/swarm.py tally --voters user,safety,skeptic --options per-event,shards --dir DIR

    Replace the voters, options and folder with yours. Exit 0 prints the decision and each dissenting vote with its reason. Exit 2 means no option has a majority of all voters; the user decides.

  5. Verify. When the winning reason rests on a number or a root cause, run falsify-first on it with an agent that did not vote.
  6. Report. Give the vote table, the decision, the strongest dissent, each voter that is not run, and how the decision can fail. State that each voter voted blind, without seeing another vote.

Rules

  • A vote that is not run or names an unknown label counts against every option; the script takes 3 or 5 voters and refuses any other count or a repeated label.
  • When the options turn out wrong, change the question and vote again with fresh agents.

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.

Check your setup, free