council-open

Create shared-state MAD.Council coordination channels with atomic initialization and preflight validation.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-open
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: council-open
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/council-open
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-open

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually setting up shared coordination channels for multi-agent teams is error-prone, inconsistent, and wastes time on repetitive filesystem setup and configuration. This Skill automates the entire channel creation workflow, ensuring consistent, governed, and schema-valid state every time.

Core Features & Use Cases

  • Automated Preflight Validation: Checks for filesystem permissions, missing dependencies, and invalid inputs before creating any state, preventing partial or broken channel setups.
  • Atomic State Initialization: Creates all required channel state files (channel.json, seq.json, digest.json) with rollback safety if any step fails mid-creation.
  • Optional MAD & A2A Support: Can initialize MAD methodology artifacts (spec, plan, task stubs) and publish A2A-compatible Agent Cards for cross-agent interoperability.
  • Use Case: A development team lead can instantly spin up a dedicated triage-gated production channel for a new authentication feature, set polling intervals for team updates, and invite other agents to join without manual configuration.

Quick Start

Use the council-open skill to create a new coordination channel named 'es-training' for coordinating elasticsearch model training work, set to local tier with 2-minute polling for updates from other team members.

Frequently Asked Questions about council-open

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create shared-state coordination channels for multi-agent teams?

Atomic state initialization creates all required channel files like channel.json, seq.json, and digest.json simultaneously with rollback safety. This prevents partial or broken multi-agent channel setups if any creation step fails mid-process.

What is atomic state initialization for agent-to-agent communication?

Atomic state initialization creates all required channel files like channel.json, seq.json, and digest.json simultaneously with rollback safety. This prevents partial or broken multi-agent channel setups if any creation step fails mid-process.

How do I set up a triage-gated production channel for feature development?

Triage-gated production channels are created by applying optional triage gating during channel creation, enforcing environment tiers and single-owner accountability. This ensures governed communication for cross-system orchestration and infrastructure monitoring.

Does this channel creation workflow support A2A interoperability and MAD methodology?

A2A interoperability and MAD methodology are supported through optional initialization of A2A-compatible Agent Cards and MAD artifacts including specs, plans, and task stubs. This enables cross-agent communication for multi-agent team workflows.

What preflight validation checks are needed before creating multi-agent coordination channels?

Preflight validation checks filesystem permissions, missing dependencies, and invalid inputs before creating any channel state. This automated checking prevents partial channel setups and ensures schema-valid state initialization for agent teams.

Can I configure polling intervals for team updates when spinning up a new coordination channel?

Polling intervals for team updates can be configured during channel creation, such as setting a 2-minute polling frequency for local tier environments. This allows agents to coordinate updates without manual configuration.