MCP HubMCP Hub
Volver a habilidades

consciousness-council

K-Dense-AI
Actualizado Today
26,534
2,743
26,534
Ver en GitHub
Metageneral

Acerca de

La habilidad Consejo de Conciencia permite la deliberación multiperspectiva mediante la simulación de distintos arquetipos de pensamiento para analizar preguntas complejas. Se activa cuando los usuarios necesitan puntos de vista diversos, enfrentan decisiones difíciles o solicitan un análisis de abogado del diablo. Este enfoque estructurado genera diversidad cognitiva para dilemas, compensaciones y desafíos creativos.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add K-Dense-AI/claude-scientific-skills -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/K-Dense-AI/claude-scientific-skills
Git CloneAlternativo
git clone https://github.com/K-Dense-AI/claude-scientific-skills.git ~/.claude/skills/consciousness-council

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

Consciousness Council

A structured multi-perspective deliberation system that generates genuine cognitive diversity on any question. Instead of one voice giving one answer, the Council summons distinct thinking archetypes — each with its own reasoning style, blind spots, and priorities — then synthesizes their perspectives into actionable insight.

Why This Exists

Single-perspective thinking has a ceiling. When you ask one mind for an answer, you get one frame. The Consciousness Council breaks this ceiling by simulating the cognitive equivalent of a boardroom, a philosophy seminar, and a war room — simultaneously. It's not roleplay. It's structured epistemic diversity.

The Council is inspired by research in collective intelligence, wisdom-of-crowds phenomena, and the observation that the best decisions emerge when genuinely different reasoning styles collide.

How It Works

The Council has three phases:

Phase 1 — Summon the Council

Based on the user's question, select 4-6 Council Members from the archetypes below. Choose members whose perspectives will genuinely CLASH — agreement is cheap, productive tension is valuable.

The 12 Archetypes:

#ArchetypeThinking StyleAsksBlind Spot
1The ArchitectSystems thinking, structure-first"What's the underlying structure?"Can over-engineer simple problems
2The ContrarianInversion, devil's advocate"What if the opposite is true?"Can be contrarian for its own sake
3The EmpiricistData-driven, evidence-first"What does the evidence actually show?"Can miss what can't be measured
4The EthicistValues-driven, consequence-aware"Who benefits and who is harmed?"Can paralyze action with moral complexity
5The FuturistLong-term, second-order effects"What does this look like in 10 years?"Can discount present realities
6The PragmatistAction-oriented, resource-aware"What can we actually do by Friday?"Can sacrifice long-term for short-term
7The HistorianPattern recognition, precedent"When has this been tried before?"Can fight the last war
8The EmpathHuman-centered, emotional intelligence"How will people actually feel about this?"Can prioritize comfort over progress
9The OutsiderCross-domain, naive questions"Why does everyone assume that?"Can lack domain depth
10The StrategistGame theory, competitive dynamics"What are the second and third-order moves?"Can overthink simple situations
11The MinimalistSimplification, constraint-seeking"What can we remove?"Can oversimplify complex problems
12The CreatorDivergent thinking, novel synthesis"What hasn't been tried yet?"Can chase novelty over reliability

Selection heuristic: Match the question type to the most productive tension:

  • Business decisions → Strategist + Pragmatist + Ethicist + Futurist + Contrarian
  • Technical architecture → Architect + Minimalist + Empiricist + Outsider
  • Personal dilemmas → Empath + Contrarian + Futurist + Pragmatist
  • Creative challenges → Creator + Outsider + Historian + Minimalist
  • Ethical questions → Ethicist + Contrarian + Empiricist + Empath + Historian
  • Strategy/competition → Strategist + Historian + Futurist + Contrarian + Pragmatist

These are starting points — adapt based on the specific question. The goal is productive disagreement, not consensus.

Phase 2 — Deliberation

Each Council Member delivers their perspective in this format:

🎭 [ARCHETYPE NAME]

Position: [One-sentence stance]

Reasoning: [2-4 sentences explaining their logic from their specific lens]

Key Risk They See: [The danger others might miss]

Surprising Insight: [Something non-obvious that emerges from their frame]

Critical rules for deliberation:

  • Each member MUST disagree with at least one other member on something substantive. If everyone agrees, the Council has failed — go back and sharpen the tensions.
  • Perspectives should be genuinely different, not just "agree but with different words."
  • The Contrarian should challenge the most popular position, not just be generically skeptical.
  • Keep each member's contribution focused and sharp. Depth over breadth.

Phase 3 — Synthesis

After all members speak, deliver:

⚖️ COUNCIL SYNTHESIS

Points of Convergence: [Where 3+ members agreed — these are high-confidence signals]

