Sign up
← all tools

cc-skill:clerk-supabase-jwt-bridge

Claude Code skill · anthropic · active

0
last 30 days
0 calls
0 of 30 days active
explain like I am new to this
what it does

This skill sets up authentication where Clerk handles user login and signup, while Supabase stores the data and enforces access rules. It bridges the two services so that Supabase knows which Clerk user is making requests and can lock down tables accordingly.

who it is for

Jay, or any founder building a Next.js app who wants strong, database-level security without managing two separate authentication systems.

when it fires

When you mention Clerk, Supabase, JWT, RLS policies, or authentication setup in Jay's projects.

say something like
  • "How do I connect Clerk to Supabase for this app?"
  • "Set up RLS policies so only the logged-in user can see their own data"
  • "My Supabase RLS policies aren't recognizing Clerk users"
what you might get back
The skill outputs the exact configuration steps: how to create a Clerk JWT template, point Supabase to Clerk's signing keys, pass the JWT token from your Next.js app to Supabase on each request, and write database policies like 'user_id = auth.jwt() ->> sub' so Supabase automatically blocks unauthorized queries.
how to know it worked

You'll know it worked when you can query Supabase from your app, the request includes the Clerk user ID, and your RLS policies correctly allow or block rows based on the logged-in user.

is this skill working for me
never used
cloud runs
0
0 deployments
local fires
0
Claude Code (optional)
posts published
0
from drafts
attributed
$0.00
signups + revenue
Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/clerk-supabase-jwt-bridge/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when setting up Clerk authentication with Supabase database access, configuring RLS policies that read Clerk JWTs, or debugging auth flow issues in Jay's projects. Triggers on "Clerk", "Clerk Supabase", "JWT bridge", "auth setup", "RLS

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/clerk-supabase-jwt-bridge/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity
never used
2026-04-03today
cost model
unitincluded
capabilities
{
  "source": "global",
  "description": "Use this skill when setting up Clerk authentication with Supabase database access, configuring RLS policies that read Clerk JWTs, or debugging auth flow issues in Jay's projects. Triggers on \"Clerk\", \"Clerk Supabase\", \"JWT bridge\", \"auth setup\", \"RLS with Clerk\", \"auth.jwt()\", or any authentication architecture work. Provides the exact configuration for Jay's standard Clerk + Supabase pattern."
}
how it gets called
{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/clerk-supabase-jwt-bridge/SKILL.md"
}
This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.