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".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code throughout, but it is monolithic — everything inline despite a reference file that duplicates rather than extends it — and the key rotation step lacks a verification feedback loop.

Suggestions

Move the full integration test suite and duplicated workflows into references/implementation.md and link to it from SKILL.md, keeping only a concise quick-start excerpt inline to improve both conciseness and progressive disclosure.

Add an explicit verification step to the key rotation workflow (e.g., run the smoke test with the new key before considering rotation complete) so the destructive operation has a feedback loop.

Link to references/implementation.md from the body (e.g., a "## Advanced / alternate CI providers" section) and de-duplicate it against the inline content so the reference is signaled and one level deep.

Dimension	Reasoning	Score
Conciseness	The body is ~280 lines of mostly inline complete files (a full 5-case integration test suite, smoke test, package.json, vitest config, key rotation) plus an "Output" section restating deliverables; it is efficient in that it avoids concept explanation, but could be tightened by pushing full files to the reference.	2 / 3
Actionability	All guidance is concrete, copy-paste-ready YAML/TypeScript/JSON with real file paths ("tests/integration/deepgram.test.ts"), specific commands ("npm run test:integration"), and real model names ("nova-3").	3 / 3
Workflow Clarity	Steps are sequenced (Step 1–6) with needs-based job gating and an Error Handling table, but the key rotation workflow — a destructive/batch operation — performs no verification of the new key, which caps workflow clarity at 2 per the rubric scoring notes.	2 / 3
Progressive Disclosure	The body is monolithic with all content inline; references/implementation.md exists but is never linked from the body and duplicates the inline workflows/tests rather than holding deeper material, so references are present but not signaled.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, third-person, and answers both what the skill does and when to use it, with an explicit set of natural trigger terms. It is a strong, well-scoped description with no over-claims.

Dimension	Reasoning	Score
Specificity	"Configure Deepgram CI/CD integration for automated testing and deployment" names multiple concrete actions (configure integration, automated testing, deployment) rather than vague language, matching the level-3 anchor.	3 / 3
Completeness	It states what ("Configure Deepgram CI/CD integration for automated testing and deployment") and when ("Use when setting up continuous integration pipelines, automated testing, or deployment workflows for Deepgram integrations") with explicit triggers, answering both clearly.	3 / 3
Trigger Term Quality	The explicit Trigger list ("deepgram CI", "deepgram CD", "deepgram pipeline", "deepgram github actions", "deepgram automated testing") gives good coverage of natural phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Every trigger is Deepgram-prefixed and the domain is a clear niche (CI/CD for Deepgram integrations), making it unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/deepgram-pack/skills/deepgram-ci-integration/SKILL.md
Commit: 0540a62

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.