Skills supabase

📦

supabase

Name: supabase
Author: supabase

v0.1.0 Content revision r1 Safe 🌐 Network access📁 Filesystem access⚙️ External commands

Build Supabase Apps Safely

Supabase projects change quickly, and outdated guidance can create database or auth defects. This skill directs Claude, Codex, and Claude Code to verify docs, use safe workflows, and check Supabase security concerns.

Supports: Claude Codex Code(CC)

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

Test it

Using "supabase". A user asks how to add private project notes.

Expected outcome:

The assistant verifies current Supabase docs, recommends RLS for project membership, and lists tests for allowed and denied access.

Using "supabase". A user reports that the MCP server is unavailable.

Expected outcome:

The assistant checks the official server URL, expects an unauthorized response without a token, then guides OAuth troubleshooting.

Using "supabase". A user needs a database migration.

Expected outcome:

The assistant proposes an iterative SQL workflow, runs advisors when available, and creates a reviewed migration after verification.

Security Audit

Safe

v5 • 7/7/2026 Open versioned report

All static findings were false positives after contextual review. The high path traversal flag is a relative Markdown link, and the external command flags are Markdown examples or legitimate Supabase guidance. No prompt injection, malicious exfiltration, or hidden override intent was found.

Files scanned

141

Lines analyzed

Review items

False positives ignored

Risk Factors

🌐 Network access (6)

references/skill-feedback.md:16 SKILL.md:45 SKILL.md:62 SKILL.md:66 SKILL.md:71 SKILL.md:75

📁 Filesystem access (2)

references/skill-feedback.md:9 SKILL.md:71

⚙️ External commands (26)

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/supabase-supabase/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/supabase-supabase.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

supabase. (2026). supabase security audit report (audit version 5) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/supabase-supabase/audits/5

BibTeX citation

@techreport{supabase-supabase-supabase-2026,
  author = {supabase},
  title = {supabase security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/supabase-supabase/audits/5},
  note = {Author version 0.1.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 security audit report (audit version 5)"
version: "0.1.0"
type: report
authors:
  - name: "supabase"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/supabase-supabase/audits/5"
identifiers:
  - type: other
    value: "skillstore:supabase-supabase:audit:5"
    description: "Skillstore immutable audit report identifier"

Compare variants

3 installable variants

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

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

supabase Recommended Current

supabase-supabase

Skillstore Score 81

Evidence Confidence High

Skillstore usage 10

Updated

2026-08-21

Acurioustractor

acurioustractor-supabase

Skillstore Score 78

Evidence Confidence High

Skillstore usage 13

Updated

2026-08-21

Dicklesworthstone

dicklesworthstone-supabase

Skillstore Score 70

Evidence Confidence High

Skillstore usage 8

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Plan a secure Supabase feature

Use current docs and security checks before adding auth, storage, database, or realtime behavior.

Troubleshoot MCP and CLI access

Check Supabase CLI versions, MCP reachability, OAuth setup, and fallback options.

Review database changes

Evaluate RLS, views, functions, policies, advisors, and migration readiness before committing schema changes.

Try These Prompts

Check Supabase Documentation

I am adding a Supabase feature. Identify the current docs I should verify first, then summarize the safest implementation path.

Debug Auth or Sessions

Help debug this Supabase auth issue. Check session handling, JWT freshness, metadata usage, and any RLS policies involved.

Plan a Schema Migration

Plan a Supabase schema change. Use an iterative workflow, list verification steps, and explain when to generate the migration.

Audit Security-Sensitive Changes

Audit these Supabase changes for RLS, views, privileged functions, storage policies, API keys, and migration risks.

Best Practices

Verify current Supabase docs before implementing feature-specific guidance.
Review RLS, keys, views, storage policies, and JWT claims before changing user data paths.
Use local verification and advisors before committing migrations.