groq-enterprise-rbac

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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

62%

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

A well-structured, code-rich skill with strong workflow sequencing and validation, but it is held back by padded repetitive config blocks, undefined helper functions that break copy-paste executability, and a monolithic single-file layout that would benefit from splitting into references.

Suggestions

Condense the three near-identical TEAM_CONFIGS entries to one or two illustrative examples to remove repetitive padding that adds no new information.

Define or stub the undefined helpers getTeamMonthlySpend and getTeamApiKey (and clarify how weeklyReport obtains its records) so the gateway code is fully executable rather than referencing unimplemented functions.

Move the full gateway implementation and pricing reference into separate reference files (e.g. references/gateway.md, references/spending.md) and keep SKILL.md as an overview with clearly signaled one-level-deep links, reducing the 250-line single-file body.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept explanation, but padded with three near-identical TEAM_CONFIGS blocks and repetitive definitions that could be tightened without losing information.	2 / 3
Actionability	Largely executable TypeScript, but core helpers getTeamMonthlySpend and getTeamApiKey are called yet never defined, and the weeklyReport records source is unclear, leaving key details missing.	2 / 3
Workflow Clarity	Steps 1-6 are clearly sequenced with explicit validation checkpoints (24h monitoring before key deletion; validateRequest and budget checks before gateway execution) and an error-handling table for recovery.	3 / 3
Progressive Disclosure	Sections are well-organized but all content sits inline in a single ~250-line file with no bundle files or signaled one-level-deep references, exceeding the simple-skill threshold where inline content would score 3.	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, concise description that names concrete capabilities and provides explicit natural-language triggers covering both 'what' and 'when'. It is distinctive to the Groq enterprise niche and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('organization management, API key scoping, spending controls, and team access patterns'), matching the score-3 anchor for several specific capabilities rather than a vague domain.	3 / 3
Completeness	Explicitly answers what it does (configure Groq org/key/spending/access) and when to use it via the explicit 'Trigger with phrases like...' clause, satisfying both halves of the score-3 anchor.	3 / 3
Trigger Term Quality	Provides six natural phrases a user would say ('groq organization', 'groq team access', 'groq spending limits', 'groq multi-team'), giving good coverage beyond a few keywords.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Groq-specific enterprise/RBAC niche with distinct trigger phrases, making it unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 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/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: 1 day 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.