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".
65
80%
Does it follow best practices?
Impact
—
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-ci-integration/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 defines its niche (Deepgram CI/CD) with explicit trigger terms and a clear 'Use when' clause. Its main weakness is the lack of specific concrete actions—it describes the general category of work rather than listing particular tasks like configuring specific CI platforms, writing test suites, or managing deployment configurations. The trigger terms are well-chosen and distinctive.
Suggestions
Add more specific concrete actions such as 'configure GitHub Actions workflows, set up automated API key rotation, create test suites for Deepgram endpoints, manage staging/production deployment configs' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Deepgram CI/CD integration) and mentions some actions (automated testing, deployment), but lacks specific concrete actions like 'configure GitHub Actions workflows', 'set up test runners', or 'create deployment scripts'. It 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 for Deepgram), with explicit trigger terms listed. | 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 requests in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Deepgram' with 'CI/CD' creates a very specific niche. The trigger terms are all prefixed with 'deepgram', 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
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at actionability with fully executable, copy-paste-ready code for a complete Deepgram CI/CD pipeline, and the workflow sequencing with validation gates is well-designed. However, the content is monolithic and lengthy, with notable redundancy between the smoke test and integration test suite. Splitting content into referenced files would significantly improve token efficiency and progressive disclosure.
Suggestions
Extract the integration test suite, smoke test script, and key rotation workflow into separate bundle files referenced from SKILL.md to improve progressive disclosure and reduce the monolithic structure.
Eliminate redundancy between the smoke test and integration test suite—either reference shared test logic or explain when to use each, rather than duplicating similar tests for auth, STT, and TTS.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial executable code which is valuable, but there's significant redundancy between the integration test suite and the smoke test script (both test authentication, transcription, and TTS with the same sample URL). The prerequisites and overview sections are reasonably lean, but the overall content is long and could be tightened by deduplicating the smoke test or referencing shared patterns. | 2 / 3 |
Actionability | Fully executable code throughout: complete GitHub Actions YAML workflows, TypeScript test suites, vitest configuration, and package.json scripts. All code is copy-paste ready with specific models, URLs, and configurations. The key rotation workflow includes concrete shell commands. | 3 / 3 |
Workflow Clarity | Clear sequential pipeline: unit tests → integration tests → smoke tests, with explicit dependency chains via `needs`. The workflow includes validation gates (unit tests must pass before integration tests run), fork PR security handling via the `if` condition, timeout limits, and the error handling table provides a feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | All content is inlined in a single monolithic file with no references to supporting files. The integration test suite, smoke test, vitest config, key rotation workflow, and CI workflow are all embedded directly. This would benefit greatly from splitting into separate referenced files (e.g., tests in one file, workflows in another), especially given the file exceeds 200 lines of content. | 1 / 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
6e9558f
- 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.