pg-auditor
Audits PostgreSQL schemas for risky defaults, missing indexes, and partitioning foot-guns — and writes the fix-it SQL.
who says so, and how do I check? →
scan — this publisher's server ran static analysis
(skillspector@2.5.1 (static)) for the shapes that make skills dangerous (hidden
instructions, data exfiltration, credential access) before publishing. After purchase,
npx allodic verify re-runs the same scan on your
copy, on your machine.
benchmarks — test runs bound cryptographically to this exact
version. After purchase, reproduce them yourself:
npx allodic verify https://demo.allodic.dev --evals. Because claims are
signed, a claim that fails reproduction is portable proof of fraud —
and a full refund revokes the license.
signed release — attested by the publisher's own key (self-hosted servers are publisher-attested, like any indie store). Your install pins this key; a future update signed by a different key is refused. Registry-attested listings — scans and benchmarks run and signed by an independent registry — are also possible in this format.
What it checks
- Risky column defaults and nullable foreign keys
- Missing or redundant indexes, with
CREATE INDEXsuggestions - Partitioning foot-guns before they bite at 100M rows
How agents use it
Point your agent at a schema dump or a live connection string; the skill produces an audit report and ready-to-review SQL migrations.