Skip to content
TrustedSkillsbeta
Back to all skills

Supabase Clerk Sync

Listed
vanman2024·vlatest·database

Synchronizes user data between your Supabase database and Clerk authentication seamlessly using vanman2024's skill.

Repository

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 vanman2024/ai-dev-marketplace --skill supabase-clerk-sync -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

vanman2024

Taken from the source listing. We haven't verified who controls this account.

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 7 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.clerk.com, app.supabase.com, clerk.your-domain.clerk.accounts.dev, clerk.your-domain.com, dashboard.clerk.com….

    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.

    Hosts contacted

    deno.landundeclaredesm.shundeclareddashboard.clerk.comundeclaredclerk.your-domain.clerk.accounts.devundeclaredclerk.your-domain.comundeclaredapp.supabase.comundeclaredapi.clerk.comundeclared

    What it found (3 of 13)

    • plugins/clerk/skills/supabase-clerk-sync/scripts/create-webhooks.sh:43contacts deno.land
      import { serve } from "https://deno.land/[email protected]/http/server.ts"
    • plugins/clerk/skills/supabase-clerk-sync/templates/edge-function-webhook.ts:14contacts deno.land
      import { serve } from 'https://deno.land/[email protected]/http/server.ts'
    • plugins/clerk/skills/supabase-clerk-sync/scripts/create-webhooks.sh:44contacts esm.sh
      import { createClient } from "https://esm.sh/@supabase/supabase-js@2"

  • 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 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 vanman2024/ai-dev-marketplace at 35f1f5a5fb.

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

Commit
35f1f5a5fb
Manifest
plugins/clerk/skills/supabase-clerk-sync/SKILL.md
Scanned
18 files, 4,080 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 synchronizes user data between Supabase and Clerk. It handles the transfer of user profiles, sessions, and potentially other relevant information to ensure consistency across both platforms. This integration streamlines authentication workflows and simplifies user management for applications utilizing both services.

When to use it

  • New application setup: When building a new application that uses both Supabase for its backend database and Clerk for authentication.
  • Migrating from another auth provider: If you're switching from a different authentication system to Clerk while retaining data in Supabase.
  • Maintaining data consistency: To ensure user profiles are accurately reflected in both systems, especially after updates or modifications.

Key capabilities

  • Synchronizes user profile information between Supabase and Clerk.
  • Manages user sessions across platforms.
  • Automates data transfer for new users.
  • Handles updates to existing user data.

Example prompts

  • "Sync all new users created in Supabase with their profiles to Clerk."
  • "Update the email address of user '[email protected]' in both Supabase and Clerk."
  • “Ensure that any changes made to a user’s profile in Clerk are reflected in Supabase.”

Tips & gotchas

The skill requires proper configuration of both your Supabase project and your Clerk application for authentication keys and database connections. Verify the data mapping between the two platforms to avoid unexpected discrepancies.