council SKILL.md skillA
council from zhiming-dev/roster is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zhiming-dev/roster/council@git:20260607.31b1c63Pins git:20260607.31b1c63 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zhiming-dev/roster
- Path
shared/council/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260607.31b1c63, committed Jun 7, 2026
- Size
- 6,124 bytes
- Repository stars
- 12
- License
- MIT
Run a cross-model deliberation: pose the same question to multiple model bindings (e.g. Claude, GPT, Gemini), have them propose independently, then critique each other, then synthesize — with explicit anti-conformity safeguards. Use ONLY for high-uncertainty / high-stakes decisions; not for every step.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Council Skill — Cross-Model Deliberation Formalizes the intuition that asking several models the same hard question — and having them argue — tends to produce a stronger answer than any one alone. Used selectively by the planner when a decision is high-uncertainty, high-stakes, or contested by sub-agents. ## When to use (and when NOT to) ✅ Use when: - The decision is **high-stakes** (will gate a T3/T4 action) and the planner is uncertain. - Two sub-agents have returned **contradictory** results on overlapping work. - The task is **ambiguous** and the planner cannot pick between several reasonable decompositions. - A research condition is **C5** (HITL + Council enabled). ❌ Do **not** use when: - The decision is routine and a single capable model handles it (Council multiplies cost). - The task is **strictly sequential** with no real branching choice (debate adds latency, not value). - You are tempted to use it as a confidence-boosting ritual on every step — that is the failure mode the literature warns about (see [`conclave-spec.md` §10](../../conclave-spec.md)). The planner's invocation policy: …
Read the whole file at its exact version.
How to install
mdr add zhiming-dev/roster/council@sha256:35383d4660d878a8The line at the top of this page pins the label git:20260607.31b1c63, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3mfps66u74lbfhio)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 7, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6124 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
zhiming-dev/roster · 12 stars · license MIT · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3mfps66u74lbfhio GET https://markdownregistry.com/api/v1/resolve?ref=zhiming-dev/roster/council GET https://markdownregistry.com/api/v1/blob/35383d4660d878a83abe4bac6f644f99f06d7dfba58f7d1419f700a2710325d4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from zhiming-dev/roster
Every file in zhiming-dev/roster