Official agent skill

Test The Docs

by supabase in supabase/supabase

Execute runnable docs snippets and examples inside a disposable Docker Compose sandbox (runner container + local Supabase stack via supabase start).

OfficialApache-2.0Auto-check passedDatabases

Install Test The Docs

skills CLI
$ npx skills add supabase/supabase --skill test-the-docs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install supabase/supabase test-the-docs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/test-the-docs .claude/skills/test-the-docs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-the-docs
GitHub stars
111k
Token cost
~1.3k tokens
SKILL.md length
537 words
Files
9
Skills in repo
22
Repo updated
First seen
Licence
Apache-2.0

At a glance

Execute runnable docs snippets and examples inside a disposable Docker Compose sandbox (runner container + local Supabase stack via supabase start).

  • Works in 6 steps: Scope → Extract → Classify → …
  • Tasks that involve Fact-checking and source verification
  • SKILL.md covers When to invoke, Core rules, Phases and Related skills
  • Runs Shell scripts from its folder; calls supabase, npm and docker

What it does

Test The Docs is an agent skill from supabase/supabase, published by the product's own GitHub organization. Execute runnable docs snippets and examples inside a disposable Docker Compose sandbox (runner container + local Supabase stack via supabase start). Use after Draft or during Self-review when asked to test the docs, fact-check CLI/SQL/code samples, or produce a verification report for a docs PR. Complements review-the-docs build and review checks; does not replace them.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files (for example `reference/sandbox-setup.md`, `reference/snippet-classes.md` and `reference/verification-report.md`).

It sits in Databases, covering Fact-checking and source verification, Containers and SQL. It works with Supabase, SQL and Docker. The repository describes itself as: The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Fact-checking and source verification
  • Tasks that involve Containers
  • Tasks that involve SQL

Example prompts

  • “/test-the-docs”

Requirements

  • Node.js
  • A Bash shell
  • Docker

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Scope
  2. Extract
  3. Classify
  4. Sandbox setup
  5. Execute
  6. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 26c838a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • supabase
    • npm
    • docker
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use supabase, npm, docker and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test The Docs loads about 1.3k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 537 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from supabase/supabase at commit 26c838a, republished under its Apache-2.0 licence (© supabase). 537 words, ~1,300 tokens.

Download SKILL.mdSave it as .claude/skills/test-the-docs/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
test-the-docs
description
Execute runnable docs snippets and examples inside a disposable Docker Compose sandbox (runner container + local Supabase stack via `supabase start`). Use after Draft or during Self-review when asked to test the docs, fact-check CLI/SQL/code samples, or produce a verification report for a docs PR. Complements review-the-docs build and review checks; does not replace them.

Test the docs

Runs procedural docs content inside disposable containers, not on the host shell and not against production. Produces a verification report for the PR body / self-review note.

For markdown rebuilds, example-app triage, and PR review, use review-the-docs. For Frame/Shape and cross-repo product lookup, use pm-the-docs.

When to invoke

  • After Draft, before or during Self-review (checklist Stage 4).
  • Standalone: "test the docs", "fact-check these snippets", "run the examples".
  • Content or tutorial PRs that add or change procedural fenced blocks.

Not for: generated reference pages, docs-app architecture questions, or hosted/production projects.

Core rules

  1. Never run against production. Local stack or temp dir only.
  2. Never run MDX fences on the host shell. Use the Compose sandbox — see reference/sandbox-setup.md and sandbox/run.sh.
  3. Proportional: Tier A (one end-to-end path) is required; Tier B spot-checks new/changed procedural blocks, not every fence on every page.
  4. Product bugs found while testing get linked or filed separately; fix docs only when the docs are wrong.

Phases

1. Scope

From explicit MDX paths, or:

bash
git diff --name-only master...HEAD -- 'apps/docs/content/**'

Skip generated reference output under features/docs/generated/.

2. Extract

List runnable artifacts from changed MDX:

  • Fenced blocks: bash, sh, sql, javascript, typescript, tsx, jsx
  • $CodeSample paths → treat as example-app (build under examples/)
  • Skip: mermaid, incomplete illustrative fragments, partial-only includes
