Skills postgres-best-practices
📦

postgres-best-practices

v1.0.0 Content revision r1 Safe ⚡ Contains scripts🌐 Network access⚙️ External commands

Optimize Postgres Queries and Schemas

Slow queries and unsafe database patterns are hard to catch during ordinary code review. This skill gives Claude, Codex, and Claude Code structured Postgres guidance for indexes, RLS, pooling, transactions, and diagnostics.

Supports: Claude Codex Code(CC)
🥈 80 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "postgres-best-practices" from https://skillstore.io/skills/sickn33-postgres-best-practices.md and its manifest at https://skillstore.io/api/skills/sickn33-postgres-best-practices/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-postgres-best-practices.md Signed manifest GET /api/skills/sickn33-postgres-best-practices/manifest Signed lockfile GET /api/skills/sickn33-postgres-best-practices/lockfile

Test it

Using "postgres-best-practices". A query filters orders by status and created date but only has separate single-column indexes.

Expected outcome:

  • Recommend one composite index with equality columns before range columns.
  • Explain why separate indexes may require extra bitmap and table work.
  • Suggest validation with a real execution plan on representative data.

Using "postgres-best-practices". A Supabase policy checks the current user directly on each row of a large table.

Expected outcome:

  • Recommend evaluating the current user once per statement.
  • Confirm an index exists on the policy column used for filtering.
  • Flag complex membership checks for a reviewed helper function.

Using "postgres-best-practices". A worker queue selects the oldest pending job, and multiple workers block each other.

Expected outcome:

  • Recommend a non-blocking locked-row claim pattern for parallel workers.
  • Prefer one claim-and-update operation that returns the selected job.
  • Keep the transaction short to reduce lock contention.

Security Audit

Safe
v4 • 7/7/2026 Open versioned report

Static analysis reported many suspicious patterns, but review found they are SQL examples, Markdown formatting, and documentation links. No executable scripts, network clients, command execution, credential access, exfiltration behavior, or prompt-injection instructions were found. The remaining operational risk is that users should review administrative SQL before applying it to production databases.

37
Files scanned
3,490
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚡ Contains scripts (4)
AGENTS.md:1084 AGENTS.md:1087 rules/data-batch-inserts.md:44 rules/data-batch-inserts.md:47
🌐 Network access (6)
metadata.json:7 metadata.json:8 metadata.json:9 metadata.json:10 metadata.json:11 rules/_contributing.md:151
⚙️ External commands (11)
README.md:101-119 SKILL.md:30 SKILL.md:31 SKILL.md:32 SKILL.md:33 SKILL.md:34 SKILL.md:35 SKILL.md:36 SKILL.md:37 SKILL.md:43-47 SKILL.md:47-59
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-postgres-best-practices/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-postgres-best-practices/security.svg)](https://skillstore.io/skills/sickn33-postgres-best-practices?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-postgres-best-practices?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-postgres-best-practices/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-postgres-best-practices.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). postgres-best-practices security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/sickn33-postgres-best-practices/audits/4

BibTeX citation

@techreport{sickn33-sickn33-postgres-best-practices-2026, author = {sickn33}, title = {postgres-best-practices security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/sickn33-postgres-best-practices/audits/4}, note = {Author version 1.0.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "postgres-best-practices security audit report (audit version 4)" version: "1.0.0" type: report authors: - name: "sickn33" date-released: "2026-07-07" url: "https://skillstore.io/skills/sickn33-postgres-best-practices/audits/4" identifiers: - type: other value: "skillstore:sickn33-postgres-best-practices:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
100
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Review a slow query before release

Check filters, joins, pagination, and selected columns against Postgres indexing rules before merging application code.

Design a scalable tenant schema

Plan primary keys, RLS policies, foreign key indexes, partitioning, and data types for a multi-tenant product.

Improve Supabase operational settings

Review connection pooling, idle timeouts, prepared statements, and monitoring queries for a growing Supabase workload.

Try These Prompts

Check one query 
Review this Postgres query for performance problems. Identify missing indexes, inefficient filters, and safer alternatives. Explain each recommendation briefly.
Review a schema migration 
Review this Postgres migration for data type choices, primary keys, foreign key indexes, naming, and future scaling risks. Suggest precise migration changes.
Optimize RLS policies 
Review these Supabase RLS policies for security and performance. Check function calls, indexes, policy scope, and least-privilege access.
Create a production tuning plan 
Build a prioritized Postgres tuning plan from these queries, schema notes, and workload constraints. Include indexes, pooling, transactions, monitoring, and rollout risks.

Best Practices

  • Validate recommendations with execution plans and representative production-like data.
  • Prioritize indexes for frequent filters, joins, ordering, and RLS policy columns.
  • Review administrative SQL in a staging environment before applying it to production.

Avoid

  • Adding separate single-column indexes for every multi-column query without checking column order.
  • Using application-only tenant filters instead of database-enforced RLS policies.
  • Keeping transactions open while external API calls or long application work runs.

Frequently Asked Questions

Does this skill run SQL against my database?
No. It provides review guidance and examples. You decide what to run in your environment.
Is it specific to Supabase?
It includes Supabase RLS and pooling guidance, but most query and schema advice applies to Postgres.
Can it replace EXPLAIN ANALYZE?
No. Use it to form hypotheses, then verify plans and timings with EXPLAIN ANALYZE.
Does it cover security?
Yes. It includes least privilege, RLS basics, and RLS performance patterns.
Can beginners use it?
Yes. The prompts can ask for short explanations and concrete migration or query changes.
What should I review before applying examples?
Check privileges, lock impact, data volume, Postgres version, and rollback plans before production changes.

Developer Details

Author

sickn33

License

MIT

Author version

v1.0.0

Skillstore revision

r1

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/postgres-best-practices

Ref

816c62b2546ddb1c6a0453e7c781b5e095117819

Maintenance freshness

7/18/2026

Usage

10 downloads · 117 views

File structure

📁 rules/

📄 _contributing.md

📄 _sections.md

📄 _template.md

📄 advanced-full-text-search.md

📄 advanced-jsonb-indexing.md

📄 conn-idle-timeout.md

📄 conn-limits.md

📄 conn-pooling.md

📄 conn-prepared-statements.md

📄 data-batch-inserts.md

📄 data-n-plus-one.md

📄 data-pagination.md

📄 data-upsert.md

📄 lock-advisory.md

📄 lock-deadlock-prevention.md

📄 lock-short-transactions.md

📄 lock-skip-locked.md

📄 monitor-explain-analyze.md

📄 monitor-pg-stat-statements.md

📄 monitor-vacuum-analyze.md

📄 query-composite-indexes.md

📄 query-covering-indexes.md

📄 query-index-types.md

📄 query-missing-indexes.md

📄 query-partial-indexes.md

📄 schema-data-types.md

📄 schema-foreign-key-indexes.md

📄 schema-lowercase-identifiers.md

📄 schema-partitioning.md

📄 schema-primary-keys.md

📄 security-privileges.md

📄 security-rls-basics.md

📄 security-rls-performance.md

📄 AGENTS.md

📄 metadata.json

📄 README.md

📄 SKILL.md