Name: netlify-database
Rating: 75.2 (1 reviews)
Author: netlify

netlify-database

Zero-config Postgres for Netlify apps via @netlify/database — querying data from Functions/Edge Functions, writing schema migrations, setting up Drizzle ORM, local dev with netlify dev, database branches for deploy previews, and migrating an existing Postgres project onto Netlify. Use when adding a database, building a contact form or CRUD API, writing SQL migrations, wiring up Drizzle, running netlify database commands, testing with a local Postgres, or switching from Neon/Supabase/RDS to Netlify Database.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, well-structured technical reference with executable examples and good progressive disclosure into real reference files. The main weakness is redundancy between the body and the appended house-rules section.

Suggestions

Deduplicate the appended 'Netlify house rules' section against the body—the PII/preview-link warning, drizzle @beta pin, and never-drizzle-kit-push rule each already appear above, so keep them in one authoritative place.

Expand the three migration-cutover phases (provision/rehearse/cut over) with the key sequenced steps inline rather than only deferring to references/migration-from-extension.md.

Tighten the 'Runtime gotchas' and 'Constraints' sections by merging overlapping plan-tier/permission notes to reduce repeated phrasing.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence, but the appended 'Netlify house rules' section reiterates body content (PII/preview warning, drizzle @beta pin, never-drizzle-kit-push appear twice), which is trimmable redundancy. Not a 5 because of that duplication; not a 3 because the bulk is efficient.	4 / 5
Actionability	Copy-paste-ready code, CLI commands, and config examples cover the common cases end to end—getDatabase querying, transactions, Drizzle setup, migrations, local dev, testing, and the REST API.	5 / 5
Workflow Clarity	Setup, local dev, and the three-phase migration cutover are sequenced, and destructive ops (branch delete, snapshot restore, reset) require explicit confirmation with drift-error feedback loops. Not a 5 because the cutover phases stay high-level and defer specifics to references.	4 / 5
Progressive Disclosure	A clear overview points to well-signaled one-level-deep references (migrations.md, local-dev.md, cli-commands.md, migration-from-extension.md, legacy-extension.md, operational-footguns.md), all of which are real bundle files; bulk detail is appropriately split out.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that concisely states what the skill does and when to use it, with concrete capabilities and natural trigger terms including competitor names. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—querying data from Functions/Edge Functions, writing schema migrations, setting up Drizzle ORM, local dev, database branches, and migrating an existing Postgres project—giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (zero-config Postgres via @netlify/database with enumerated capabilities) and 'when' (a concrete 'Use when...' clause with multiple trigger phrases).	5 / 5
Trigger Term Quality	The 'Use when...' clause packs in natural phrases users would say ('adding a database', 'building a contact form or CRUD API', 'writing SQL migrations', 'wiring up Drizzle') plus competitor synonyms (Neon/Supabase/RDS).	5 / 5
Distinctiveness Conflict Risk	The Netlify Database niche is clearly scoped with distinct triggers (@netlify/database, netlify database commands, Neon/Supabase/RDS migration), giving minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: netlify/context-and-tools
Path: codex/skills/netlify-database/SKILL.md
Commit: 47848e2

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.