skills.rest
sudarshan-krishnan
sudarshan-krishnanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

clerk-chrome-extension-patterns

Implement Clerk authentication in Chrome extensions with syncHost and message passing.

Updated Jun 20, 2026
Search Tags:#authentication#clerk#chrome-extension#service-worker#content-scripts#plasmo#synchost
One-click install
npx skills add https://github.com/sudarshan-krishnan/Sentinel_AIHackathon_Berkley_2026 --skill clerk-chrome-extension-patterns-sudarshan-krishnan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clerk-chrome-extension-patterns
Source: https://github.com/sudarshan-krishnan/Sentinel_AIHackathon_Berkley_2026/tree/main/app/.agents/skills/clerk-chrome-extension-patterns
Command: npx skills add https://github.com/sudarshan-krishnan/Sentinel_AIHackathon_Berkley_2026 --skill clerk-chrome-extension-patterns-sudarshan-krishnan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers implement secure and reliable Clerk authentication in Chrome extensions, avoiding broken redirects, stale sessions, and unsupported auth flows.

Core Features & Use Cases

  • Popup and side panel authentication with publishable keys and redirect-safe flows.
  • Background service worker token access using createClerkClient with fresh sessions.
  • syncHost-based web app synchronization for OAuth, SAML, magic links, and headless extensions.
  • Content script auth via message passing to the background page.
  • Stable CRX ID setup and token caching so auth survives rebuilds and popup closes.
  • Use case: build a Plasmo extension that signs users in, reads session tokens in the background, and mirrors web-app sign-in state without manual re-login.

Quick Start

Ask for a Chrome extension auth implementation using ClerkProvider, safe redirect URLs, and the correct popup, background, and syncHost patterns for your app.

Frequently Asked Questions about clerk-chrome-extension-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Clerk authentication in a Chrome extension service worker?▼

Clerk authentication in a Chrome extension service worker requires using createClerkClient to access fresh session tokens. This pattern ensures the background service worker reliably makes authenticated requests and reads session tokens even when the extension popup is closed.

How do I sync Clerk auth sessions between a Chrome extension and a web app?▼

To sync Clerk auth sessions between a Chrome extension and a web app, configure the syncHost property within your ClerkProvider setup. This syncHost-based synchronization mirrors web-app sign-in state, supporting OAuth, SAML, and magic links without manual re-login.

Why are my Clerk OAuth redirects broken in a Chrome extension popup?▼

Broken Clerk OAuth redirects in a Chrome extension popup usually stem from incorrect redirect URL configurations. Using the correct ClerkProvider setup with redirect-safe URLs and ensuring a stable CRX ID prevents broken redirects and ensures authentication flows complete successfully.

How do I get session tokens in a Chrome extension content script using Clerk?▼

To get session tokens in a Chrome extension content script using Clerk, implement message passing to the background service worker. The content script sends a message to the background page, which retrieves the authenticated session token via createClerkClient.

Does Clerk authentication work with Plasmo Chrome extensions?▼

Yes, Clerk authentication works with Plasmo Chrome extensions. You can build a Plasmo extension that signs users in, reads session tokens in the background service worker, and mirrors web-app sign-in state using correct ClerkProvider and syncHost patterns.

Why does my Chrome extension lose its Clerk session after rebuilding?▼

A Chrome extension loses its Clerk session after rebuilding due to an unstable CRX ID. Configure a stable CRX ID and implement token caching so that your authentication state survives rebuilds, popup closures, and background service worker restarts.

Related Skills

Explore More Software Engineering Skills→
Aditya07024Aditya07024

clerk-chrome-extension-patterns

Implement Clerk authentication patterns for Chrome extensions with popup and service worker workflows.

Community
Advanced
JoshkovuJoshkovu
1

clerk-chrome-extension-patterns

Configure Clerk authentication across Chrome extension UI, service workers, and content scripts.

Community
Advanced
jinwoonghongjinwoonghong

moai-platform-chrome-extension

Develop Chrome extensions using Manifest V3 service workers and content scripts.

Community
Advanced
clerkclerk
66

clerk-chrome-extension-patterns

Authenticate Chrome extension users with Clerk across popup, background, and content-script contexts.

Official
Advanced