clerk-backend-apis
This skill guides you through authenticating and authorizing incoming requests on backend services using Clerk's SDKs and middleware. It covers request flow, token verification, cross-origin patterns, proxy header preservation, and Backend API client usage across Node, Go, Python, Ruby, Java, C#, and PHP frameworks.
Clerk Backend APIs helps you authenticate incoming backend requests using Clerk tokens and middleware across multiple frameworks.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-06-18
Clerk Backend APIs helps you authenticate incoming backend requests using Clerk tokens and middleware across multiple frameworks. This skill guides you through authenticating and authorizing incoming requests on backend services using Clerk's SDKs and middleware. It covers request flow, token verification, cross-origin patterns, proxy header preservation, and Backend API client usage across Node, Go, Python, Ruby, Java, C#, and PHP frameworks.
Use it when
- clerk-backend-apis guides you through implementing authorization checks for protected API resources and actions.
- clerk-backend-apis covers CORS configuration and Bearer token handling for cross-origin requests.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
JosiahSiegel/claude-plugin-marketplace/clerk-backend-apis · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I authenticate requests in Node.js with Clerk?
clerk-backend-apis provides middleware and SDK patterns for Node.js frameworks. In Express, use the Clerk middleware to automatically verify Bearer tokens in the Authorization header and attach user/session context to the request object. For other frameworks like Fastify, Clerk offers framework-specific plugins that follow the same token-verification flow. The middleware validates Clerk session tokens, checks their expiration, and rejects unauthenticated requests with 401 responses.
What does clerk-backend-apis cover for authorization?
clerk-backend-apis guides you through implementing authorization checks for protected API resources and actions. After authentication verifies the user's identity via token validation, authorization determines what that user can access. The skill covers role-based access control patterns, permission checks, and organization-level authorization using Clerk's Backend API client for server-side user and organization operations.
How should I handle cross-origin API calls with Clerk tokens?
clerk-backend-apis covers CORS configuration and Bearer token handling for cross-origin requests. When frontend clients make requests to backend APIs from different origins, include the Clerk session token in the Authorization header as a Bearer token. Configure your backend's CORS policy to accept requests from your frontend domain, and ensure the Clerk middleware validates the Bearer token before processing the request.
What authentication patterns does clerk-backend-apis support?
clerk-backend-apis supports authentication across Node, Go, Python, Ruby, Java, C#, and PHP frameworks. It covers standard Bearer token validation, middleware-based request authentication, Backend API client setup for server-side operations, machine-to-machine authentication, and webhook signature verification. Each framework has language-specific examples and SDK guidance for integrating Clerk's authentication into your backend service.
How do I debug authentication failures with proxies and forwarded headers?
clerk-backend-apis addresses debugging authentication failures in proxies, CDNs, and forwarded header scenarios. When requests pass through reverse proxies or load balancers, ensure the Authorization header containing the Clerk token is preserved and forwarded to your backend. Check that proxy configurations don't strip or modify headers, and verify that your backend correctly reads tokens from the Authorization header rather than expecting them in cookies.
What's included in the clerk-backend-apis integration checklist?
clerk-backend-apis provides a backend integration checklist covering token verification setup, middleware configuration for your framework, CORS and cross-origin handling, Bearer token validation, authorization pattern implementation, Backend API client initialization, error handling for 401/403 responses, and proxy header preservation. The skill is licensed under MIT and guides you through each step to secure your backend API endpoints.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Clerk Backend APIs
Overview
Use this skill for Clerk authentication in backend services, API servers, workers, and server-to-server integrations. The key responsibilities are authenticating incoming requests, enforcing authorization on server resources, safely using the Backend API, and making cross-origin token behavior explicit.
Prefer official Clerk SDKs and middleware when available. When the target runtime lacks a first-class Clerk framework SDK, use Clerk-documented token verification and Backend API patterns rather than ad hoc JWT
(truncated - see the full file via the links below)
File tree — 1 file
plugins/clerk-auth-master/skills/clerk-backend-apis/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Authenticate incoming backend requests using Clerk tokens and middleware”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Master Clerk authentication in React Router v7 and v8 apps with server-side loaders, middleware integration, and protected route patterns. This skill covers rootAuthLoader setup, getAuth usage in loaders and actions, client-side hooks, organization switching, and common SSR pitfalls specific to each React Router version.
Build event-driven features by listening to Clerk authentication and organization events through webhooks. Verify every webhook using the framework-specific verifyWebhook function, then sync data to your database, send notifications, or trigger downstream integrations. Complete working examples show how to handle user lifecycle events, organization membership changes, and multi-service workflows like welcome emails and Slack alerts.
Clerk Validator audits your authentication implementation for modern Clerk patterns and deprecated code. It checks package versions, proxy.ts setup, ClerkProvider configuration, auth imports, and environment variables—catching issues before they reach production. Run it during setup, after AI-generated code, or in CI/CD pipelines.
Master authentication in Nuxt 3 by implementing Clerk across middleware, composables, and server routes. This skill covers route protection with built-in auth middleware, server-side auth via Nitro routes, and client-side reactive auth state with useAuth and useUser. Avoid common pitfalls like hydration mismatches and environment variable configuration errors.
Integrate Clerk's authentication system into Next.js 16 applications via proxy.ts configuration, environment setup, and ClerkProvider integration. Protect routes, access user data in server and client components, and migrate from Next.js 15's middleware.ts pattern. Includes MCP server setup for AI agent integration.
This skill guides frontend integration of Clerk authentication across React, Vue, Nuxt, Astro, Expo, and plain JavaScript. Learn SDK selection for your framework, provider setup with publishable keys, prebuilt component patterns, and custom flow state management. Covers token fetching for cross-origin APIs, CORS and cookie handling, routing guards, organization switching, and the critical distinction between client-side presentation state and server-side authorization.