clerk-enterprise-rbac
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".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that hits all the key criteria. It provides specific capabilities, explicit trigger guidance with both 'Use when' and 'Trigger with phrases' clauses, and uses the 'clerk' prefix to create strong distinctiveness. The third-person voice and concise structure make it easy for Claude to match against user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure enterprise SSO', 'role-based access control', and 'organization management'. These are distinct, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure enterprise SSO, RBAC, org management) and 'when' (explicit 'Use when' clause with specific scenarios plus a 'Trigger with phrases' section listing exact keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'clerk SSO', 'clerk RBAC', 'clerk enterprise', 'clerk roles', 'clerk permissions', 'clerk organizations'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The 'clerk' prefix on all trigger terms creates a very clear niche tied to the Clerk platform. Combined with specific domains (SSO, RBAC, organizations), this is highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable enterprise RBAC skill with executable code examples covering the full spectrum from UI components to backend API management. Its main weaknesses are the lack of validation checkpoints between steps (important for enterprise SSO/RBAC configuration) and the monolithic structure that could benefit from splitting detailed API examples into separate files. The content is mostly efficient but could be tightened in places.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Verify organization creation works by visiting /org-selector before proceeding to Step 2' and 'Test middleware protection by accessing /admin as a non-admin user'.
Split the Backend API examples (Steps 6-7) and SAML SSO configuration (Step 8) into separate referenced files to improve progressive disclosure and reduce the main file's length.
Remove the illustrative custom permissions/roles tables or condense them into a single compact example—Claude can generate variations from one clear pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity—the tables for custom permissions/roles are illustrative examples that could be trimmed, and some inline comments restate what's obvious from the code. However, it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Every step includes fully executable TypeScript code with proper imports, file paths, and realistic configurations. The code is copy-paste ready for a Next.js App Router project, covering middleware, server components, client components, and API routes. | 3 / 3 |
Workflow Clarity | The 8 steps are clearly sequenced from setup through SSO configuration, and the error handling table is helpful. However, there are no explicit validation checkpoints—no 'verify this works before proceeding' steps between stages, and no feedback loops for error recovery in what is a complex multi-step enterprise configuration. | 2 / 3 |
Progressive Disclosure | The skill includes a Resources section with external links and a Next Steps pointer, but the body itself is quite long (~200+ lines of inline code) with content that could be split into separate reference files (e.g., Backend API examples, SSO configuration). The structure is good with clear headings but the content density is high for a single SKILL.md. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
70e9fa4
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.