Write, edit, organize, and review Supabase content anywhere in apps/docs — guides, explainers, tutorials, troubleshooting entries, reference docs, and partials.
SkillScore77Maintained
Automatic
◆Doc Ops pack
Last verified 9/27/2026
What it changes
Passed 17 of 22 test cases with the skill, and 4 of 22 without it.
Without skill18%
With skill77%
Checks it passed that the model alone missed
Specifies running pnpm lint:mdx from apps/docs.
Uses TOML frontmatter for the troubleshooting entry.
Requires using lowercase SQL keywords in code samples.
and 17 more in the full report
13 fixed4 passed either way5 still failing0 broke
Pass-rate lift
+59 pp
Tokens
+3%
Agent turns
0%
Response time
-42%
Model gemini-3.6-flashMeasured 9/27/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
If a term formatting rule in `apps/docs/WORD_LIST.md` directly contradicts a content structure rule in `apps/docs/CONTRIBUTING.md`, which file acts as the primary source of truth?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies that apps/docs/CONTRIBUTING.md takes precedence when guidance conflicts.
Missed
Passed
case-17 · gemini-3.6-flash · 9/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md92 linessingle file
Supabase docs authoring
Sources of truth
Before changing docs content:
Read apps/docs/CONTRIBUTING.md for content types, structure, components, and
style.
Read apps/docs/WORD_LIST.md for preferred terminology, spelling, and
capitalization.
Inspect nearby content of the same type and the relevant navigation section
before deciding on file placement or structure. Guides, explainers, and
tutorials live under apps/docs/content/guides. Troubleshooting entries live
under apps/docs/content/troubleshooting and use TOML frontmatter — follow
_template.mdx in that directory rather than a guide's YAML frontmatter.
Reference docs are generated from apps/docs/spec and library source, so
look for the spec file or repo definition instead of editing rendered output
directly.
When guidance conflicts, follow apps/docs/CONTRIBUTING.md. Match literal code,
API names, UI labels, and third-party product names even when they differ from the
word list.
Writing workflow
Identify the document type: explainer, tutorial, guide, or reference, per
apps/docs/CONTRIBUTING.md. A guide is a concise procedure for a targeted
task; a tutorial covers a larger goal and includes more explanatory context;
an explainer is conceptual and prose-based; reference content is factual,
like a dictionary entry. Troubleshooting entries follow their own TOML
structure rather than these four types.
Define the reader's goal and prerequisites before drafting.
Classify substantial sections as contextual, procedural, or reference content.
In a mixed page, group sections by information type so that context doesn't
interrupt the procedural path.
For a long or mixed page, add a short introduction that links to its major
section groups and tells readers when to use each one. Skip this navigation
when a short page is already easy to scan.
Connect contextual sections to their corresponding procedures when useful.
Add introductions to section groups, transitions between information types,