3. Classify

Assign each artifact a class per reference/snippet-classes.md:

ClassAction
runnable-localRun in temp stack / temp dir
runnable-with-setupRun after documented setup (migrations, seed)
example-appnpm install && npm run build in examples/…
illustrative-onlyNo run required
deferredRecord reason; do not silently skip
Show full SKILL.md (286 more words)Show less
4. Sandbox setup

Follow reference/sandbox-setup.md and drive lifecycle with sandbox/run.sh:

  1. Refuse if the host is running as root.
  2. Require docker + docker info + docker compose on the host for any in-container run.
  3. Gate profiles per artifact class:
    • runnable-local / runnable-with-setup that need DB/API: ./sandbox/run.sh up-stack (DinD + runner → supabase init / supabase start in /work).
    • CLI-only blocks with no DB: still use a runner profile so fences stay off-host; skip supabase start when unused.
    • example-app: TTD_EXAMPLE_DIR=<repo>/examples/<app> ./sandbox/run.sh up-examples (Node in runner; no DinD). Do not defer solely because the host lacks a global Supabase CLI.
  4. Always ./sandbox/run.sh down when finished (cleanup trap on the host session).
  5. Capture connection URLs only inside the runner; never paste credential fields into notes or logs.

If a required prerequisite for that artifact is unavailable, mark that artifact deferred with the specific reason — never silent skip, and do not defer unrelated classes.

5. Execute
  • Tier A: one copy-pasteable end-to-end path from the page.
  • Tier B: each new/changed block classified runnable-* or example-app (build and record the result).
  • Run every fence via ./sandbox/run.sh exec or exec-timeout (never a bare host shell).
  • Bound every artifact: default 60s for shell / SQL / JS / TypeScript / tsx / jsx; allow longer for example-app install/build (e.g. 5m). On timeout, kill the process group inside the runner, then record fail or deferred with reason.
  • curl / wget only to filtered stack URLs (or page-documented local endpoints). npm / npx / node only for mounted example-app builds.
  • Capture exit code, stdout/stderr (redact secrets), and observed vs expected behavior.
6. Report

Write a verification report per reference/verification-report.md for the PR body / self-review note.

© supabase, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files in .agents/skills/test-the-docs of supabase/supabase.

  • SKILL.md
  • reference/sandbox-setup.md
  • reference/snippet-classes.md
  • reference/verification-report.md
  • sandbox/.empty/.keep
  • sandbox/.gitignore
  • sandbox/Dockerfile
  • sandbox/compose.yaml
  • sandbox/run.sh

Open the folder on GitHubat commit 26c838a

Compare with similar skills

Test The Docs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test The Docs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test The Docs this skillsupabase/supabase111k—~1.3kAutomated safety check: PassApache-2.0
SQL Database Support for pRESTprest/prest4.6k—~1.6kAutomated safety check: PassMIT
StarRocks SQL Doc Auto-FixStarRocks/starrocks12k—~7.6kAutomated safety check: NotesApache-2.0
Replica ArchitectJakeschincariol/replica-skill908—~1.1kAutomated safety check: PassMIT
Srtd CLIt1mmen/srtd105—~360Automated safety check: PassMIT
Expert DatabaseReJeCtAll/ExpertTeam-Codex113—~692Automated safety check: PassMIT

