CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable code throughout, but it is monolithic: it duplicates some concerns across steps, omits validation checkpoints for security-sensitive role operations, and fails to surface the bundled implementation-guide.md reference that already exists.

Suggestions

Link references/implementation-guide.md from the body (e.g., a "## Implementation guide" section) and move the detailed SAML/Okta and Backend API steps there, keeping SKILL.md as a concise overview that points one level deep.

Add explicit validation checkpoints to the role/permission and invitation workflows (e.g., verify the created role appears via getOrganizationMembershipList before proceeding, or confirm the invitation status) to close the feedback loop on these security-sensitive operations.

Consolidate the overlapping permission-check examples in Steps 4 and 5 into a single section showing both server and client patterns, and trim the Enterprise Considerations bullets that restate information already shown in the code.

DimensionReasoningScore

Conciseness

The body avoids concept-explanation fluff and is mostly code plus tables, but eight full code blocks (Steps 4 and 5 both cover permission checks; Steps 6 and 7 both use the Backend API) could be tightened or consolidated, so not every token earns its place.

2 / 3

Actionability

Every step ships complete, copy-paste-ready TypeScript with exact permission keys, dashboard navigation paths, and a concrete error-handling table, fully meeting the executable-guidance anchor.

3 / 3

Workflow Clarity

Steps 1-8 are clearly sequenced, but role/permission assignment and invitations are security-sensitive operations with no explicit validate-then-proceed checkpoints; the reactive Error Handling table is not a feedback loop, capping this at 2 per the destructive/batch-operations guideline.

2 / 3

Progressive Disclosure

A 348-line references/implementation-guide.md bundle exists but is never linked from the body, while the 316-line SKILL.md keeps all eight detailed steps inline — references present but not signaled, and content that could be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description: it states concrete capabilities, gives explicit "Use when" guidance, and lists natural clerk-prefixed trigger phrases that distinguish it from generic auth skills. The only blemish is stray blank lines mid-sentence inside the YAML folding, which does not affect semantic clarity.

DimensionReasoningScore

Specificity

"Configure enterprise SSO, role-based access control, and organization management" lists three concrete, distinct actions rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It explicitly answers both what ("Configure enterprise SSO, role-based access control, and organization management") and when ("Use when implementing SSO integration..." plus explicit trigger phrases), satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

"Trigger with phrases like \"clerk SSO\", \"clerk RBAC\", \"clerk enterprise\", \"clerk roles\", \"clerk permissions\", \"clerk organizations\"" gives good coverage of natural terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Every trigger is prefixed with "clerk", carving a clear niche unlikely to fire for unrelated skills; the scope is enterprise RBAC/SSO specifically.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.