Menú
Sync and archive data from messaging platforms (WhatsApp, Discord, Slack, Twitter/X, Google) into Moltis memory as daily digest summaries. Orchestrates crawl tools and writes structured markdown to the memory system.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Archive and search Slack workspace messages, threads, and channels via the slacrawl CLI. Supports API sync, Slack export ZIP import, local desktop cache import, and full-text search.
Archive and search Discord guild messages, threads, and members via the discrawl CLI. Supports bot API sync, local cache import, full-text and semantic search, and Git-backed NDJSON snapshots.
Create and manage webhook subscriptions for event-driven agent activation. Use when the user wants external services (GitHub, GitLab, Stripe, Linear, PagerDuty, Sentry, or any generic source) to trigger agent runs by POSTing events to a URL.
Read-only local archive and full-text search of WhatsApp Desktop messages via the wacrawl CLI. Use for searching chat history, exporting conversations, and creating encrypted backups. macOS only (reads local WhatsApp Desktop SQLite databases).
Local-first Twitter/X workspace for archiving, searching, and triaging tweets, DMs, likes, bookmarks, and mentions. Includes a web UI for inbox triage and AI scoring.
Add, remove, configure, and troubleshoot MCP (Model Context Protocol) servers. Use when the user wants to connect external tools, manage MCP server lifecycle, or debug MCP connectivity issues.
| name | data-sync |
| description | Sync and archive data from messaging platforms (WhatsApp, Discord, Slack, Twitter/X, Google) into Moltis memory as daily digest summaries. Orchestrates crawl tools and writes structured markdown to the memory system. |
| origin | {"source":"moltis","url":"https://github.com/moltis-org/moltis"} |
Orchestrate data archiving tools to sync external platform data into Moltis memory as searchable daily digest summaries.
| Source | Tool | Auth Required |
|---|---|---|
wacrawl | None (macOS local files) | |
| Discord | discrawl | DISCORD_BOT_TOKEN |
| Slack | slacrawl | SLACK_BOT_TOKEN |
| Twitter/X | birdclaw | Optional (xurl for API) |
| Google Suite | gog | Google OAuth2 |
For each source the user wants to sync:
<tool> doctor to verify the tool is installed and authenticated--json: Extract relevant messages and datamemory/<source>/YYYY-MM-DD.mdmemory/
whatsapp/YYYY-MM-DD.md # wacrawl digests
discord/YYYY-MM-DD.md # discrawl digests
slack/YYYY-MM-DD.md # slacrawl digests
twitter/YYYY-MM-DD.md # birdclaw digests
google/YYYY-MM-DD.md # gog digests
Each digest file should follow this structure for optimal memory indexing (section headers create natural chunk boundaries for search):
# <Source> — YYYY-MM-DD
## <Channel/Category 1>
- Key point or conversation summary
- Decisions made, action items
- Notable links or attachments shared
## <Channel/Category 2>
- ...
## Action Items
- [ ] Follow up on X with @person
- [ ] Review document shared by Y
wacrawl sync
wacrawl search "query" --json --limit 50
discrawl sync --all
discrawl search "query" --json --after YYYY-MM-DD
slacrawl sync
slacrawl search "query" --json --after YYYY-MM-DD
birdclaw sync
birdclaw inbox --json
birdclaw search "query" --json --after YYYY-MM-DD
gog gmail list --query "after:YYYY/MM/DD" --json --limit 50
gog calendar events --from YYYY-MM-DD --to YYYY-MM-DD --json
When the user asks to "sync all my messages" or "update my data":
which wacrawl discrawl slacrawl birdclaw gog--jsonYYYY-MM-DD.md format. The memory system indexes by filename date.