agentleFS
rmarjirmarji/chiron-council/skills/council/SKILL.md

council

Skill1 starsChanged 23 days agoMITView on GitHub

Convene a Chiron bench. Seats answer independently, only disagreements that are on the record are surfaced, and one recommendation keeps the dissent. Use when the user says "council", "run this by my bench", "convene", or names a bench such as money, strategy, deals, relationship, shipping, or work-design.

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

Files
SKILL.md

Convene a council

ChatGPT and Codex have no /chiron slash commands. This skill is that council flow.

The plugin root is the directory that contains skills/ and scripts/. Follow commands/council.md there, exactly, including the isolation rule and the sequential fallback when subagents are unavailable. Wherever that file says ${CLAUDE_PLUGIN_ROOT}, use the plugin root. Run each python3 invocation as its own command. Do not wrap it in a shell substitution or chain it with ;.

Seat text lives in skills/<id>/SKILL.md and that seat's references/ and disagreements.md. Read those files. Do not copy a seat into this skill, and do not invent a seat that is not installed. With no benches file of the user's own, python3 <plugin-root>/scripts/benches.py resolves the bundled examples (money, strategy, deals, relationship, shipping, work-design).

User data stays in ~/.chiron (CHIRON_HOME overrides that directory). Logs, benches, and seats Chiron creates go there, through python3 <plugin-root>/scripts/memory.py and python3 <plugin-root>/scripts/benches.py. Never write under ~/.claude. A path under ~/.claude is legacy and read-only. Pass --home .chiron only when the host cannot write the home directory (Cowork).

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.