Ponytail SQL Objects — Security skill for Claude Code
This skill makes Claude write SQL Server objects the way this project requires — the audit columns, the soft delete, the naming, the header blocks, the descriptions — without you having to restate the.
How to install Ponytail SQL Objects
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open roscoesincero-MDE/ponytail-sql-objects and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Ponytail SQL Objects does
This skill makes Claude write SQL Server objects the way this project requires — the audit columns, the soft delete, the naming, the header blocks, the descriptions — without you having to restate the rules each time. It also installs and checks the change logging that records who altered which database object.
Alternatives in Security
- Migration Agent — Plans a token migration (format, tool, naming or tier): chains token-audit and naming-audit, builds the transf 194 ★
- Postgres — Execute safe read-only SQL queries against PostgreSQL databases with multi-connection support and defense-in-d 159 ★
- Site Metadata — Audit and refresh the docs site's SEO/social metadata (descriptions, keywords, OG cards, JSON-LD) and verify t 76 ★
README
How to use this skill
This skill makes Claude write SQL Server objects the way this project requires — the audit columns, the soft delete, the naming, the header blocks, the descriptions — without you having to restate the rules each time. It also installs and checks the change logging that records who altered which database object.
You do not run this skill. You just ask for what you want, and it applies.
1. Install it (once)
The folder must be named after the skill, and it goes in one of two places.
**For this project only:**
\.claude\skills\ponytail-sql-objects\
**For every project on this machine:**
C:\Users\\.claude\skills\ponytail-sql-objects\
Copy this whole folder there and rename the copy to `ponytail-sql-objects` — `SKILL.md`, `templates\`, `scripts\` and `references\` must all sit inside it. Then restart Claude Code. Type `/skills` to confirm `ponytail-sql-objects` is listed.
That is the entire installation. Nothing to configure, no dependencies.
2. Use it (just ask)
Ask in plain language. The skill loads by itself when the request touches SQL objects.
| Say something like | You get |
|---|---|
"Add a Permit table to dbo" |
A guarded CREATE TABLE with all 7 audit columns, DF_dbo_Permit_* constraint names, a filtered unique index, an AFTER UPDATE trigger that maintains the audit columns, and a description on the table and every column |
"Add a PermitStatus column to dbo.Permit" |
A separate guarded ALTER TABLE ... ADD block — it will not edit the original CREATE TABLE |
"Write a view over dbo.Permit" |
A CREATE OR ALTER VIEW with the header block and WHERE IsDeleted = 0 |
| "Write a procedure that merges the permit batch" | A procedure with the header block, TRY/CATCH, the logs.ExecutionLog instrumentation, and a bare ;THROW; |
| "Does this database record its schema changes?" | The read-only check script, and what to do about anything missing |
| "Set u |
Related Skills
Pbi Audit Fix
Autonomous audit-then-fix pipeline — scan the TMDL/TMSL model, auto-fix WARN-level issues (missing description
Pbi Audit
Run a comprehensive 21-rule health check across 8 domains: relationships, naming, date table, measure quality,
Arbitus
Open-source security gateway for MCP tool calls — blocks secret leaks, enforces agent policies, and requires h
Cc Cache Audit
A/B test proving Claude Code's billing header breaks cross-session prompt cache sharing. One env var fix saves
Yakos
Multi-runtime agent framework (Claude Code, Codex, Antigravity) with hard/soft controls, audit-first hooks, an
Ponytail Audit
Audit the whole repo for over-engineering, what can be deleted
Related Agents
Ponytail Review
Cold over-engineering reviewer. Spawned by parallel workflows when non-test source changes, to find what to de
Integrity Reviewer
Reviews Kulturní Přehled changes against what must never silently break — the sync invariants (change_log seq,
Cleanup Phase 1
Runs phase 1 (dead code) and phase 1.5 (duplicate functions) of a codebase cleanup that is already under way.