Clerk Enterprise RbacSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: clerk-enterprise-rbac description: 'Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations". ' allowed-tools: Read, Write, Edit, Grep version: 1.15.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - clerk - rbac - enterprise - organizations compatibility: Designed for Claude Code --- # Clerk Enterprise RBAC ## Overview Implement enterprise-grade role-based access control, organization management, and SSO with Clerk. Covers custom roles and permissions, organization lifecycle, multi-tenant access patterns, SAML/OIDC SSO, and the Backend API for programmatic role management (released Nov 2025). ## Prerequisites - Clerk Pro or Enterprise plan (Organizations + SSO require paid plan) - Organizations feature enabled in Clerk Dashboard > Organizations > Settings - Next.js 14+ with App Router (examples use `@clerk/nextjs`) ## Instructions ### Step 1: Enable Organizations and Add UI Components ```typescript // app/org-selector/page.tsx import { OrganizationSwitcher, OrganizationProfile } from '@clerk/nextjs' export default function OrgPage() { return ( <div className="p-8"> <h1>Select Organization</h1> <OrganizationSwitcher hidePersonal={false} afterSelectOrganizationUrl="/dashboard" afterCreateOrganizationUrl="/dashboard" /> <div className="mt-8"> <OrganizationProfile /> </div> </div> ) } ``` ### Step 2: Define Custom Roles and Permissions Configure in **Clerk Dashboard > Organizations > Roles** and **Permissions**. **Default roles (built-in):** | Role | Key | Built-in Permissions | |------|-----|---------------------| | Admin | `org:admin` | Full org management (members, settings, billing) | | Member | `org:member` | View org, read-only access | **Custom permissions (create in Dashboard > Organizations > Permissions):** | Permission | Key | Description | |------------|-----|-------------| | Read data | `org:data:read` | View organization resources | | Write data | `org:data:write` | Create/update resources | | Delete data | `org:data:delete` | Delete resources | | Manage billing | `org:billing:manage` | Access billing settings | | View analytics | `org:analytics:read` | Access analytics dashboard | **Custom roles (create in Dashboard > Organizations > Roles):** | Role | Permissions | Use Case | |------|-------------|----------| | `org:manager` | `data:read`, `data:write`, `analytics:read` | Content managers | | `org:viewer` | `data:read` | Read-only stakeholders | | `org:billing_admin` | `data:read`, `billing:manage` | Finance team | ### Step 3: RBAC Middleware — Route Protection by Role ```typescript // middleware.ts import { clerkMiddleware, createRouteMatcher } from '@clerk/nextjs/server' const isPublicRoute = createRouteMatcher([ '/', '/sign-in(.*)', '/sign-up(.*)', '/api/webhooks(.*)', ]) const isAdminRoute = createRouteMatcher(['/admin(.*)']) const isManagerRoute = createRouteMatcher(['/manage(.*)']) export default clerkMiddleware(async (auth, req) => { if (isPublicRoute(req)) return if (isAdminRoute(req)) { // Only org:admin can access /admin/* await auth.protect({ role: 'org:admin' }) } else if (isManagerRoute(req)) { // org:admin OR org:manager can access /manage/* await auth.protect((has) => has({ role: 'org:admin' }) || has({ role: 'org:manager' }) ) } else { // All other routes just require authentication await auth.protect() } }) ``` ### Step 4: Permission Checks in Server Components ```typescript // app/admin/page.tsx import { auth } from '@clerk/nextjs/server' import { redirect } from 'next/navigation' export default async function AdminPage() { const { userId, orgId, orgRole, has } = await auth() if (!userId) redirect('/sign-in') if (!orgId) redirect('/org-selector') // Permission-based checks (preferred over role-based) const canManageMembers = has({ permission: 'org:sys_memberships:manage' }) const canWriteData = has({ permission: 'org:data:write' }) const canDeleteData = has({ permission: 'org:data:delete' }) const canViewAnalytics = has({ permission: 'org:analytics:read' }) return ( <div> <h1>Admin Panel</h1> <p>Current role: {orgRole}</p> <nav> {canManageMembers && <a href="/admin/members">Manage Members</a>} {canWriteData && <a href="/admin/content">Content Management</a>} {canDeleteData && <a href="/admin/danger-zone">Danger Zone</a>} {canViewAnalytics && <a href="/admin/analytics">Analytics</a>} </nav> </div> ) } ``` ### Step 5: Permission Checks in Client Components ```typescript 'use client' import { Protect, useOrganization, useAuth } from '@clerk/nextjs' export function AdminSection() { const { organization } = useOrganization() const { has } = useAuth() return ( <div> <h2>{organization?.name}</h2> {/* Declarative: Protect component with fallback */} <Protect role="org:admin" fallback={<p>You need admin access to view this section.</p>} > <DangerZone /> </Protect> {/* Permission-based rendering */} <Protect permission="org:data:write"> <EditForm /> </Protect> {/* Imperative: has() for conditional logic */} {has?.({ permission: 'org:analytics:read' }) && ( <AnalyticsDashboard /> )} </div> ) } ``` ### Step 6: Organization Member Management via Backend API ```typescript // app/api/org/members/route.ts import { auth, clerkClient } from '@clerk/nextjs/server' export async function GET() { const { orgId, has } = await auth() if (!orgId) return Response.json({ error: 'No org sele
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__clerk-enterprise-rbac.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Clerk Enterprise Rbac skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Clerk Enterprise Rbac safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Clerk Enterprise Rbac access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Clerk Enterprise Rbac work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.