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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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 examples but is hurt by verbosity (duplicating the bundled reference inline) and weak progressive disclosure, since references/implementation.md is never linked from the body and large blocks belong in separate files. Workflow clarity is good but lacks explicit validation feedback loops.

Suggestions

Link the bundled reference from the body (e.g., 'See [implementation.md](references/implementation.md) for full client factory, Terraform, and K8s details') and move the duplicated Docker/Kustomize/validation blocks there to reduce inline token weight.

Convert Step 6 validation into an explicit checkpoint loop (run validation -> if failures, fix and re-run -> only proceed when ALL PASS) so batch environment promotion has clear gates.

Turn the bare 'Resources' bullets into real links (e.g., Deepgram Projects/Key Management URLs) or remove them if they cannot be linked.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code, but large inline blocks (full TypeScript factory, Docker Compose, Kustomize, validation) duplicate material also present in references/implementation.md and could be tightened or offloaded.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript, bash, YAML, and Kustomize examples with specific commands and concrete config values.	3 / 3
Workflow Clarity	Steps are clearly numbered, but the validation step (Step 6) is presented as a script rather than an explicit validate-then-proceed feedback loop, and destructive batch config changes lack explicit checkpoints.	2 / 3
Progressive Disclosure	The body is a monolithic wall of inline code with a single reference (implementation.md) never linked or signaled from the body, and the Resources section lists unlinked bullets; deep content that should be separate is duplicated inline rather than split.	1 / 3
	Total	8 / 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.

The description is strong: concrete capabilities, a 'Use when...' clause, explicit triggers, and a distinct niche with low conflict risk. It would benefit from slight tightening of the multi-line padding but the content itself is solid.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions ('setting up environment-specific configurations, managing multiple Deepgram projects, or implementing environment isolation'), matching the top anchor.	3 / 3
Completeness	Explicitly answers what the skill does and when Claude should use it via a 'Use when...' clause plus a 'Trigger:' list, hitting the top anchor.	3 / 3
Trigger Term Quality	Includes natural phrases users would say ('deepgram environments', 'deepgram staging', 'deepgram dev prod', 'multi-environment deepgram', 'deepgram config management') with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Clear niche (Deepgram multi-environment isolation) with distinct triggers unlikely to overlap with 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
Commit: 02d6341

Reviewed: 4 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.