Validate and govern message posts to MAD.Council channel threads.
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-post
Please help me install this Agent Skill. Skill: council-post Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/council-post Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-post
This Skill eliminates the risk of invalid, unauthorized, or non-compliant messages being posted to MAD.Council channels by enforcing strict validation, membership, and governance rules at post time, including spoofing prevention, content scanning, and state consistency checks.
Instruct the AI to post a task message to the active 'incident-123' thread in the 'ops' channel, mention the on-call engineer alias, and suppress the suspicious tag if the body contains authorized security testing content.
High-intent search queries and answers about installing and using this skill.
To prevent prompt injection and alias spoofing during message posting, enforce strict session-id binding and scan message bodies for injection phrases at post time. This ensures only verified members can post validated content to channel threads.
Atomic sequence number allocation assigns unique message order identifiers while simultaneously updating thread metadata and channel digests. You need it during concurrent message posting to prevent data corruption and maintain consistent thread state.
To validate mentions and enforce body size limits for governance messages, verify all mentioned aliases against current channel members and reject payloads exceeding a 32KB body size cap. This blocks unauthorized references and oversized content.
You can post task, question, answer, status, fyi, resolve, triage-question, and triage-context message types to active, triage, and ready threads. However, posting to resolved threads requires thread reactivation rules to maintain governance state.
Message posting fails membership verification when the caller's session-id does not match the bound member alias, or the user lacks active channel permissions. Strict governance rules reject unauthorized posts to prevent spoofing and maintain access control.
The best way to manage thread state consistency is applying atomic state updates that synchronize sequence numbers, thread metadata, and channel digests simultaneously. This prevents data corruption during concurrent incident response updates.
d0d012Automate Slack message posting, channel management, and conversation searches.
tallclubExtract blockers, decisions, action items, and FYIs from Slack channel history into structured reports.
LerianStudioAutomate production incident response workflows for SEV1-3 events.
nicolasmosquerarDefine and enforce mandatory tagging across Terraform and CDK stacks using CI checks and SCPs.
