Discrawl

Mirror Discord guild data into a local SQLite archive for search, inspection, and agent queries. Bot-token only, no user-token hacks. Data stays local.

Security Scan

Discrawl's requirements and runtime instructions are coherent with its stated purpose (mirroring Discord guild data locally); the only minor notes are reuse of an OpenClaw config file and the need to verify the third‑party Homebrew tap before installing.

Purpose & Capability

The skill declares a single required binary (discrawl) and a Discord bot token, which is exactly what's needed to crawl guild data. No unrelated credentials or unusual binaries are requested. The optional mention that it can reuse ~/.openclaw/openclaw.json is reasonable for convenience but is not required.

Instruction Scope

SKILL.md instructs only to run the discrawl binary (doctor/init/sync/status/search/sql) and store data under ~/.discrawl. This stays within the stated purpose. Notes: (1) it mentions optionally reusing ~/.openclaw/openclaw.json — reading that file is out-of-band relative to declared requirements and is optional, (2) it recommends scheduling via PaperFang cron (infrastructure suggestion), and (3) it exposes a raw SQL command (discrawl sql ...), meaning an agent with access to this skill can run arbitrary read queries against the local SQLite archive — protect that DB accordingly.

Install Mechanism

Installation is via a Homebrew formula (steipete/tap → discrawl). Brew formulas are a standard install path; this is lower-risk than arbitrary downloads. As a best practice, verify the tap (steipete/tap) and formula source before installing.

Credentials

Only DISCORD_BOT_TOKEN is required, which matches the stated purpose. No unrelated secrets or multiple credentials are requested. The only caveat: the SKILL.md mentions optionally reusing ~/.openclaw/openclaw.json (a config file) even though no config paths are declared — this is optional but worth noting.

Persistence & Privilege

The skill does not request always:true and writes its own config and DB under ~/.discrawl, which is expected. Model invocation is allowed (normal). Consider that allowing autonomous agent invocation plus the ability to run discrawl sql gives the agent read access to all mirrored messages — protect the local DB and limit agent privileges accordingly.

Assessment

This skill appears to do what it says: it runs a local tool (discrawl) to copy Discord guild data into ~/.discrawl/discrawl.db using a Discord bot token. Before installing and using it: (1) verify the Homebrew tap (steipete/tap) and the formula source on the project's GitHub to ensure you're installing the expected binary, (2) create a bot token with the minimum permissions required and only invite the bot to guilds you control or trust, (3) protect the local DB (~/.discrawl/discrawl.db) with appropriate filesystem permissions or encryption because it will contain message history, and (4) be aware that an agent invoking this skill can run raw SQL (discrawl sql ...) against the local archive — restrict agent autonomy or review queries if you don't want full local-history access. If you want me to, I can check the GitHub repo and brew tap homepage for matching authorship and release artifacts.

Local-first Discord crawler. Pulls guild metadata, channels, and message history into ~/.discrawl/discrawl.db (SQLite) so an agent can query history without depending on Discord search.

Requirements

• Discord bot token (not a user token). Create one at https://discord.com/developers/applications.
• Bot must be invited to each guild you want to mirror, with permissions to read message history.
• discrawl binary on PATH.

Setup

export DISCORD_BOT_TOKEN="your-bot-token"
discrawl doctor       # verify token + permissions
discrawl init         # create local config + database
discrawl sync --full  # initial sync of all accessible guilds

If you already use OpenClaw, discrawl can reuse ~/.openclaw/openclaw.json for shared config.

State

• Config: ~/.discrawl/config.toml
• Database: ~/.discrawl/discrawl.db

Common Commands

discrawl status                       # last sync, row counts
discrawl sync --incremental           # pull new messages since last run
discrawl guilds list --json
discrawl channels list --guild <id> --json
discrawl messages list --channel <id> --limit 100 --json
discrawl search "keyword" --json
discrawl sql 'SELECT count(*) FROM messages'   # raw SQL

Integration Notes

• Read-only against Discord; only writes to the local SQLite file.
• Use --json on every command for agent-parseable output.
• Schedule incremental syncs via PaperFang cron for continuous mirroring.