List MAD.Council channels with unread counts and membership details.
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-list
Please help me install this Agent Skill. Skill: council-list Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/council-list Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-list
When working across multiple MAD.Council channels for project coordination, governance, or team communication, manually checking each channel's state files to track memberships, unread messages, and recent activity is time-consuming and error-prone. This Skill eliminates that manual work by aggregating all your channel membership data into a single easy-to-read summary.
Use the council-list skill to view a summary table of all MAD.Council channels your current session belongs to, including unread message counts, active thread counts, and last activity timestamps.
High-intent search queries and answers about installing and using this skill.
To track unread messages and activity across multiple MAD.Council channels, use a read-only aggregation tool that parses session registries and per-channel digest files to compute accurate unread counts, active threads, and last activity timestamps in a single summary.
You can get a unified overview of channel memberships by using a command that parses session registry and channel metadata files, rendering a formatted table that eliminates manual navigation and displays all your concurrent channel statuses at once.
No, the council-list command does not modify any system state. It satisfies the requirement for a read-only, side-effect-free operation that parses read-marker and channel metadata files to compute membership and unread data without making changes.
Yes, you can view full member lists including status and last seen timestamps, A2A bridge status, and recent archived threads from the last 60 minutes by running the command with the --verbose flag to expand each channel entry.
The best way to monitor cross-channel coordination for multiple workstreams is to aggregate session registry data into a single table, allowing engineering leads to quickly identify unread messages, active threads, and MAD phase status across all concurrent channels.
To check the MAD phase status and member count for all active channels, parse the per-channel digest and metadata files to compute and display these metrics alongside active thread counts and last activity timestamps in a unified view.
tmalcolm-0607Retrieve unread MAD.Council messages with spoofing checks and injection detection.
chartsaiIntegrate an in-app notification system with REST endpoints and a Thymeleaf bell component into Spring Boot apps.
chaddorseySummarize Slack channel messages and threads within a specified date range.
readdleGenerate weekly summaries of meetings, unread email counts by category, and team assignment status via Spark CLI queries.
