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".
79
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/deepgram-pack/skills/deepgram-multi-env-setup/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and completeness. It clearly identifies both what the skill does and when to use it, with explicit trigger phrases. The main weakness is that the capabilities could be more specific—listing concrete actions like creating config files, managing API keys per environment, or setting up deployment pipelines would strengthen it.
Suggestions
Add more concrete actions to improve specificity, e.g., 'Creates environment-specific config files, manages per-environment API keys, sets up project isolation between dev/staging/prod.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Deepgram multi-environment setup) and mentions some actions like 'setting up environment-specific configurations' and 'implementing environment isolation', but doesn't list concrete specific actions (e.g., create config files, set API keys, configure endpoints). | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Deepgram multi-environment setup for dev, staging, and production) and 'when' (explicit 'Use when' clause with triggers for environment-specific configurations, managing multiple projects, or implementing environment isolation). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'deepgram environments', 'deepgram staging', 'deepgram dev prod', 'multi-environment deepgram', 'deepgram config management'. These cover natural variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Deepgram with multi-environment configuration. The explicit mention of 'Deepgram' plus environment-specific terms makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, well-structured multi-environment setup guidance with executable code and a solid validation workflow. However, it is significantly over-verbose for a SKILL.md — much of the boilerplate (Docker Compose, Kubernetes overlays, repetitive per-env configs) could be generated by Claude from a concise specification or split into referenced files. The token cost is disproportionate to the unique knowledge conveyed.
Suggestions
Drastically reduce inline code by showing one environment config as an example and noting the pattern for others, rather than spelling out all three environments in full.
Move Docker Compose and Kubernetes overlay examples to separate referenced files (e.g., DOCKER.md, K8S.md) and keep only a brief summary with links in the main skill.
Remove the environment strategy table or merge it into the config code comments — the same information is duplicated between the table and the TypeScript config object.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines with extensive boilerplate code that Claude could generate on its own. The full Docker Compose, Kubernetes overlays, and repetitive per-environment config blocks inflate token usage significantly. The environment strategy table and typed config could be condensed dramatically. | 1 / 3 |
Actionability | All code examples are fully executable TypeScript, YAML, and bash. The config, client factory, Docker Compose, Kubernetes overlays, and validation script are all copy-paste ready with concrete values and realistic patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from config definition through client factory, env vars, containerization, and validation. Step 6 provides an explicit validation script with three test checkpoints (auth, project access, transcription) and pass/fail reporting, forming a proper feedback loop. | 3 / 3 |
Progressive Disclosure | The content is a monolithic wall of code that could benefit from splitting Docker/K8s configs into separate reference files. The Resources section links externally but the inline content is too heavy for a SKILL.md overview — the K8s overlays and Docker Compose especially should be referenced rather than inlined. | 2 / 3 |
Total | 9 / 12 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 — 9 / 11 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 | 9 / 11 Passed | |
- Commit
70e9fa4
- 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.