deepgram-migration-deep-dive
Deep dive into migrating to Deepgram from other transcription providers. Use when migrating from AWS Transcribe, Google Cloud STT, Azure Speech, OpenAI Whisper, AssemblyAI, or Rev.ai to Deepgram. Trigger: "deepgram migration", "switch to deepgram", "migrate transcription", "deepgram from AWS", "deepgram from Google", "replace whisper with deepgram".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 description excels at trigger term coverage and completeness, with explicit 'Use when' and 'Trigger' clauses that enumerate specific providers and natural user phrases. Its main weakness is the vagueness of the actual capabilities — 'deep dive into migrating' doesn't convey specific actions the skill performs. Adding concrete actions like 'maps API parameters, converts request formats, provides equivalent Deepgram configurations' would strengthen it significantly.
Suggestions
Replace 'Deep dive into migrating' with specific concrete actions such as 'Maps API parameters, converts request/response formats, and provides equivalent Deepgram SDK code for migrating from other transcription providers'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (migrating to Deepgram from other transcription providers) and lists specific source providers, but the actual actions are vague — 'deep dive into migrating' doesn't describe concrete actions like 'maps API parameters', 'converts configuration files', or 'provides code migration examples'. | 2 / 3 |
Completeness | Clearly answers both 'what' (migrating to Deepgram from other transcription providers) and 'when' (explicit 'Use when' clause listing specific providers, plus a 'Trigger' section with natural phrases). Both components are explicitly stated. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including explicit phrases like 'deepgram migration', 'switch to deepgram', 'migrate transcription', and provider-specific variations like 'deepgram from AWS', 'replace whisper with deepgram'. These closely match what users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of Deepgram as the target platform and specific competing providers creates a very clear niche that is unlikely to conflict with other skills. The trigger terms are uniquely tied to this migration scenario. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured migration skill with excellent actionability — concrete feature mapping tables and complete, executable TypeScript implementations. The workflow is clearly sequenced with validation checkpoints and rollback procedures. However, the skill is quite long due to inline code that could benefit from being split into bundle files, and some code sections include unnecessary commentary that Claude wouldn't need.
Suggestions
Extract the full adapter implementations (DeepgramAdapter, AWSTranscribeAdapter, MigrationRouter, validateMigration) into separate bundle files and reference them from SKILL.md to improve progressive disclosure.
Remove obvious code comments like '// AWS is async-only' and '// Poll for completion' to improve conciseness — Claude understands these patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The feature mapping tables are efficient and valuable, but the full adapter implementations (especially the AWS legacy adapter and the validation function) are quite lengthy. The migration router code could be more concise since the pattern is straightforward. Some code comments explain obvious things ('AWS is async-only', 'Poll for completion'). | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with complete adapter implementations, a migration router, and a validation function. The feature mapping tables give concrete parameter-to-parameter translations. Code is copy-paste ready with proper imports and error handling. | 3 / 3 |
Workflow Clarity | The migration is clearly sequenced from adapter pattern setup through validation to phased rollout with explicit percentages and timelines. The parallel running step serves as a validation checkpoint, the migration checklist provides a clear timeline, and the error handling table includes rollback instructions ('router.setDeepgramPercent(0) immediately'). | 3 / 3 |
Progressive Disclosure | All content is inline in a single file with no bundle files for the detailed adapter implementations or validation code. The lengthy code blocks (AWS adapter, validation function) could be split into referenced files. The Resources section links to external docs but the skill itself is monolithic at ~300 lines. | 2 / 3 |
Total | 10 / 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
3a2d27d
- 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.