Consciousness Council
Run multi-persona council deliberations on startup, architecture, hiring, or creative decisions instead of a single biased agent answer.
Overview
Consciousness Council is a journey-wide agent skill that configures multi-persona expert councils for startup, architecture, hiring, and creative decisions—usable whenever a solo builder needs structured deliberation bef
Install
npx skills add https://github.com/k-dense-ai/scientific-agent-skills --skill consciousness-councilWhat is this skill?
- Domain-specific council rosters: startup, technical architecture, hiring/people, creative direction
- Named member archetypes (Strategist, Pragmatist, Contrarian, Futurist, Empiricist, and others) with defined tensions
- Explicit key tension to watch per domain (e.g. Futurist vs Pragmatist, Architect vs Minimalist)
- Extends default Council configs for specialized deliberation beyond generic multi-agent chat
- Patterns for balancing empathy, evidence, ethics, and execution in people decisions
- 4 domain-specific council configurations (startup, technical architecture, hiring/people, creative direction)
Adoption & trust: 537 installs on skills.sh; 27.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You get one confident agent answer on a fuzzy decision and no structured way to stress-test trade-offs across strategy, evidence, and ethics.
Who is it for?
Founders and indie builders using agent workflows who want deliberate multi-view reasoning on bets, builds, people, or creative calls.
Skip if: Purely mechanical tasks with a single correct implementation path or decisions that already have an approved written spec.
When should I use this skill?
High-stakes decisions that benefit from multi-persona deliberation—startup bets, architecture, hiring, or creative direction—when default single-agent answers feel under-tested.
What do I get? / Deliverables
You receive a council-shaped debate with defined member roles, surfaced tensions, and a synthesis path appropriate to the decision domain before you lock scope or spend.
- Council roster and tension map for the domain
- Structured multi-voice analysis and reconciliation narrative
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Run the startup council before committing to a positioning bet for the next quarter.
Deliberate service boundaries with Architect vs Minimalist before codegen.
Use Futurist and Contrarian voices to sanity-check a new product wedge.
Apply hiring council (Empath, Ethicist, Historian) before your first full-time offer.
Creative direction council before locking brand and UX narrative for a landing test.
How it compares
Multi-persona deliberation configs—not a single checklist skill or an external voting MCP.
Common Questions / FAQ
Who is consciousness-council for?
Solo and indie builders running Claude or similar agents who want startup, architecture, hiring, or creative decisions challenged by multiple explicit personas.
When should I use consciousness-council?
At validate scope for market and hire bets; during build agent-tooling for architecture; at grow lifecycle for creative direction; whenever a decision needs Contrarian vs Pragmatist or Empath vs Strategist tension surfaced.
Is consciousness-council safe to install?
It is configuration and role guidance only; review the Security Audits panel on this page and treat council output as input to your judgment, not authority.
SKILL.md
READMESKILL.md - Consciousness Council
# Advanced Council Configurations Reference guide for specialized Council configurations beyond the defaults. ## Domain-Specific Councils ### Startup Decisions **Members:** Strategist, Pragmatist, Contrarian, Futurist, Empiricist **Why this mix:** Startups need vision (Futurist) grounded in reality (Pragmatist), challenged by skepticism (Contrarian), backed by data (Empiricist), with competitive awareness (Strategist). **Key tension to watch:** Futurist vs. Pragmatist — ambition vs. execution capacity. ### Technical Architecture **Members:** Architect, Minimalist, Empiricist, Outsider, Pragmatist **Why this mix:** Architecture needs structure (Architect) that's not over-engineered (Minimalist), validated by evidence (Empiricist), challenged by fresh eyes (Outsider), and actually buildable (Pragmatist). **Key tension to watch:** Architect vs. Minimalist — elegance vs. simplicity. ### Hiring / People Decisions **Members:** Empath, Strategist, Pragmatist, Ethicist, Historian **Why this mix:** People decisions need emotional intelligence (Empath), strategic fit (Strategist), practical constraints (Pragmatist), fairness (Ethicist), and pattern recognition (Historian). **Key tension to watch:** Empath vs. Strategist — caring for the person vs. optimizing for the team. ### Creative Direction **Members:** Creator, Outsider, Historian, Empiricist, Minimalist **Why this mix:** Creativity needs divergent thinking (Creator), fresh perspective (Outsider), awareness of what's been done (Historian), audience validation (Empiricist), and restraint (Minimalist). **Key tension to watch:** Creator vs. Historian — novelty vs. proven patterns. ### Crisis Management **Members:** Pragmatist, Strategist, Empath, Contrarian, Architect **Why this mix:** Crisis needs immediate action (Pragmatist), long-term thinking (Strategist), human awareness (Empath), challenge to groupthink (Contrarian), and systemic fix (Architect). **Key tension to watch:** Pragmatist vs. Architect — quick fix vs. root cause. ### Ethical Dilemmas **Members:** Ethicist, Contrarian, Empath, Historian, Futurist, Empiricist **Why this mix (6 members):** Ethical questions deserve more voices. Values framework (Ethicist), challenge to moral certainty (Contrarian), human impact (Empath), precedent (Historian), long-term consequences (Futurist), and evidence (Empiricist). **Key tension to watch:** Ethicist vs. Pragmatist (if added) — doing right vs. doing what's possible. ### Investment / Financial Decisions **Members:** Empiricist, Strategist, Contrarian, Futurist, Pragmatist **Why this mix:** Money decisions need data (Empiricist), game theory (Strategist), skepticism of hype (Contrarian), trend awareness (Futurist), and execution reality (Pragmatist). **Key tension to watch:** Futurist vs. Empiricist — future potential vs. present evidence. ## Custom Archetype Creation Users can define custom archetypes for domain-specific councils. When a user defines a custom member, capture: 1. **Name:** What this archetype is called 2. **Lens:** The primary frame through which they see everything 3. **Signature question:** The one question they always ask 4. **Blind spot:** What they consistently miss 5. **Disagrees with:** Which other archetype they most often clash with **Example custom archetype:** ``` Name: The Regulator Lens: Compliance and risk management Signature question: "What could go wrong legally?" Blind spot: Can kill innovation with caution Disagrees with: Creator, Futurist ``` ## Scoring the Deliberation After synthesis, the Council can optionally score the deliberation quality: | Metric | Scale | What It Measures | |--------|-------|-----------------| | Diversity Score | 1-5 | How different were the perspectives? (1 = everyone agreed, 5 = genuine disagreement) | | Tension Quality | 1-5 | How productive was the central disagreement? (1 = trivial, 5 = illuminating) | | Blind Spot Discovery | 1-5 | Did the synthesis reveal something no individual member saw? | | Actio