deepgram-local-dev-loop
Configure Deepgram local development workflow with testing and mocks. Use when setting up development environment, configuring test fixtures, or establishing rapid iteration patterns for Deepgram integration. Trigger: "deepgram local dev", "deepgram development setup", "deepgram test environment", "deepgram dev workflow", "deepgram mock".
80
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/deepgram-pack/skills/deepgram-local-dev-loop/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 that clearly identifies its niche (Deepgram local dev setup) and provides explicit trigger terms. Its main weakness is that the capability description could be more specific about the concrete actions it performs beyond the general 'configure workflow with testing and mocks'. The completeness and trigger term coverage are strong.
Suggestions
Add more specific concrete actions, e.g., 'Creates mock API responses, configures test fixtures for speech-to-text results, sets up local proxy servers, and establishes hot-reload patterns for Deepgram integration.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Deepgram local development) and some actions (configure workflow, testing, mocks), but doesn't list multiple concrete specific actions like 'create mock responses', 'set up test fixtures', 'configure environment variables', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Deepgram local development workflow with testing and mocks) and 'when' (setting up development environment, configuring test fixtures, establishing rapid iteration patterns) with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'deepgram local dev', 'deepgram development setup', 'deepgram test environment', 'deepgram dev workflow', 'deepgram mock'. These cover natural variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Deepgram' domain combined with 'local development workflow' focus. The trigger terms are very specific and unlikely to conflict with other skills unless there are multiple Deepgram-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with complete, executable code examples covering the full local dev workflow. Its main weaknesses are verbosity in mock definitions and test code that inflates the token cost, and the lack of validation checkpoints between setup steps. The content would benefit from trimming mock detail and adding verification steps.
Suggestions
Add validation checkpoints after key steps, e.g., 'Run `npx vitest run tests/transcribe.test.ts` to verify mocks are working before proceeding to integration tests'
Trim mock objects to essential fields only — the full word-level timing arrays and metadata can be shortened with comments like '// add more words as needed'
Consider extracting the full mock file and test files into bundle files, keeping only a concise example in the SKILL.md body
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary bulk — the mock objects are very detailed with many fields that could be trimmed, and the unit test examples are somewhat verbose for what they demonstrate. The overall structure is good but could be tightened by ~30%. | 2 / 3 |
Actionability | Fully executable code throughout: bash commands for setup, complete TypeScript files for mocks, unit tests, and integration tests, plus concrete package.json scripts. Everything is copy-paste ready with real URLs and realistic configurations. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (1-6), but there are no validation checkpoints between steps — no 'verify your fixtures downloaded correctly,' no 'run tests to confirm mocks work before proceeding to integration tests.' For a multi-step setup workflow, explicit verification steps would improve reliability. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's quite long and monolithic — the detailed mock objects and full test files could be split into referenced files. The 'Next Steps' reference to deepgram-sdk-patterns is good, but no bundle files exist to support progressive disclosure. | 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
a04d1a2
- 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.