CtrlK
BlogDocsLog inGet started
Tessl Logo

deepgram-prod-checklist

Execute Deepgram production deployment checklist. Use when preparing for production launch, auditing production readiness, or verifying deployment configurations. Trigger: "deepgram production", "deploy deepgram", "deepgram prod checklist", "deepgram go-live", "production ready deepgram".

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 content is highly actionable and token-efficient, with complete executable code throughout. Its main weaknesses are the absence of explicit validation checkpoints in the deployment workflow and an unreferenced, duplicative bundle file that underuses progressive disclosure.

Suggestions

Add explicit validation/verify checkpoints between deployment steps (e.g., "Verify all readiness-matrix items are checked before proceeding to Step 2") to raise workflow clarity.

Either reference references/implementation.md from the body (e.g., "For full implementation details, see implementation.md") or remove the duplicate code from one location to avoid redundancy and improve signaling.

De-duplicate the metrics/alert code that appears in both SKILL.md and references/implementation.md, keeping the body as a concise overview and pushing full implementations to the reference file.

DimensionReasoningScore

Conciseness

The body is dense with executable code and configuration and avoids explaining concepts Claude already knows; nearly every line is actionable rather than padded.

3 / 3

Actionability

Six complete, copy-paste-ready TypeScript and YAML blocks with concrete values (model 'nova-3', 30000ms timeout, specific histogram buckets, alert expressions) give fully executable guidance.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1-6 plus a D-7 to D+7 timeline) but lack explicit validation/verify checkpoints between steps for a risky deployment operation, capping it below 3.

2 / 3

Progressive Disclosure

A bundle file references/implementation.md exists but is never referenced from the body and largely duplicates the inline code, so content that should be split is instead duplicated inline with poor signaling.

2 / 3

Total

10

/

12

Passed

Description

90%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.

A strong, well-structured description that answers both what and when with explicit, natural trigger phrases and a distinct niche. The only minor weakness is specificity, since it frames the skill as a single checklist action rather than enumerating the concrete capabilities it covers.

DimensionReasoningScore

Specificity

The description names the domain and a single high-level action ("Execute Deepgram production deployment checklist") but does not enumerate multiple concrete capabilities like the score-3 anchor does.

2 / 3

Completeness

It states both what it does ("Execute Deepgram production deployment checklist") and when to use it ("Use when preparing for production launch, auditing production readiness, or verifying deployment configurations").

3 / 3

Trigger Term Quality

It provides five natural trigger phrases ("deepgram production", "deploy deepgram", "deepgram prod checklist", "deepgram go-live", "production ready deepgram") that a user would plausibly say.

3 / 3

Distinctiveness Conflict Risk

The Deepgram-specific production deployment niche is narrow and uses distinct trigger terms, making conflict with other skills unlikely.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.