Similar skills

  • Guides classifying, gap-analyzing and scaffolding support for a new SQL database in pREST, from Postgres-compatible variants to entirely new dialects.

    4.6k GitHub stars~1.6k tokensUpdated today
    DatabasesAuto-check passed
  • StarRocks SQL Doc Auto-Fix

    StarRocks/starrocks

    Proposes verified fixes for failing SQL examples in StarRocks docs across three languages and several versions, then opens draft pull requests and never merges.

    12k GitHub stars~7.6k tokensUpdated today
    DatabasesAuto-check: notes
  • Replica Architect

    Jakeschincariol/replica-skill

    Plans the stack, database schema and API for an app clone, from the recon map replica-recon wrote.

    908 GitHub stars~1.1k tokensUpdated 4 days ago
    DatabasesAuto-check passed
  • Srtd CLI

    t1mmen/srtd

    This skill should be used when the user mentions "srtd", "sql templates", "migrations-templates", "live reload sql", "supabase functions", when working with files in supabase/migrations-templates/…

    105 GitHub stars~360 tokensUpdated 1 mo ago
    DatabasesAuto-check passed
  • Expert Database

    ReJeCtAll/ExpertTeam-Codex

    数据库优化专家入口。用于 Codex CLI 的 $expert-database 调用. An agent skill from ReJeCtAll/ExpertTeam-Codex.

    113 GitHub stars~692 tokensUpdated 3 mo ago
    DatabasesAuto-check passed
  • DB Migrate

    alexeykrol/claude-code-starter

    Миграция схемы базы данных: SQLite → PostgreSQL/Supabase. An agent skill from alexeykrol/claude-code-starter.

    194 GitHub stars~405 tokensUpdated 2 mo ago
    DatabasesAuto-check: notes

More from supabase/supabase

All 22 skills in this repo
  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    Auto-check passed
  • Clickhouse Logs Queries

    supabase/supabase

    Official

    Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).

    111k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Review The Docs

    supabase/supabase

    Official

    Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).

    111k GitHub stars~4.6k tokensUpdated today
    Auto-check passed
  • Vitest

    supabase/supabase

    Official

    Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering.

    111k GitHub starsUsed in 12 repos~1.1k tokens
    Auto-check passed
  • Safe SQL Execution

    supabase/supabase

    Official

    A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…

    111k GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • Studio E2E Tests

    supabase/supabase

    Official

    Write and run Playwright E2E tests for Supabase Studio (e2e/studio).

    111k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Questions about Test The Docs

What does Test The Docs do?

Execute runnable docs snippets and examples inside a disposable Docker Compose sandbox (runner container + local Supabase stack via supabase start). Test The Docs is an agent skill from supabase/supabase, published by the product's own GitHub organization. Execute runnable docs snippets and examples inside a disposable Docker Compose sandbox (runner container + local Supabase stack via supabase start).

When should I use Test The Docs?

Test The Docs fits situations like: tasks that involve Fact-checking and source verification; tasks that involve Containers; tasks that involve SQL.

How do I install Test The Docs in Claude Code?

Run `npx skills add supabase/supabase --skill test-the-docs -a claude-code`. Or copy the skill folder (.agents/skills/test-the-docs in supabase/supabase) into .claude/skills/test-the-docs in your project. Claude Code loads it when a task matches its description.

How do I install Test The Docs in Codex?

Run `npx skills add supabase/supabase --skill test-the-docs -a codex`. Or copy the skill folder (.agents/skills/test-the-docs in supabase/supabase) into .agents/skills/test-the-docs in your project. Codex loads it when a task matches its description.

Can I use Test The Docs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add supabase/supabase --skill test-the-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-the-docs, .gemini/skills/test-the-docs, .github/skills/test-the-docs and .opencode/skills/test-the-docs in your project.

What does Test The Docs need to run?

Going by SKILL.md and its folder, Test The Docs needs a shell for the scripts in its folder and the command-line tools its instructions call (supabase, npm, docker and git). Our summary lists: Node.js; A Bash shell; Docker.

Does Test The Docs access the network?

SKILL.md contains no URLs. Its commands use npm, docker and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Test The Docs safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test The Docs use?

Test The Docs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test The Docs use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Test The Docs?

Skills that share tags, products or a category with Test The Docs: SQL Database Support for pREST (prest/prest, 4.6k stars), StarRocks SQL Doc Auto-Fix (StarRocks/starrocks, 12k stars), Replica Architect (Jakeschincariol/replica-skill, 908 stars) and Srtd CLI (t1mmen/srtd, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test The Docs?

supabase (a GitHub organization, an official publisher) maintains it in supabase/supabase, which has 111,222 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 8, 2026.

Source: supabase/supabase on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.