How do I install the Supacrawl skill?

Run npx skillmds@latest add tomevault-io/supacrawl in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Supacrawl skill do?

Use this skill when the user wants to inspect, mirror, search, export, or back It is listed under Coding & Dev Tools on SkillMD.

Is Supacrawl safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Supacrawl?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Supacrawl free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Supacrawl?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Supacrawl by tomevault-io — Agent Skill

Name: Supacrawl
Author: tomevault-io

File contents

supacrawl

Use this skill when the user wants to inspect, mirror, search, export, or back up a Supabase project into a local SQLite archive.

Safety

Never print secrets. Redact Postgres URLs, passwords, service role keys, JWTs, and anon keys.
Do not write to the remote Supabase project.
Prefer temporary archives under /private/tmp for trials unless the user asks for a durable archive.
Start with doctor before a live sync.
Use sync before sync --full on unfamiliar projects.
Use storage pull --limit before downloading a large bucket.
Use status --sync never when the user wants an archive-only read.
Use encrypted backups only with age recipients or identities supplied through config, files, or environment variables.

Quick Workflow

supacrawl init --project-id <label>
supacrawl doctor --json
supacrawl sync --json
supacrawl status --json
supacrawl diff /path/to/older-archive.db --json
supacrawl size --json

Use diff against a copy of the archive made before the sync you want to compare against.

Read commands auto-refresh stale metadata by default. Override the policy when needed:

supacrawl status --sync never --json
supacrawl report --sync always --json
supacrawl search --stale-after 1h "auth.uid"

For a full local database copy:

supacrawl sync --full --batch-size 2000

For a smaller archive:

supacrawl sync --full --no-row-fts --batch-size 2000

Export one table:

supacrawl export --type jsonl --out companies.jsonl public.companies

Download Storage blobs after a full sync:

supacrawl storage pull --dir ./supabase-storage --limit 10

Create and inspect an encrypted local backup:

supacrawl backup keygen --out ~/.supacrawl/age.key
supacrawl backup init --recipient age1...
supacrawl backup push --json
supacrawl backup status --json
supacrawl backup pull --out ./supacrawl-restore --json

Local Analysis

Use read-only SQL against the archive:

supacrawl sql "select schema_name, name, rls_enabled from tables order by schema_name, name"
supacrawl sql "select json_extract(row_json, '$.name') from table_rows where schema_name='public' and table_name='companies' limit 20"

Expected Archive Tables

schemas
tables
columns
indexes
constraints
policies
functions
triggers
storage_buckets
storage_object_stats
crawl_runs
data_copy_runs
search_docs
table_rows

Validation

Before declaring the tool healthy, run:

./scripts/validate-local.sh

If SUPABASE_DB_URL is set, the validator also runs live doctor and metadata sync checks. Set SUPACRAWL_VALIDATE_FULL=1 only when a full data copy is safe.

Source: davemorin/supacrawl — distributed by TomeVault.

---name: supacrawldescription: Use this skill when the user wants to inspect, mirror, search, export, or back---# supacrawlUse this skill when the user wants to inspect, mirror, search, export, or backup a Supabase project into a local SQLite archive.## Safety- Never print secrets. Redact Postgres URLs, passwords, service role keys, JWTs, and anon keys.- Do not write to the remote Supabase project.- Prefer temporary archives under `/private/tmp` for trials unless the user asks for a durable archive.- Start with `doctor` before a live sync.- Use `sync` before `sync --full` on unfamiliar projects.- Use `storage pull --limit` before downloading a large bucket.- Use `status --sync never` when the user wants an archive-only read.- Use encrypted backups only with age recipients or identities supplied through config, files, or environment variables.## Quick Workflow```bashsupacrawl init --project-id <label>supacrawl doctor --jsonsupacrawl sync --jsonsupacrawl status --jsonsupacrawl diff /path/to/older-archive.db --jsonsupacrawl size --json```Use diff against a copy of the archive made before the sync you want to compareagainst.Read commands auto-refresh stale metadata by default. Override the policy whenneeded:```bashsupacrawl status --sync never --jsonsupacrawl report --sync always --jsonsupacrawl search --stale-after 1h "auth.uid"```For a full local database copy:```bashsupacrawl sync --full --batch-size 2000```For a smaller archive:```bashsupacrawl sync --full --no-row-fts --batch-size 2000```Export one table:```bashsupacrawl export --type jsonl --out companies.jsonl public.companies```Download Storage blobs after a full sync:```bashsupacrawl storage pull --dir ./supabase-storage --limit 10```Create and inspect an encrypted local backup:```bashsupacrawl backup keygen --out ~/.supacrawl/age.keysupacrawl backup init --recipient age1...supacrawl backup push --jsonsupacrawl backup status --jsonsupacrawl backup pull --out ./supacrawl-restore --json```## Local AnalysisUse read-only SQL against the archive:```bashsupacrawl sql "select schema_name, name, rls_enabled from tables order by schema_name, name"supacrawl sql "select json_extract(row_json, '$.name') from table_rows where schema_name='public' and table_name='companies' limit 20"```## Expected Archive Tables- `schemas`- `tables`- `columns`- `indexes`- `constraints`- `policies`- `functions`- `triggers`- `storage_buckets`- `storage_object_stats`- `crawl_runs`- `data_copy_runs`- `search_docs`- `table_rows`## ValidationBefore declaring the tool healthy, run:```bash./scripts/validate-local.sh```If `SUPABASE_DB_URL` is set, the validator also runs live `doctor` and metadatasync checks. Set `SUPACRAWL_VALIDATE_FULL=1` only when a full data copy is safe.---> Source: [davemorin/supacrawl](https://github.com/davemorin/supacrawl) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Supacrawl