community-pulselisted

# Community Pulse — Discord weekly digest Surface the signal in a busy Discord server. Who joined, which channels are hot, who's contributing, what's getting asked, and what's left hanging — in one digest you can act on in 15 minutes. ## Usage `/community-pulse` — weekly digest of the connected Discord server. Pass a guild ID if the bot is in more than one server: `/community-pulse 123456789012345678` ## Prerequisites The Discord MCP needs **two privileged intents** enabled in the Discord Developer Portal → Bot tab → Privileged Gateway Intents: - **Server Members Intent** — without it, `list_guild_members` returns only the bot itself. - **Message Content Intent** — without it, `get_channel_messages` returns authors and timestamps but every `content` field comes back empty. If the report comes back with a 1-element member list or empty message content, this is almost always why. The skill flags the gap loudly at the top of the output rather than silently producing misleading numbers. The bot also needs **View Channel + Read Message History** in each channel you want analysed — these are channel-level permissions, not intents. ## Steps ### 1. Sanity check the connection Call `mcp__cogny__discord__get_current_user` to confirm the bot identity. If this fails with an authentication error, the bot token in the cogny warehouse is bad — reconnect at `app.cogny.com/warehouse/<id>/settings/api`. ### 2. Pick the guild Call `list_guilds`. If exactly one guild, use it.