deepgram-ci-integration
Configure Deepgram CI/CD integration for automated testing and deployment. Use when setting up continuous integration pipelines, automated testing, or deployment workflows for Deepgram integrations. Trigger: "deepgram CI", "deepgram CD", "deepgram pipeline", "deepgram github actions", "deepgram automated testing".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 is a well-structured skill description with strong trigger terms and clear 'what/when' guidance. Its main weakness is the lack of specific concrete actions—it says 'configure CI/CD integration' but doesn't enumerate what that entails (e.g., writing GitHub Actions YAML, setting up test fixtures, configuring API key secrets). The description uses proper third-person voice and is concise.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Creates GitHub Actions workflows, configures API key secrets, sets up test fixtures for Deepgram speech-to-text endpoints, and defines deployment stages.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Deepgram CI/CD) and mentions 'automated testing and deployment' but doesn't list specific concrete actions like 'create GitHub Actions workflows, configure test runners, set up deployment scripts'. The description stays at a high level. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Deepgram CI/CD integration for automated testing and deployment) and 'when' (setting up CI pipelines, automated testing, or deployment workflows), plus includes explicit trigger terms. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'deepgram CI', 'deepgram CD', 'deepgram pipeline', 'deepgram github actions', 'deepgram automated testing'. These cover common variations of how users would phrase CI/CD requests for Deepgram. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Deepgram' with 'CI/CD' creates a very specific niche. The explicit trigger terms are all Deepgram-prefixed, making it unlikely to conflict with generic CI/CD skills or other Deepgram skills focused on different aspects. | 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 highly actionable skill with complete, executable code for setting up Deepgram CI/CD pipelines. The workflow is well-sequenced with proper dependency gates and error handling. However, the skill is quite long with some redundancy between the smoke test and integration tests, and would benefit from splitting the large code blocks into referenced files rather than inlining everything.
Suggestions
Extract the integration test suite, smoke test script, and key rotation workflow into separate referenced files to improve progressive disclosure and reduce the main skill's token footprint.
Remove the smoke test or consolidate it with integration tests, as they largely duplicate the same API calls (auth, STT, TTS).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code, but is quite long. The smoke test largely duplicates the integration tests, and some inline comments are unnecessary. The overall length (~250 lines of code) could be trimmed without losing value. | 2 / 3 |
Actionability | Fully executable code throughout: complete GitHub Actions YAML, TypeScript test suites, vitest config, package.json scripts, and key rotation workflow. Everything is copy-paste ready with specific models, URLs, and configurations. | 3 / 3 |
Workflow Clarity | Clear sequential pipeline (unit -> integration -> smoke) with explicit dependency gates (`needs`), conditional execution for fork PRs, timeout limits, and the error handling table provides troubleshooting for common failure modes. The key rotation workflow includes validation via the smoke test pipeline. | 3 / 3 |
Progressive Disclosure | All content is inline in a single monolithic file. The integration test suite, smoke test script, and key rotation workflow could reasonably be referenced as separate files. The Resources section provides external links but the skill itself has no internal file references for the substantial code blocks. | 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
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.