Skills supabase-postgres-best-practices

📦

supabase-postgres-best-practices

Name: supabase-postgres-best-practices
Author: sickn33

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

Optimize Postgres with Supabase Practices

Postgres performance problems often come from missing indexes, weak RLS policies, and poor connection management. This skill gives Supabase-aligned rules for improving queries, schema design, and database operations.

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 "supabase-postgres-best-practices" from https://skillstore.io/skills/sickn33-supabase-postgres-best-practices.md and its manifest at https://skillstore.io/api/skills/sickn33-supabase-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-supabase-postgres-best-practices.md Signed manifest GET /api/skills/sickn33-supabase-postgres-best-practices/manifest Signed lockfile GET /api/skills/sickn33-supabase-postgres-best-practices/lockfile

Test it

Using "supabase-postgres-best-practices". A query filters orders by customer and status, then sorts by creation date.

Expected outcome:

The skill recommends a composite index that starts with equality filters and ends with the range or sort column. It also suggests checking the plan with EXPLAIN ANALYZE.

Using "supabase-postgres-best-practices". A Supabase app uses RLS policies that call authentication helpers directly.

Expected outcome:

The skill explains why repeated function calls can slow large scans and recommends cached policy expressions plus indexes on policy columns.

Using "supabase-postgres-best-practices". A table stores hundreds of millions of time-stamped events.

Expected outcome:

The skill recommends range partitioning by time, smaller local indexes, and retention through partition drops after validation.

Security Audit

Safe

v4 • 7/7/2026 Open versioned report

AI adjudication found the static alerts are documentation examples, Markdown formatting, or reference URLs rather than executable behavior. No evidence found for malicious prompt injection, secret access, unauthorized command execution, or data exfiltration intent.

Files scanned

3,485

Lines analyzed

Review items

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:28 SKILL.md:29 SKILL.md:30 SKILL.md:31 SKILL.md:32 SKILL.md:33 SKILL.md:34 SKILL.md:35 SKILL.md:41-45 SKILL.md:45-57

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

Copy report link

https://skillstore.io/skills/sickn33-supabase-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-supabase-postgres-best-practices/security.svg)](https://skillstore.io/skills/sickn33-supabase-postgres-best-practices?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-supabase-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). supabase-postgres-best-practices security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/sickn33-supabase-postgres-best-practices/audits/4

BibTeX citation

@techreport{sickn33-sickn33-supabase-postgres-best-practices-2026,
  author = {sickn33},
  title = {supabase-postgres-best-practices security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/sickn33-supabase-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: "supabase-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-supabase-postgres-best-practices/audits/4"
identifiers:
  - type: other
    value: "skillstore:sickn33-supabase-postgres-best-practices:audit:4"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

supabase Recommended

supabase-supabase-postgres-best-practices

Skillstore Score 80

Evidence Confidence High

Skillstore usage 17

Updated

2026-08-21

sickn33 Current

sickn33-supabase-postgres-best-practices

Skillstore Score 80

Evidence Confidence High

Skillstore usage 12

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Review Slow Queries

Identify likely missing indexes, bad pagination, and inefficient joins before changing production SQL.

Design Multi-Tenant Schemas

Apply RLS, foreign key indexes, and least privilege patterns for Supabase applications.

Prepare Database Scaling Work

Plan pooling, partitioning, and diagnostic checks before traffic growth or data migration.

Try These Prompts

Check a Query

Review this Postgres query for missing indexes, bad filters, and safer pagination. Explain the top improvements in priority order.

Review a Schema

Review this table design for data types, primary keys, foreign key indexes, and partitioning opportunities. Include tradeoffs for each recommendation.

Optimize Supabase RLS

Analyze these Supabase RLS policies for security and performance. Look for per-row function calls, missing indexes, and least privilege gaps.

Plan a Performance Audit

Create a prioritized Postgres audit plan for this workload. Cover query plans, pooling, transactions, maintenance, and monitoring checks.

Best Practices

Validate each recommendation with EXPLAIN ANALYZE on representative data before shipping.
Index foreign keys and policy columns when they appear in frequent joins or RLS predicates.
Keep transactions short and use pooling settings that match the deployment model.