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

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

72%Weight 40%Scale 1-5

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

A well-structured overview that delegates full implementation to one-level-deep reference files with clear navigation and mostly executable inline examples. The main gap is the key-rotation runbook, which performs a destructive deletion without an explicit pre-deletion verification checkpoint, capping workflow_clarity.

Suggestions

Add an explicit validation step to the key-rotation runbook before deletion, e.g. 'Confirm zero requests on the old key for 24h (check gateway logs) before deleting it.'

De-duplicate the 'Groq keys have no scopes, control lives in the gateway' point so it appears once (e.g. in the Access Model) rather than across four sections.

Inline a minimal executable validateRequest() guard snippet so the model-access-control step is copy-paste runnable without opening the reference.

Dimension	Reasoning	Score
Conciseness	Largely efficient and assumes Claude's competence, but the 'no built-in scopes / gateway is the control point' idea is restated across Overview, Groq Access Model, Prerequisites, and the Instructions opener, which is minor padding that could be tightened; not verbose enough for a 3.	4 / 5
Actionability	Provides concrete, executable inline guidance (a TS KEY_REGISTRY object, a groqGateway() call showing the expected throw, named functions like validateRequest/recordTeamUsage with concrete config fields) with the full copy-paste implementation correctly delegated to references/implementation.md; minor gaps in inline completeness keep it just below a 5.	4 / 5
Workflow Clarity	The five numbered steps are well-sequenced, but the destructive key-rotation runbook ('monitor 24h, then delete the old key') lacks an explicit verification checkpoint (e.g. confirm zero traffic on the old key before deletion), so the rubric's destructive-operation cap holds workflow_clarity at 3 rather than 4.	3 / 5
Progressive Disclosure	SKILL.md is a concise overview with well-signaled, one-level-deep references to references/implementation.md (full code) and references/examples.md (worked examples); content is appropriately split and navigation is easy, matching the top anchor against the actual bundle structure.	5 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

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 clearly states what the skill does and when to use it, with concrete trigger phrases and a distinct niche. The only defect is second-person voice ('you run/need'), which the rubric penalizes on specificity.

Suggestions

Rephrase in third person or imperative to avoid the voice penalty, e.g. 'Use when running Groq inference for multiple teams that need per-team model allow-lists...' instead of 'when you run... you need'.

Consider trimming the redundant restatement of 'no built-in scopes / access control in your gateway' which appears in both the 'when' clause and the 'what' clause.

Dimension	Reasoning	Score
Specificity	Lists multiple specific 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') approaching comprehensive coverage, but the second-person voice ('Use when you run...', 'you need') triggers the rubric's 1-point specificity penalty, dropping it from a 5 to a 4.	4 / 5
Completeness	Explicitly 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 concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Enumerates natural trigger phrases a user managing Groq enterprise access would actually say ('groq organization', 'groq RBAC', 'groq enterprise', 'groq team access', 'groq spending limits', 'groq multi-team'), covering the niche with synonyms; no relevant file extensions exist for this domain.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (Groq enterprise per-team RBAC) with distinctive triggers ('groq RBAC', 'groq enterprise', 'groq multi-team') that are unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/tons-of-skills-marketplace
Path: plugins/saas-packs/groq-pack/skills/groq-enterprise-rbac/SKILL.md
Commit: 88dcf65

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.