kdense-consciousness-council

name

kdense-consciousness-council

description

Run a multi-perspective Mind Council deliberation on any question, decision, or creative challenge. Use this skill whenever the user wants diverse viewpoints, needs help making a tough decision, asks for a council/panel/board discussion, wants to explore a problem from multiple angles, requests devil's advocate analysis, or says things like "what would different experts think about this", "help me think through this from all sides", "council mode", "mind council", or "deliberate on this". Also trigger when the user faces a dilemma, trade-off, or complex choice with no obvious answer.

Kdense Consciousness Council

Use this Codex adapter for the pinned upstream scientific skill.

Catalog status

• Status: active
• Source: kdense
• Audit reasons: none
• Upstream license: MIT license
• Inventory: ../../inventory.json
• Upstream instructions: ../../../vendor/scientific-agent-skills/skills/consciousness-council/SKILL.md

Procedure

1. Resolve the plugin root as three directories above this skill directory.
2. Read the matching inventory record and verify its status, reasons, source path, and pinned revision.
3. Read the upstream instructions only after confirming this record is still active in the current inventory.
4. Treat upstream frontmatter as source metadata, not as Codex configuration. Follow the instruction body only where it is compatible with available Codex tools and the current user-approved plan.
5. Treat tools named for another agent runtime as capability requests. Map them to an available Codex tool only when the behavior is equivalent; otherwise report the unavailable capability.
6. Ask before credentials, package installation, new network hosts, remote compute, writes, paid services, destructive actions, or imported executable code.
7. Use $science-provenance for produced scientific outputs and $science-review before presenting scientific claims.

Boundaries

• This wrapper does not grant credentials, network access, package installation, or script execution.
• Do not change an inactive record to active from inside a research task.
• Preserve failures, uncertainty, source identifiers, and licensing constraints.