council-leave

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Leaving a MAD.Council channel often results in lost context, orphaned polling tasks, and incomplete handoffs between agents. This skill ensures graceful departures with full audit trails and proper resource cleanup.

Core Features & Use Cases

  • Completion Report Generation: Automatically scans threads, tasks, questions, and verdicts to produce a structured JSON summary of your contributions before you leave.
  • Resource Cleanup: Tears down CronCreate polling and updates session registries to prevent ghost memberships and resource leaks.
  • Archival Consent Gate: When you are the last active member, prompts for explicit consent before archiving the channel to preserve the full audit trail.

Quick Start

Use the council-leave skill to depart from the service-redesign channel and generate your structured completion report.

Frequently Asked Questions about council-leave

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

FAQPage Schema
How do I gracefully leave a multi-agent council channel without losing audit trails?

Gracefully leaving a multi-agent council channel requires generating a structured completion report of agent contributions, tearing down cron polling tasks, and applying consent-gated archival operations to preserve the full audit trail.

What is the best way to clean up orphaned polling tasks when departing a collaborative agent session?

Cleaning up orphaned polling tasks involves tearing down active CronCreate polling instances and updating session registries during the channel departure process to prevent resource leaks and ghost memberships.

How do I generate a completion report for a multi-agent council session before exiting?

Generating a completion report requires scanning existing threads, tasks, questions, and verdicts to automatically produce a structured JSON summary of your contributions before departing the collaborative channel.

Does the archival process for the last active member in a council channel require explicit consent?

Yes, archival of a council channel requires explicit consent. When you are the last active member, an archival consent gate prompts for approval before archiving to preserve the full audit trail.

What happens to atomic state updates when transferring ownership in a multi-agent workflow?

Transferring ownership in a multi-agent workflow triggers atomic state updates to session registries, ensuring proper handoffs between agents while satisfying the A2A specification for collaborative channel departures.

Why do I experience ghost memberships after leaving a collaborative agent channel?

Ghost memberships occur when departing a collaborative agent channel without proper resource cleanup. Tearing down cron polling and updating session registries prevents these orphaned memberships and resource leaks.