Skip to content
Agentmart
Submit a tool

adapter-supabase

Supabase adapter guidance for client/server key separation, policy-aware data access, and auth integration.

Skill by JahacksV1

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/jahacksv1-adapter-supabase

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Supabase adapter guidance for client/server key separation, policy-aware data access, and auth integration. Use when touching Supabase clients, queries, or policies.

Use cases: backend, data, security

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/adapter-supabase

What's inside

Skill name
adapter-supabase
Description
Supabase adapter guidance for client/server key separation, policy-aware data access, and auth integration. Use when touching Supabase clients, queries, or policies.
License
MIT
Instructions
29 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Adapter: Supabase

## Focus

- Correct use of anon vs service-role credentials.
- RLS-aware query and policy patterns.
- Clear separation of client and server responsibilities.

## Starter Checklist

- [ ] Secret keys remain server-only.
- [ ] Data access path respects auth and policy boundaries.
- [ ] Policy impact considered for new queries/mutations.
- [ ] Environment variable names and scopes are documented.

## Implementation Pattern

Evidence: 4-repo field extraction — this was the single strongest, most unanimous signal across
the whole dataset. See `.ai/MERGE_REPORT.md`.

- Split Supabase clients by runtime/privilege context (anonymous/browser vs. server vs.
  admin/service-role); never reuse a browser-scoped client for server-side privileged
  operations.
- Keep raw `supabase.from(...)` table access inside a service/persistence layer, not scattered
  through UI components or route handlers directly.

If the current project already has an established pattern for either of these, follow the
existing pattern instead of this default.

From JahacksV1/day-one-agent-kit, MIT.

More from JahacksV1/day-one-agent-kit

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jul 13, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from JahacksV1

Cite this page

adapter-supabase skill. Agent Mart. https://agentmart.dev/skills/jahacksv1-adapter-supabase (last updated 2026-10-24)