CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-enterprise-rbac

Use when you run Groq inference for multiple teams and need per-team model allow-lists, spending caps, rate limits, and key rotation — because Groq API keys have no built-in scopes, so access control must live in your gateway. Configure Groq organization management, API key scoping, spending controls, and team access patterns. Trigger with phrases like "groq organization", "groq RBAC", "groq enterprise", "groq team access", "groq spending limits", "groq multi-team".

75

Quality

95%

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.

A tight, well-organized body that gives concrete actionable guidance, a clearly sequenced workflow with validation checkpoints, and clean one-level-deep progressive disclosure to verified reference files.

DimensionReasoningScore

Conciseness

The body is lean and well-structured with concise bullets and one short code snippet; it assumes Claude's competence and avoids explaining what Groq or API keys are, so every section earns its place.

3 / 3

Actionability

Concrete, specific guidance throughout — a real TypeScript key-registry snippet, named functions (validateRequest, groqGateway, recordTeamUsage), exact config fields (allowedModels, maxTokensPerRequest, monthlyBudgetUsd, rateLimitRPM), a naming convention, and a pointer to the full copy-paste implementation in references/implementation.md.

3 / 3

Workflow Clarity

A clearly sequenced five-step process with explicit validation (the gateway guard throws before unauthorized/oversized requests reach Groq), an error-handling table for recovery, and a key-rotation runbook with a 'monitor 24h' checkpoint before deleting the old key.

3 / 3

Progressive Disclosure

SKILL.md is a clear overview that defers full detail to well-signaled, one-level-deep references (references/implementation.md and references/examples.md, both present), with a Resources section consolidating navigation.

3 / 3

Total

12

/

12

Passed

Description

90%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 strong, specific description with explicit triggers covering both what and when for a well-defined Groq enterprise RBAC niche. The only weakness is second-person voice, which costs a specificity point under the rubric.

Suggestions

Rewrite the opening in third person to recover the specificity point, e.g. 'Use when running Groq inference for multiple teams...' or 'Manages per-team Groq access with model allow-lists, spending caps, rate limits, and key rotation.'

Consider adding a couple of natural user phrasings beyond the 'groq <noun>' pattern, such as 'groq per-team limits' or 'groq key rotation', to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('per-team model allow-lists, spending caps, rate limits, and key rotation', 'Configure Groq organization management, API key scoping, spending controls, and team access patterns') which would be a 3, but the description is written in second person ('Use when you run Groq inference'), which the rubric penalizes by reducing specificity by one point.

2 / 3

Completeness

Clearly answers both what ('Configure Groq organization management, API key scoping, spending controls, and team access patterns') and when ('Use when you run Groq inference for multiple teams and need per-team model allow-lists...') with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

Explicit, natural trigger phrases a user managing Groq enterprise access would say are listed: 'groq organization', 'groq RBAC', 'groq enterprise', 'groq team access', 'groq spending limits', 'groq multi-team'.

3 / 3

Distinctiveness Conflict Risk

A clear, narrow niche (Groq per-team enterprise access control via a gateway) with distinct triggers like 'groq RBAC' and 'groq enterprise', making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.