skill council

AI Community

Skill notes

Phase 0: Preflight

Collect or infer: goal: advice, decision, plan, implement, or review domain: auto, architecture, product, security, business, research, or docs style: balanced, adversarial, implementation, executive, or red-team depth: quick, standard, or deep

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.

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 0: Preflight

Collect or infer: goal: `advice`, `decision`, `plan`, `implement`, or `review` domain: `auto`, `architecture`, `product`, `security`, `business`, `research`, or `docs` style: `balanced`, `adversarial`, `implementation`, `executive`, or `red-team` depth: `quick`, `standard`, or `deep`

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.