Skip to content
TrustedSkillsbeta
Back to all skills

Supabase Postgres Best Practices

Official
supabase·vlatest·database·MIT

Official supabase skill covering Supabase, PostgreSQL, best practices for working with databases and data persistence.

Repositoryskills.sh

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add supabase/agent-skills --skill supabase-postgres-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

supabase

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned supabase/agent-skills at 544bfc56c8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
544bfc56c8
Manifest
skills/supabase-postgres-best-practices/SKILL.md
Scanned
36 files, 1,826 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides best practices for working with Supabase and PostgreSQL, including schema design, query optimization, security configurations, and efficient use of Supabase's features like real-time subscriptions and row-level security.

When to use it

  • Designing a database schema for a new application using Supabase.
  • Optimizing slow queries in an existing Supabase project.
  • Setting up secure access controls with row-level security policies.
  • Implementing real-time data synchronization between clients and the database.

Key capabilities

  • Guidance on efficient PostgreSQL schema design.
  • Tips for optimizing query performance.
  • Best practices for configuring row-level security.
  • Recommendations for using Supabase's real-time features effectively.
  • Security considerations for production environments.

Example prompts

  • "How can I optimize my PostgreSQL queries in Supabase?"
  • "What are the best practices for setting up row-level security in Supabase?"
  • "Can you explain how to use real-time subscriptions with Supabase?"

Tips & gotchas

  • Ensure your PostgreSQL version is compatible with Supabase's supported versions.
  • Always test query performance in a staging environment before deploying to production.