discord-ops

Enforce safe Discord mention and thread behaviors for Zeus/Atena inter-agent communication.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mattei2005/mgs-agent --skill discord-ops-mattei2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discord-ops
Source: https://github.com/mattei2005/mgs-agent/tree/main/profiles/zeus-skills/ops/discord-ops
Command: npx skills add https://github.com/mattei2005/mgs-agent --skill discord-ops-mattei2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves operational unreliability in inter-agent communication via Discord by providing safe, repeatable procedures to keep Zeus/Atena behavior consistent, prevent bot-to-bot loops, and ensure infra actions (gateway restart, cron/diagnostics, and git-hook notifications) are executed with guardrails.

Core Features & Use Cases

  • Inter-agent Discord communication rules: Defines when Zeus should talk to Atena (thread vs cross-channel), how to handle bot mentions safely, and how to avoid confirmation/queued/read-only ping-pong loops.
  • Operational diagnostics and recovery: Covers gateway session stale detection, Message Content Intent verification, rate-limit symptoms, and Hermes routing/restart incident handling.
  • Discord infra automation: Provides playbooks for roles managed by Discord, git post-commit webhook notifications (TTY-gated), and operational alert formatting.

Quick Start

Use this skill when you need to diagnose missing Discord inbound messages or prevent recurring multi-agent mention loops in a shared thread involving Zeus and Atena.

Frequently Asked Questions about discord-ops

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

FAQPage Schema
How do I prevent Discord bot-to-bot confirmation loops in shared threads?

To prevent Discord bot-to-bot confirmation loops, you enforce safe mention behaviors and thread lifecycle rules defined in operational playbooks. This involves configuring DISCORD_ALLOW_BOTS gating and applying evidence-first validation using agent logs to stop recurring ping-pong interactions.

How do I diagnose stale Discord gateway sessions and rate-limit noise?

Diagnosing stale Discord gateway sessions and rate-limit noise requires running operational playbooks that verify Message Content Intent configurations and analyze agent logs. You then coordinate routing and restart actions using Discord and Hermes API actions to recover communication stability.

What are the YAML operational playbook requirements for Discord inter-agent messaging?

YAML operational playbooks for Discord inter-agent messaging must define DISCORD_ALLOW_BOTS gating, thread lifecycle rules, role and webhook constraints, and evidence-first validation steps. These configurations ensure consistent Zeus and Atena behavior across cross-channel routing.

Can I use git hooks to send Discord webhook notifications for post-commit events?

Yes, you can use git hooks to send Discord webhook notifications for post-commit events. The automation requires TTY-gating to ensure notifications are triggered safely and formatted correctly as operational alerts within your established role constraints.

What is the best way to manage Zeus and Atena routing during active Discord conversations?

The best way to manage Zeus and Atena routing during active Discord conversations is to apply operational playbooks that dictate thread versus cross-channel communication. This prevents confirmation loops by safely handling bot mentions and coordinating Hermes restart actions.