CtrlK
BlogDocsLog inGet started
Tessl Logo

exa-enterprise-rbac

Manage Exa API key scoping, team access controls, and domain restrictions. Use when implementing multi-key access control, configuring per-team search limits, or setting up organization-level Exa governance. Trigger with phrases like "exa access control", "exa RBAC", "exa enterprise", "exa team keys", "exa permissions".

78

Quality

100%

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

100%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 body is a lean, fully executable implementation guide with concrete code for each step and a validated key-rotation workflow. It is well-organized into clear sections with no nested or broken references.

DimensionReasoningScore

Conciseness

The body is lean and dominated by executable TypeScript/bash with minimal prose; the only explanatory sentence (that Exa is API-key-based with no built-in RBAC) earns its place by justifying the architecture rather than restating general knowledge.

3 / 3

Actionability

Every step ships complete, executable code — keyed client factory, a role-permission validator, an enforcedSearch wrapper, a KeyUsageTracker class, and a copy-paste curl key-rotation script — with concrete role definitions and values rather than pseudocode.

3 / 3

Workflow Clarity

A clear 5-step sequence is presented, and the destructive key-rotation step includes an explicit validation checkpoint (curl returning the HTTP status code to 'Verify new key works') followed by monitor-then-revoke-after-24h feedback, satisfying the feedback-loop requirement for risky operations.

3 / 3

Progressive Disclosure

Though a single file with no bundle, the content is well-organized into Overview, Prerequisites, five numbered instruction steps, an Error Handling table, Resources, and Next Steps pointing one level out to sibling skills, with no nested references.

3 / 3

Total

12

/

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.

The description is concise yet specific, naming concrete access-control actions and pairing them with explicit 'Use when' and trigger-phrase guidance. It is clearly niche-scoped and unlikely to trigger for the wrong skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions including 'Manage Exa API key scoping, team access controls, and domain restrictions', 'multi-key access control', 'per-team search limits', and 'organization-level Exa governance', matching the score-3 anchor that lists several specific concrete actions.

3 / 3

Completeness

It answers both what ('Manage Exa API key scoping, team access controls, and domain restrictions') and when ('Use when implementing multi-key access control, configuring per-team search limits, or setting up organization-level Exa governance' plus explicit trigger phrases), matching the score-3 anchor with explicit triggers.

3 / 3

Trigger Term Quality

It provides explicit natural trigger phrases users would say ('exa access control', 'exa RBAC', 'exa enterprise', 'exa team keys', 'exa permissions'), giving good coverage of natural terms rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

The Exa enterprise RBAC niche with distinct 'exa access control'/'exa RBAC'/'exa team keys' triggers is clearly scoped and unlikely to conflict with other skills.

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.