postgresql
/postgresql
Design, query, migrate, or troubleshoot a PostgreSQL-backed application. Use for schema, indexes, constraints, transactions, row-level security, query plans, extensions, or backup concerns.
- Author
- helx0071 ↗
- Repository
- skillsmo ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Design, query, migrate, or troubleshoot a PostgreSQL-backed application. Use for schema, indexes, constraints, transactions, row-level security, query plans, extensions, or backup concerns.
Original author description
Design, query, migrate, or troubleshoot a PostgreSQL-backed application. Use for schema, indexes, constraints, transactions, row-level security, query plans, extensions, or backup concerns.
How it works
- Goal
- Workflow
- Decision rules
- Boundaries
- Completion standard
- Further reading
SKILL.md preview
--- name: postgresql description: "Design, query, migrate, or troubleshoot a PostgreSQL-backed application. Use for schema, indexes, constraints, transactions, row-level security, query plans, extensions, or backup concerns." --- # PostgreSQL database workflow ## Goal Use PostgreSQL-specific behavior carefully and preserve data, access, and concurrency invariants. ## Workflow 1. Identify PostgreSQL major version, extensions, connection pool, schema conventions, isolation level, and migration tool. 2. Inspect tables, constraints, indexes, policies, query plans, and application assumptions relevant to the requested change. 3. Design the smallest SQL change and evaluate null semantics, locking, generated values, RLS, and existing data. 4. Check concurrent transactions, retryable errors, pool limits, query performance, backup, and restore implications. 5. Verify in a representative non-production database; document migration order, version assumptions, and operational risks. ## Decision rules - Match syntax and features to the deployed major version. - Use constraints and transactions to enforce invariants at the database boundary when appropriate. - Treat RLS policies as part of security behavior and test both allowed and denied roles. ## Boundaries - Do not run production DDL or data edits without explicit authorization. - Do not assume application filters replace database access policies. ## Completion standard Return the requested artifact or findings with enough evidence for a reviewer to understand what changed, what was checked, and what remains uncertain. Distinguish observed facts, inferred risks, and unverified assumptions. Keep the scope tied to the user's request. ## Further reading - [Field guide](references/field-guide.md) — use for task-specific review questions and edge cases. - [Source and rights notes](references/source-notes.md) — use when maintaining this package or reviewing its provenance.
Files in this package (3)
- SKILL.md 2 KB
- references/field-guide.md 1 KB
- references/source-notes.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · helx0071/skillsmo | 90 | MIT |
| speakeasy-api/gram | 100 | AGPL-3.0 |
| TerminalSkills/skills | 100 | Apache-2.0 |
| iliaal/whetstone | 100 | MIT |
| itechmeat/llm-code | 100 | MIT |
| claude-dev-suite/claude-dev-suite | 100 | MIT |
| yvssdheeraj/opencode-engineering-harness | 100 | MIT |
| G1Joshi/Agent-Skills | 100 | MIT |
| bcastelino/agent-skills-kit | 100 | MIT |
Database snapshot: 13.11.2026 · package version c931c1859213 (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
- 100database-engineering
Design, query, migrate, secure, and optimize relational databases, especially PostgreSQL. Use for schema design, SQL, indexes, transactions, concurrency, data integrity, backup/recovery, and production migrations. - 90mysql
Design, query, migrate, or troubleshoot a MySQL-backed application. Use when dealing with schema, indexes, transactions, isolation, replication, backups, or MySQL-specific behavior. - 90postgres-schema-rls
Use when supabase/Postgres data modeling, slow queries, RLS or schema migrations. Design PostgreSQL schemas, indexes and row-level security from explicit access contracts. Do not use when data is stored in a different engine and Postgres semantics are irrelevant. - 95postgresql-data-engineering
Design, review, troubleshoot, or improve PostgreSQL schemas, queries, transactions, migrations, pooling, security, and production recovery. Use for PostgreSQL engineering decisions; skip unrelated backend work and trivial SQL or text edits. - 100database-postgresql
Apply PostgreSQL standards for migrations, indexing, transactions, and ORM boundaries. Use when editing entities, Prisma schema, migrations, RLS, or query-performance work for PostgreSQL. - 100db-stinger
Design PostgreSQL data layers. Use for schema, indexes, migrations, query performance, ORM choice, or serverless databases. Read guides/ for the decision path.