openclaw/discrawl

cli for Discord with sqlite backend

Go760 ★Data & StorageGitHub ↗
Quality: solid 18/24
PAI: integrate 0.63
Appraised: 2026-05-27 current
Contents

Overview

Verdict

Rating Summary
Quality solid (18/24) Actively maintained, well-documented CLI with strong adoption signals but no visible test infrastructure or CI configuration.
PAI Relevance integrate (0.63) Fills PAI's complete gap in Discord/communication archiving via a subprocess-able Go CLI with structured JSON output; Git snapshot distribution pattern worth studying.

Quality Assessment

18/24 — maintained / adequately-documented / solid

Health: 6/8 (maintained)

Failed:

Passed:

Documentation: 6/8 (adequately-documented)

Failed:

Passed:

Engineering Signals: 6/8 (solid)

Failed:

Passed:

PAI Relevance

Dimension Score Assessment
Harvest Value 1 Git-backed private snapshot distribution (read access with no Discord credentials on reader machines) and the FTS5+SQLite local-archive pipeline are worth studying for PAI's file-based KNOWLEDGE/ memory and knowledge distribution patterns.
Integration Readiness 1 Go prevents direct bun add, but --json output flags (doctor --json, status --json, metadata --json) and clean subcommand structure allow wrapping as a PAI skill via subprocess with modest adapter code.
Overlap Risk 0 No Discord-specific skill, tool, or hook exists in PAI's manifest; Browser, Apify, and BrightData skills target general web scraping and are not Discord-aware.
Gap Fill 1 Addresses communication-platform archiving and local FTS search over team history — a functional area absent from PAI's 52 skills and 79 tools — though the scope is narrower than PAI's broader memory and knowledge gaps.

Composite: 0.63

What Next

Landscape Position

Category: Data & Storage

In this category: simonw--datasette (excellent, 20/24)

Standing: First Discord-specific archiving entry; ranks below datasette (20/24) on quality but fills a completely different niche — live ingestion and local FTS search for a single communication platform rather than general-purpose multi-source data exploration and publishing.

Evidence Base

Density: 8/10 — Available: full repo metadata (stars, forks, open issues, dates, license, archived status), 8KB README excerpt, release tag and date, primary language, description. Missing: dependency manifest contents (go.mod), CI workflow configuration, test file structure, contributor count.

Notes