skills.rest
tmalcolm-0607
tmalcolm-0607COMMUNITY
Explore all skills by this author →
WebsiteGitHub

council-join

Joins existing council channels with automated alias conflict resolution and atomic member list updates.

Updated May 7, 2026
Search Tags:#council#alias-management#atomic-updates#agent-collaboration#mad-council#channel-join#session-reclaim
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-join
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: council-join
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/council-join
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-join

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about council-join

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

FAQPage Schema
How do I join a multi-agent council channel and manage alias conflicts automatically?▼

Joining a multi-agent council channel is automated by this skill, which handles fresh alias joins, silent reclaims of disconnected sessions, active collision rejections, and idempotent same-session re-joins to maintain consistent collaborative state.

What happens when an active alias collision occurs during channel session registration?▼

An active alias collision during channel session registration triggers a rejection of the new join attempt, with an optional prompt for explicit force-reclaim consent to override the currently active session bound to that alias.

How do I reclaim a disconnected or idle alias when restarting a collaborative agent session?▼

Reclaiming a disconnected or idle alias during a collaborative agent session restart is performed silently by the skill, which preserves read markers and applies atomic updates to the channel member list to maintain unread state across the session registry.

Does the council channel join process preserve read markers during alias reclaims?▼

Yes, the council channel join process preserves read markers during alias reclaims to maintain unread state, ensuring messages marked as read in prior sessions remain consistent after the session registry is synchronized and the alias is reclaimed.

Can I configure polling for channel message retrieval after joining a multi-agent council?▼

Configuring polling for channel message retrieval after joining a multi-agent council is supported by the skill, allowing your session to consistently retrieve new messages and maintain synchronized read state across session restarts.

When should I avoid using automated alias conflict resolution for collaborative agent workflows?▼

Avoid using automated alias conflict resolution when your collaborative agent workflow requires custom conflict handling logic, or when multiple active sessions must share the same alias simultaneously without relying on atomic channel member list updates.

Related Skills

Explore More Software Engineering Skills→
tmalcolm-0607tmalcolm-0607

council-list

List MAD.Council channels with unread counts and membership details.

Community
Intermediate
tmalcolm-0607tmalcolm-0607

council-leave

Depart MAD.Council channels with audit trails and completion reports.

Community
Advanced
GratefulJinx77GratefulJinx77

Councildescription

Manage multi-agent council debates with structured workflows and session persistence.

Community
Advanced
AtaraxiaEpiphanyAtaraxiaEpiphany

reconcile

Synchronize track-state.json with plan.md by mapping tasks via phase and name identifiers.

Community
Advanced