
from discord.py-self-mcp24
CLI-driven Discord operations with a persistent daemon: send/read messages, list guilds/channels, manage threads and basic moderation via local scripts.
This skill provides a CLI wrapper around a persistent Discord client daemon (discord.py-self) so agents or local tooling can perform Discord operations instantly without reconnect overhead. It exposes commands to send, delete, pin messages, create and manage threads, list guilds and channels, and read messages. The daemon-client architecture uses a local Unix socket for low-latency command exchange and handles auto-restart on code changes.
Use this skill when an agent needs programmatic, low-latency access to a Discord account for tasks like automated messaging, reading channel/thread history, or lightweight moderation/administration workflows that benefit from a persistent connection. It's aimed at developer tooling and MCP-style integrations rather than public webhooks.
Best matched to agent tooling that can run local Python CLIs or shell commands (Copilot-style agents, local CLI-driven agents, or any automation that can execute python scripts). Not designed as a browser UI or web service integration.
Discord CLI skill providing a daemon-client architecture for Discord operations via Unix socket IPC. Scripts are well-written with proper auth (timing-safe compare_digest) and process management, but fail to run due to missing discord and discord_py_self_mcp Python packages. The self-bot approach (discord.py-self) violates Discord ToS, noted in the SKILL.md, which limits practical safe usage.
discorddiscord_py_self_mcpClean codebase with good security practices (timing-safe auth, private file permissions, no hardcoded secrets). Auto-restart on code change is a minor concern. The self-bot nature is a ToS issue not a security one. JS files (postinstall, sync-release-version) are package tooling, not runtime scripts.