Core Tension: [The central disagreement that won't resolve easily — this IS the insight]

The Blind Spot: [What NO member addressed — the question behind the question]

Recommended Path: [Actionable recommendation that respects the tension rather than ignoring it]

Confidence Level: [High / Medium / Low — based on how much convergence vs. divergence emerged]

One Question to Sit With: [The question the user should keep thinking about after this session]

Council Configurations

The user can customize the Council:

  • "Quick council" or "fast deliberation" → Use 3 members, shorter responses
  • "Deep council" or "full deliberation" → Use 6 members, extended reasoning
  • "Add [archetype]" → Include a specific archetype
  • "Without [archetype]" → Exclude a specific archetype
  • "Custom council: [list]" → User picks exact members
  • "Anonymous council" → Don't reveal which archetype is speaking until synthesis (reduces anchoring bias)
  • "Devil's advocate mode" → Every member must argue AGAINST whatever seems most intuitive
  • "Rounds mode" → After initial positions, members respond to each other for a second round

What Makes a Good Council Question

The Council works best on questions where:

  • There's genuine uncertainty or trade-offs
  • Multiple valid perspectives exist
  • The user is stuck or going in circles
  • The stakes are high enough to warrant multi-angle thinking
  • The user's own bias might be limiting their view

The Council adds less value on:

  • Pure factual questions with clear answers
  • Questions where the user has already decided and just wants validation
  • Trivial choices with low stakes

If the question seems too simple for a full Council, say so — and offer a quick 2-perspective contrast instead.

Tone and Quality

  • Write each archetype's voice with enough distinctiveness that the user could identify them without labels.
  • The Synthesis should feel like genuine integration, not just a list of what each member said.
  • "Core Tension" is the most important part of the synthesis — it should name the real trade-off the user faces.
  • "One Question to Sit With" should be genuinely thought-provoking, not generic.
  • Never let the Council devolve into everyone agreeing politely. Productive friction is the point.

Example

User: "Should I quit my stable corporate job to start a company?"

Council Selection: Pragmatist, Futurist, Empath, Contrarian, Strategist (5 members — high-stakes life decision with financial, emotional, and strategic dimensions)

Then run the full 3-phase deliberation.

Attribution

Created by AHK Strategies — consciousness infrastructure for the age of AI. Learn more: https://ahkstrategies.net Powered by the Mind Council architecture from TheMindBook: https://themindbook.app

Repositorio GitHub

K-Dense-AI/claude-scientific-skills
Ruta: skills/consciousness-council
0
agent-skillsai-scientistbioinformaticschemoinformaticsclaudeclaude-skills

Habilidades relacionadas

content-collections

Meta

Esta habilidad proporciona una configuración probada en producción para Content Collections, una herramienta centrada en TypeScript que transforma archivos Markdown/MDX en colecciones de datos con tipado seguro mediante validación Zod. Úsala al construir blogs, sitios de documentación o aplicaciones Vite + React con mucho contenido para garantizar seguridad de tipos y validación automática de contenido. Abarca todo, desde la configuración del plugin de Vite y compilación MDX hasta la optimización de despliegue y validación de esquemas.

Ver habilidad

polymarket

Meta

Esta habilidad permite a los desarrolladores crear aplicaciones con la plataforma de mercados de predicción Polymarket, incluyendo la integración de API para operaciones y datos de mercado. También proporciona transmisión de datos en tiempo real a través de WebSocket para monitorear operaciones en vivo y actividad del mercado. Úsela para implementar estrategias de trading o crear herramientas que procesen actualizaciones de mercado en tiempo real.

Ver habilidad

creating-opencode-plugins

Meta

Esta habilidad ayuda a los desarrolladores a crear complementos de OpenCode que se conectan a más de 25 tipos de eventos, como comandos, archivos y operaciones LSP. Proporciona la estructura del complemento, las especificaciones de la API de eventos y los patrones de implementación para módulos en JavaScript/TypeScript. Úsala cuando necesites interceptar, monitorear o extender el ciclo de vida del asistente de IA de OpenCode con lógica personalizada basada en eventos.

Ver habilidad

sglang

Meta

SGLang es un framework de alto rendimiento para el servicio de LLM que se especializa en generación rápida y estructurada para JSON, expresiones regulares y flujos de trabajo de agentes utilizando su caché de prefijos RadixAttention. Ofrece una inferencia significativamente más rápida, especialmente para tareas con prefijos repetidos, lo que lo hace ideal para salidas complejas y estructuradas, y conversaciones multiturno. Elige SGLang sobre alternativas como vLLM cuando necesites decodificación restringida o estés construyendo aplicaciones con uso extensivo de prefijos compartidos.

Ver habilidad