← ClaudeAtlas

discord-channel-memorylisted

Automatically reads your Discord channels every 6 hours and builds a rolling memory digest. Solves the problem of losing context when work happens across multiple channels — your agent will always know what's going on everywhere, without wasting tokens loading everything at startup.
oh-ashen-one/openclaw-discord-memory · ★ 12 · Web & Frontend · score 67
Install: claude install-skill oh-ashen-one/openclaw-discord-memory
# Discord Channel Memory ## What This Does If you run OpenClaw across multiple Discord channels, you've hit this problem: work happens in one channel, you ask about it in another, and your agent has no idea what you're talking about. This skill fixes that. Every 6 hours, your agent reads your channels, extracts what happened, and saves a rolling memory digest. When you reference something from another channel, your agent checks the digest instead of saying "I don't know." **Two files are written:** - `memory/channels/digest.md` — rolling 7-day window. Always fresh, never bloated. Automatically trims anything older than a week. - `memory/channels/digest-archive.md` — permanent archive. Every run appended, never deleted. There if you ever need to look back further. **After each run**, your agent posts one message to your announcements channel confirming the digest ran. --- ## Quick Start ### Step 1 — Configure your channels Edit the channel list in the cron payload below. Add your Discord channel IDs and how many messages to read from each: ``` # High-traffic channels (read more) YOUR_GENERAL_CHANNEL_ID → 50 messages YOUR_MAIN_PROJECT_CHANNEL_ID → 50 messages # Medium-traffic channels YOUR_OTHER_CHANNEL_ID → 30 messages # Low-traffic channels YOUR_ARCHIVE_CHANNEL_ID → 20 messages ``` To find a channel ID in Discord: right-click the channel → Copy Channel ID (developer mode must be on). ### Step 2 — Set your workspace path Replace `YOUR_WORKSPACE_PATH` with your O