CtrlK
BlogDocsLog inGet started
Tessl Logo

deepgram-enterprise-rbac

Configure enterprise role-based access control for Deepgram integrations. Use when implementing team permissions, managing API key scopes, or setting up organization-level access controls. Trigger: "deepgram RBAC", "deepgram permissions", "deepgram access control", "deepgram team roles", "deepgram enterprise", "deepgram key scopes".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

Highly actionable with complete, runnable code and a clear six-step sequence, but it underuses the existing reference bundle and lacks explicit validation checkpoints on its destructive/batch key operations. Tightening the duplication and signaling the reference would raise the lower dimensions.

Suggestions

Lean the SKILL.md body into an overview and move the duplicated role/key/middleware/rotation implementations into references/implementation.md, linking to it explicitly so content is split rather than repeated.

Add an explicit verification checkpoint in the key-rotation workflow (confirm the new key works and the DB update succeeded) before revoking the old key, and turn the 'grace period' parenthetical into a concrete step.

Reference references/implementation.md from the body (e.g., in a Resources or Advanced section) so the bundle file is clearly signaled and discoverable.

DimensionReasoningScore

Conciseness

The body is largely code with minimal concept explanation, but it duplicates much of the content already present in references/implementation.md (roles, key provisioning, middleware, team management, rotation), which is unnecessary token spend that could be tightened.

2 / 3

Actionability

Fully executable, copy-paste-ready TypeScript throughout — DeepgramKeyManager, requireRole/requireScope middleware, TeamManager, and rotateExpiringKeys with concrete Deepgram SDK calls and real route examples.

3 / 3

Workflow Clarity

Six steps are clearly sequenced with some error handling, but destructive/batch operations (key rotation revoking and recreating keys, role changes) lack explicit validation checkpoints — the post-rotation verification and grace period are only implied in a parenthetical comment, capping the score at 2.

2 / 3

Progressive Disclosure

Sections are organized and a one-level-deep reference file exists, but the body never signals or links references/implementation.md and instead carries the full implementation inline (~340 lines), duplicating content that should be split out.

2 / 3

Total

9

/

12

Passed

Description

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.

A strong, specific description that answers both what the skill does and when to use it, with a broad set of natural trigger terms and a clear, low-conflict niche. No notable weaknesses.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Configure enterprise role-based access control', 'implementing team permissions', 'managing API key scopes', 'setting up organization-level access controls' — matching the multi-action anchor.

3 / 3

Completeness

Clearly answers both what ('Configure enterprise role-based access control for Deepgram integrations') and when (an explicit 'Use when...' clause plus a Trigger list), satisfying the full-3 anchor.

3 / 3

Trigger Term Quality

Six natural trigger terms ('deepgram RBAC', 'deepgram permissions', 'deepgram access control', 'deepgram team roles', 'deepgram enterprise', 'deepgram key scopes') give broad coverage of what a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The 'Deepgram' + 'enterprise RBAC' niche with Deepgram-prefixed triggers is narrow 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.