CtrlK
BlogDocsLog inGet started
Tessl Logo

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

68

Quality

83%

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

78%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.

Well-structured, actionable content that uses progressive disclosure effectively, offloading full code to clearly signaled reference files. Weaknesses are minor verbosity in the Output/Examples sections and an implicit rather than explicit validation feedback loop.

Suggestions

Make the verify feedback loop explicit in the Instructions (e.g., 'If verify reports Connection: FAILED, fix the key/model and re-run verify-groq-env.ts before deploying').

Trim the 'Output' expected-text block and the 'You end with:' recap, or fold them into the verify step, to tighten token use.

Replace the `/* ... */` placeholders in the inline config skeleton with the few missing fields (or note explicitly that the full record is in implementation.md) so the body snippet stands alone.

DimensionReasoningScore

Conciseness

The body is a lean map that assumes Claude's competence and avoids explaining basic concepts, but the 'Output' and 'You end with:' summary plus the Examples section add some tokens that could be trimmed.

4 / 5

Actionability

Provides a concrete config skeleton, executable example snippets, and specific verify/secret commands, with complete copy-paste code in the referenced files; the inline skeleton uses `/* ... */` placeholders, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

Six numbered steps are clearly sequenced with an explicit verify checkpoint (Step 5, live round-trip) and an Error Handling table for recovery, but the validate→fix→re-validate feedback loop is less explicit than the top anchor.

4 / 5

Progressive Disclosure

The body is a concise overview pointing to two real, one-level-deep reference files (implementation.md, secrets-and-deployment.md) via well-signaled markdown links with section anchors; content is appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

88%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 both capability and trigger conditions with concrete phrases. The main weakness is trigger homogeneity and minor overlap with a sibling Groq deployment skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'environment-specific model selection, rate limits, and secrets', 'per-environment API keys', 'hardened retries', 'verbose logs in dev' — giving comprehensive coverage of what the skill configures.

5 / 5

Completeness

Explicitly answers both what ('Configure environment-specific model selection, rate limits, and secrets' with a dev/staging/prod behavior split) and when ('Use when you need Groq to behave differently across dev, staging, and production' plus a concrete 'Trigger with phrases like...' clause).

5 / 5

Trigger Term Quality

Provides six natural trigger phrases ('groq environments', 'groq staging', 'groq dev prod', 'groq environment setup', 'groq multi-env', 'groq config by env'), but they are homogeneous permutations of 'groq + env-word' and miss a few natural variants a user might say.

4 / 5

Distinctiveness Conflict Risk

Groq-scoped triggers carve a clear niche, but the skill body references a closely related sibling 'groq-deploy-integration' skill, creating minor overlap risk with a neighboring Groq skill rather than minimal conflict risk.

4 / 5

Total

18

/

20

Passed

Validation

81%

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

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository
jeremylongshore/tons-of-skills-marketplace
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.