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 strong skill description that clearly defines its scope around Clerk's enterprise features (SSO, RBAC, organizations), provides explicit 'Use when' guidance, and includes well-chosen trigger phrases prefixed with 'clerk' to minimize conflict risk. The description is concise, uses third-person voice, and covers all key dimensions effectively.
| 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 seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The 'clerk' prefix on all trigger terms creates a very clear niche tied to the Clerk platform. SSO, RBAC, and organization management are specific enough to avoid overlap with generic auth or permissions 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 Clerk organizations workflow. Its main weaknesses are the lack of validation checkpoints in the multi-step workflow (especially around role creation and SSO 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 where JSX boilerplate doesn't add instructional value.
Suggestions
Add explicit validation checkpoints after key steps—e.g., 'Verify role creation by calling getOrganizationRoleList()' after Step 7, and 'Test SSO login with a test user before enforcing for all domain users' after Step 8.
Split Steps 6-7 (Backend API member management and programmatic role management) into a separate reference file like `CLERK_BACKEND_API.md` and link to it from the main skill.
Trim boilerplate JSX in Steps 1 and 5 (e.g., the wrapping div/className/h1 elements) to focus on the Clerk-specific component configuration.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity—e.g., the full JSX markup in Step 1 and Step 5 could be trimmed, and some inline comments restate what's obvious. However, it mostly avoids explaining concepts Claude already knows and stays focused on Clerk-specific patterns. | 2 / 3 |
Actionability | Every step includes fully executable TypeScript code with correct imports, file paths, and API calls. The permission tables, SAML configuration steps, and error handling table provide concrete, copy-paste-ready guidance with no pseudocode. | 3 / 3 |
Workflow Clarity | The 8-step sequence is logically ordered and covers the full lifecycle from enabling organizations to SSO configuration. However, there are no explicit validation checkpoints or feedback loops—e.g., no step to verify roles were created correctly, no guidance on testing SSO before going live, and no verify-then-proceed pattern for the destructive member management operations. | 2 / 3 |
Progressive Disclosure | The skill is quite long (~200+ lines of inline content) with all code examples embedded directly. The Resources section at the end provides external links, but the detailed API code in Steps 6-7 and the full component examples could be split into separate reference files. The structure is clear with good headings, but the monolithic nature hurts discoverability. | 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
3e83543
- 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.