deepgram-multi-env-setup

Configure Deepgram multi-environment setup for dev, staging, and production. Use when setting up environment-specific configurations, managing multiple Deepgram projects, or implementing environment isolation. Trigger: "deepgram environments", "deepgram staging", "deepgram dev prod", "multi-environment deepgram", "deepgram config management".

Quality

82%

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

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

The content is highly actionable with complete, executable code for every step, but it is weakened by redundancy between the table and code, missing inline validation checkpoints for risky operations, and an orphaned bundle file that is never referenced from the body.

Suggestions

Remove the Environment Strategy table or reduce it to settings not already shown in the Step 1 code to avoid duplicating the same configuration values twice.

Add inline validate→fix→retry checkpoints between the Docker/Kustomize build and deploy steps rather than only providing a terminal validation script.

Either reference references/implementation.md from the body (e.g., "See [implementation.md](references/implementation.md) for the full Terraform and validation details") or merge its unique content (Terraform, deeper validation) into the body and drop the duplicate material.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy and largely efficient, but the Environment Strategy table duplicates settings that reappear verbatim in the Step 1 code, and the unreferenced implementation.md repeats much of the same material — content that could be tightened.	2 / 3
Actionability	Provides fully executable TypeScript, bash, and YAML throughout (typed config, client factory, Docker Compose profiles, Kustomize overlays, validation script) that is copy-paste ready, matching the score-3 anchor.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced and Step 6 provides a validation script, but there are no inline validate→fix→retry checkpoints between the build/deploy steps, and risky operations (key rotation, cross-env keys) lack an explicit feedback loop, capping this at 2.	2 / 3
Progressive Disclosure	A bundle file references/implementation.md exists but is never referenced or signaled from the body, and the body is a long monolithic set of inline code blocks that largely duplicates the bundle — content that should be split is inline with no clear navigation.	2 / 3
	Total	9 / 12 Passed

Description

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

The description is specific, complete, and distinctive: it names concrete actions, includes a clear Use-when clause with natural trigger phrases, and occupies a well-scoped niche. No major weaknesses; the only nit is the trailing whitespace/blank lines inside the YAML string, which does not affect scoring.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Configure Deepgram multi-environment setup", "managing multiple Deepgram projects", "implementing environment isolation") rather than vague language, matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what ("Configure Deepgram multi-environment setup for dev, staging, and production") and when ("Use when setting up environment-specific configurations...") with an explicit trigger clause.	3 / 3
Trigger Term Quality	Provides good coverage of natural phrases a user would say ("deepgram environments", "deepgram staging", "deepgram dev prod", "multi-environment deepgram", "deepgram config management"), beyond just "some relevant keywords".	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Deepgram multi-environment setup) with distinct, domain-specific triggers, making it unlikely to fire for unrelated skills.	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
Path: plugins/saas-packs/deepgram-pack/skills/deepgram-multi-env-setup/SKILL.md
Commit: 0540a62

Reviewed: about 15 hours 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.