council-join

What problem does it solve?

Joining an existing MAD council channel as a named member typically requires manual state management, alias conflict resolution, and session tracking, which is error-prone and time-consuming for collaborative agent workflows. This skill automates the entire join process, handling edge cases like disconnected alias reclaims and active alias collisions without manual intervention.

Core Features & Use Cases

• Automated Alias Conflict Resolution: Handles four canonical join scenarios: fresh joins for new aliases, silent reclaims of disconnected or idle aliases, rejection of active alias collisions with optional force-reclaim consent, and idempotent no-ops for same-session re-invokes.
• Consistent State Management: Automatically updates channel member lists with atomic writes, preserves read markers during alias reclaims to maintain unread state, and synchronizes session registry entries to track channel memberships.
• Use Case: For example, if you restart a Claude Code session and want to rejoin a council channel with your existing alias, this skill will silently reclaim it if your prior session was marked idle, or prompt for explicit consent if another active session is currently using the alias.

Quick Start

Use the council-join skill to join the existing 'service-redesign' council channel as the alias 'Skeptic' to participate in ongoing council discussions.