groq-multi-env-setup

Use when you need Groq to behave differently across dev, staging, and production — cheap fast models and verbose logs in dev, the production model and hardened retries everywhere else, with per-environment API keys. Configure environment-specific model selection, rate limits, and secrets. Trigger with phrases like "groq environments", "groq staging", "groq dev prod", "groq environment setup", "groq multi-env", "groq config by env".

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 well-structured, actionable skill body that delegates full implementations to real one-level-deep reference files and includes a verification checkpoint. The main weakness is redundancy of the env/model/retry values across the table, skeleton, examples, and error table.

Suggestions

Remove the duplicated model/retry/logging values from the inline config skeleton and error-handling table, citing them once and pointing to the strategy table for the source of truth.

Drop the repeat 'Full, runnable versions of every snippet are in implementation.md and secrets-and-deployment.md' line in Examples since the Instructions already links each step to those files.

Dimension	Reasoning	Score
Conciseness	It is mostly efficient — a compact table, short sections, and a skeleton that delegates full code to references — but the model/retry/logging values recur across the strategy table, the config skeleton, the example snippets, and the error-handling table, which is tightening room the middle anchor describes.	2 / 3
Actionability	It provides a copy-paste config skeleton, concrete file paths (config/groq.ts, services/groq-service.ts), and executable commands like 'NODE_ENV=production GROQ_API_KEY_PROD=gsk_... npx tsx scripts/verify-groq-env.ts', with the full runnable code living in the references.	3 / 3
Workflow Clarity	Six numbered steps form a clear sequence with an explicit verification checkpoint (step 5: verify each environment) and an error-handling table, matching the top anchor's clear sequence with validation.	3 / 3
Progressive Disclosure	The body is a map pointing to two one-level-deep, clearly signaled references (references/implementation.md and references/secrets-and-deployment.md, both present in the bundle) with section anchors, keeping full code out of the overview.	3 / 3
	Total	11 / 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, well-scoped description that clearly states what the skill does and when to use it, with a generous set of natural trigger phrases. The only ding is the second-person 'you need' phrasing, which the rubric treats as a voice violation.

Suggestions

Rewrite in third person/imperative to match the good examples, e.g. 'Use when Groq must behave differently across dev, staging, and production — cheap fast models and verbose logs in dev, the production model and hardened retries elsewhere, with per-environment API keys.'

Dimension	Reasoning	Score
Specificity	It names concrete actions ('Configure environment-specific model selection, rate limits, and secrets' and 'per-environment API keys', 'hardened retries'), but the opening 'Use when you need Groq to behave differently' is second person ('you need'), which the rubric penalizes by reducing specificity by one — so a 3 anchors down to 2.	2 / 3
Completeness	It explicitly answers both what ('Configure environment-specific model selection, rate limits, and secrets') and when ('Use when you need Groq to behave differently across dev, staging, and production', plus the 'Trigger with phrases like' clause), satisfying the top anchor.	3 / 3
Trigger Term Quality	It lists six natural trigger phrases users would actually say — 'groq environments', 'groq staging', 'groq dev prod', 'groq environment setup', 'groq multi-env', 'groq config by env' — matching the top anchor's good coverage.	3 / 3
Distinctiveness Conflict Risk	The Groq multi-environment niche is specific and the triggers are Groq-scoped ('groq environments', 'groq multi-env'), making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 13 / 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
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/groq-pack/skills/groq-multi-env-setup/SKILL.md
Commit: 4c47e33

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.