Skip to content
Skills Library
Data & analytics · Review & audit

audit

/audit

Audit a database schema, ORM model, or migrations for design and performance — produces two independent 0-100 scores (Design & Integrity + Performance & Scale) plus a prioritized, evidence-backed report. Read-only; never writes or migrates. Use when the user asks to audit, analyze, review, check, or score a database, schema, data model, migrations, indexes, keys, referential integrity, types, constraints, query patterns, partitioning, or connection pooling — for Postgres, MySQL, Mongo, DynamoDB, Cassandra, pgvector, ClickHouse, Neo4j, and friends.

Repository
claude-db ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Audit a database schema, ORM model, or migrations for design and performance — produces two independent 0-100 scores (Design & Integrity + Performance & Scale) plus a prioritized, evidence-backed report. Read-only; never writes or migrates. Use when the user asks to audit, analyze, review, check, or score a database, schema, data model, migrations, indexes, keys, referential integrity, types, constraints, query patterns, partitioning, or connection pooling — for Postgres, MySQL, Mongo, DynamoDB, Cassandra, pgvector, ClickHouse, Neo4j, and friends.

Arguments

/audit <path|connection-target> [--paradigm auto|relational|document|key-value|wide-column|vector|time-series|graph] [--tier 0|
Original author description

Audit a database schema, ORM model, or migrations for design and performance — produces two independent 0-100 scores (Design & Integrity + Performance & Scale) plus a prioritized, evidence-backed report. Read-only; never writes or migrates. Use when the user asks to audit, analyze, review, check, or score a database, schema, data model, migrations, indexes, keys, referential integrity, types, constraints, query patterns, partitioning, or connection pooling — for Postgres, MySQL, Mongo, DynamoDB, Cassandra, pgvector, ClickHouse, Neo4j, and friends.

How it works

  1. What to do
Original SKILL.md headings · 19 lines, 316 words
SKILL.md preview
---
name: audit
description: Audit a database schema, ORM model, or migrations for design and performance — produces two independent 0-100 scores (Design & Integrity + Performance & Scale) plus a prioritized, evidence-backed report. Read-only; never writes or migrates. Use when the user asks to audit, analyze, review, check, or score a database, schema, data model, migrations, indexes, keys, referential integrity, types, constraints, query patterns, partitioning, or connection pooling — for Postgres, MySQL, Mongo, DynamoDB, Cassandra, pgvector, ClickHouse, Neo4j, and friends.
argument-hint: "<path|connection-target> [--paradigm auto|relational|document|key-value|wide-column|vector|time-series|graph] [--tier 0|1|2]"
allowed-tools: Read, Grep, Glob, Bash, Task
---
<!-- Copyright (c) 2026 Enrique Rocha (@soyenriquerocha) · tododeia.com · id er-f37b7121 -->

# /claude-db:audit

A full, **read-only** database audit. Never writes files, never mutates the database — even at Tier 1/2 it runs only read-only verification queries.

`$ARGUMENTS` = `<path|connection-target> [flags]`. The target is a repo path (schema/ORM/migration files) and, optionally, a live database via `$DATABASE_URL` for Tier-1/2 verification. If no target is given **and no schema/ORM/migration artifacts are found in the working directory**, do not fabricate a pass: say so plainly and suggest `/claude-db:start` (guided wizard, zero artifacts) or `/claude-db:design` (greenfield).

## What to do
1. Invoke the **db-orchestrator** skill with the target and flags. It detects the stack (`scripts/detect-stack.mjs` — paradigm/engine/ORM/platform), parses the schema (`scripts/parse-schema.mjs` / `parse-orm-python.py`), records the data **tier** reached (0/1/2), dispatches the read-only auditor subagents in parallel, merges findings, and runs **db-score**.
2. Present:
   - The two scores — **Design & Integrity** and **Performance & Scale** — each with a band (A–F) and a one-line interpretation. Show the uncapped `computed` alongside any `capped:true` (a `fail`+`severity:5` on that axis caps it at F). Never blend the two.
   - A per-category breakdown for each score (value, weight, active?), the detected paradigm/engine, the tier reached, and the count of `needs_api` checks (score confidence — never a silent pass).
   - If multiple datastores were detected, the **worst-of-across-stores** roll-up per axis with the flooring store named, plus the per-store breakdown.
   - A **prioritized action list** sorted by impact: each item with status, severity, evidence (`evidence.observed` quoting real DDL/query with secrets redacted), recommendation, fixability (auto/proposed/advisory), and `expected_impact` (axis + confidence + magnitude, banded high|medium|low — never a fabricated %/latency/row-count).
3. End by offering: "Run `/claude-db:fix` to apply the safe, reversible changes (you confirm each one), `/claude-db:migrate` to lint a migration, or `/claude-db:next` to see what to tackle first."

Two scores, never blended. Every finding conforms to `schema/finding.schema.json` with reproducible evidence. Respond in the user's language (EN/ES).

Versions

RepositoryScoreLicence
This page · hainrixz/claude-db90MIT
marcel-bich/marcel-bich-claude-marketplace100MIT
jeremylongshore/tons-of-skills-marketplace100MIT
friendlyinternet/nuxt-crouton100MIT
userKael/rastro100MIT
Archont561/qgis-agent-harness100MIT
lilly-logic-labs/lll-skills100MIT
Come-In-Labs/agent-skills100MIT
minanyang/10x-agent100MIT

Database snapshot: 13.11.2026 · package version 604bb860c694 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100audit-db-schema
    Audit a database schema for consistency, constraints, naming, indexes, and migrations. Use when reviewing schema design. Destructive-op gates → plan-data-integrity. RLS → plan-rls-audit. Restore/RPO → plan-backup-dr.
  • 95data-storage-migrations
    Use this capability for database schema design, SQL/NoSQL selection, migrations, indexing, query review, connection pooling, backups, object storage, event storage, data retention, and data lifecycle planning. Trigger on database, schema, migration, index, SQL, PostgreSQL,…
  • 100database-design
    Database schema design and data modeling: normalization, indexing, constraints, migrations, partitioning, audit trails. Use to design or review a schema.
  • 90database-design
    Picks a database and ORM, designs schemas and indexes, plans safe migrations. Use when designing a schema, adding indexes or planning a migration.
  • 100uw-analyze-database
    Use when analyzing the database layer including schema, migrations, ORM configuration, and data access patterns
  • 100qe-database-testing
    Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance. Use when testing data persistence, ensuring referential integrity, or validating database migrations.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.