Skills supabase-server
๐Ÿ“ฆ

supabase-server

Content revision r1 Safe โšก Contains scriptsโš™๏ธ External commands๐ŸŒ Network access๐Ÿ”‘ Env variables

Build Secure Supabase Server Endpoints

Server-side Supabase authentication and client setup can be easy to misconfigure. This skill provides current patterns for secure handlers, webhooks, adapters, and migrations.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

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

Test it

Using "supabase-server". Create a user-authenticated function that returns the current user todo list.

Expected outcome:

A Deno Edge Function design using user authentication, a context-scoped client, structured errors, and the required npm import format.

Using "supabase-server". Accept Stripe checkout webhooks and mark matching orders as paid.

Expected outcome:

  • A public handler that verifies the Stripe signature before processing events.
  • Secret configuration guidance for Stripe credentials and webhook verification.
  • A scoped database update using the administrative Supabase client.

Using "supabase-server". Update an older function that uses service-role and anonymous keys.

Expected outcome:

A migration plan mapping legacy key usage to explicit authentication modes while preserving caller verification and administrative database access.

Security Audit

Safe
v1 โ€ข 8/21/2026 Open versioned report

All 120 static alerts are false positives caused by Markdown formatting, documentation links, placeholder credentials, or legitimate server examples. SKILL.md contains no executable audit-time scripts, dynamic code construction, shell substitution, secret exfiltration, or prompt injection. Documented network and environment access is scoped to user-authored Supabase and Stripe integrations.

1
Files scanned
428
Lines analyzed
0
Review items
0
False positives ignored
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
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/supabase-supabase-server/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/supabase-supabase-server.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-server security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/supabase-supabase-server/audits/1

BibTeX citation

@techreport{supabase-supabase-supabase-server-2026, author = {supabase}, title = {supabase-server security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/supabase-supabase-server/audits/1}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "supabase-server security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "supabase" date-released: "2026-08-21" url: "https://skillstore.io/skills/supabase-supabase-server/audits/1" identifiers: - type: other value: "skillstore:supabase-supabase-server:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
91
Spec Compliance

What You Can Build

Create Edge Functions

Build authenticated Supabase Edge Functions with the correct runtime imports, clients, and platform configuration.

Add Framework Authentication

Integrate per-route Supabase authentication into Hono, Cloudflare Workers, or cookie-based server frameworks.

Modernize Existing Functions

Replace legacy keys, CDN imports, manual clients, and deprecated authentication options with current server patterns.

Try These Prompts

Create an Authenticated Function
Create a Supabase Edge Function that lists todos for an authenticated user. Use @supabase/server, user authentication, and clear error handling.
Add Hono Route Authentication
Add @supabase/server authentication to this Hono application. Protect [route] for signed-in users and preserve the existing response behavior.
Build a Verified Webhook
Design a Supabase Edge Function for [provider] webhooks. Verify the provider signature before database updates and explain required secret configuration.
Migrate a Legacy Service
Migrate this legacy Supabase server code to @supabase/server: [code]. Preserve authorization intent, update keys and imports, and identify configuration changes.

Best Practices

  • Confirm endpoint access requirements before choosing an authentication mode.
  • Keep secrets in platform secret storage and use named keys for isolated services.
  • Verify external webhook signatures before parsing events or changing database records.

Avoid

  • Do not use unauthenticated mode for sensitive reads, writes, or administrative actions.
  • Do not embed real API keys in source files, prompts, logs, or example requests.
  • Do not copy legacy auth names or environment keys into new implementations.

Frequently Asked Questions

Which runtimes does this skill cover?
It covers Supabase Edge Functions, Deno, Node.js, Cloudflare Workers, Hono, and server frameworks using @supabase/ssr.
Does it choose the authentication mode automatically?
It recommends a mode from the endpoint requirements. Public or ambiguous access should be confirmed before implementation.
Can it handle Stripe webhooks?
Yes. It uses an unauthenticated Supabase wrapper only when the handler validates the Stripe signature before processing.
Does it support server-to-server calls?
Yes. It documents secret authentication, named keys, function invocation, and database calls through pg_net and Vault.
Can it migrate legacy Edge Functions?
Yes. It maps old imports, keys, manual clients, configuration options, and authentication fields to current equivalents.
Does it configure production secrets?
No. It can provide commands and storage guidance, but users must manage real credentials through their deployment environment.

Developer Details

Author

supabase

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

e152e69d5b5fda6735649f4334cb64b82e1ba84e

Maintenance freshness

8/21/2026

Usage

0 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md

More from supabase

View all
View all