skill-council
- Repo stars 3,406
- Author updated Live
- Author repo claude-octopus
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @nyldn · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skill-council
description: Run a configurable multi-LLM council with personas, budget caps, synthesis, veto gates, and opti…
category: ai
runtime: no special runtime
---
# skill-council output preview
## PART A: Task fit
- Use case: Run a configurable multi-LLM council with personas, budget caps, synthesis, veto gates, and optional implementation handoff. Use this skill for /octo:council and council-style requests. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Phase 0: Preflight / Quorum / Council Procedure” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Run a configurable multi-LLM council with personas, budget caps, synthesis, veto gates, and optional implementation handoff. Use this skill for /octo:council and council-style requests. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Phase 0: Preflight / Quorum / Council Procedure” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/octo`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Phase 0: Preflight / Quorum / Council Procedure”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-council
description: Run a configurable multi-LLM council with personas, budget caps, synthesis, veto gates, and opti…
category: ai
source: nyldn/claude-octopus
---
# skill-council
## When to use
- Run a configurable multi-LLM council with personas, budget caps, synthesis, veto gates, and optional implementation ha…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Phase 0: Preflight / Quorum / Council Procedure” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-council" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Phase 0: Preflight / Quorum / Council Procedure
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Council
Use this skill for /octo:council and council-style requests.
Phase 0: Preflight
Collect or infer:
- goal:
advice,decision,plan,implement, orreview - domain:
auto,architecture,product,security,business,research, ordocs - style:
balanced,adversarial,implementation,executive, orred-team - depth:
quick,standard, ordeep - members:
auto,3,5, or7 - budget cap in USD
- providers and provider availability
- pinned personas
- implementation permission and worktree isolation
Show the selected council, provider availability, benchmark freshness, quorum requirement, and cost estimate before provider fanout. Re-check the budget before critique, revision, synthesis, and implementation planning so the run stops before the next phase would exceed --max-cost. If the run is a dry run, stop after this preflight and write summary.json.
Quorum
- quick requires at least one non-chair response plus a synthesis-capable chair
- standard and deep require at least two non-chair responses plus a synthesis-capable chair
- if the chair fails, retry once with the highest-scoring synthesis-capable fallback
- if quorum is lost, stop by default and present partial artifacts instead of pretending consensus exists
Council Procedure
- Independent advice: ask each selected persona for recommendation, assumptions, risks, implementation notes, and confidence.
- Cross-critique: for standard/deep runs, semi-anonymize responses and ask members to critique gaps, assumptions, and risks.
- Revision: for deep runs or high disagreement, let members revise their positions after critique.
- Chair synthesis: produce agreement, disagreement, minority reports, risk register, implementation path, confidence, and conditions that would change the recommendation.
- Ratify / veto: verifier, red-team, security, legal, finance, and medical roles can veto implementation for critical risks.
Implementation Gates
- Gate A: user accepts the council synthesis or asks for revision.
- Gate B: user accepts the concrete implementation plan generated from the synthesis.
- Gate C: execution proceeds through existing Octopus implementation safety behavior. This is a one-shot authorization for the accepted plan, not per-file approval, unless existing safety hooks detect destructive or risky actions.
Never implement from council output without explicit approval. Preserve disagreement, summarize risks, and keep vetoes visible in the final answer and artifacts.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review