database-design — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited database-design (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Reason about the workload first. Patterns follow from requirements, not habit.
Each topic lives in its own file. Open only the ones the current task touches.
| File | Covers | Open it when |
|---|---|---|
database-selection.md | Engine trade-offs across Postgres, Neon, Turso, SQLite, and friends | Picking where data lives |
orm-selection.md | Drizzle, Prisma, Kysely, raw SQL | Picking how code talks to the DB |
schema-design.md | Normalization, keys, relationships, soft deletes | Modeling tables |
indexing.md | Index families and composite ordering | Speeding up reads |
optimization.md | N+1, query plans, tuning order | Hunting down slow queries |
migrations.md | Expand/contract, online changes, managed engines | Evolving a live schema |
A lightweight checker flags common Prisma/Drizzle schema smells. Run it; don't read it.
python scripts/schema_validator.py <project_path>Work through these (or ask) before writing any DDL:
❌ Reaching for Postgres on a tiny app where embedded SQLite would do ❌ Leaving frequently-filtered columns unindexed ❌ Shipping SELECT * to production paths ❌ Dumping structured fields into a JSON blob out of laziness ❌ Letting ORM relation loads fan out into N+1 query storms
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.