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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

An actionable, token-efficient checklist with strong executable examples, but it is monolithic rather than progressively disclosed and lacks explicit validation checkpoints in its deployment workflow.

Suggestions

Add explicit validation/feedback checkpoints to the Steps 1-6 sequence (e.g., 'verify the /health endpoint returns healthy before instrumenting metrics') so the deployment workflow has validate-then-proceed loops.

Link the existing references/implementation.md from the body (e.g., a '## Implementation details: See [implementation.md](references/implementation.md)') and move the longer code blocks there to split the monolith one level deep.

Reconcile the inline code (nova-3) with implementation.md (nova-2) to avoid a stale version contradiction now that the detail file is referenced.

Dimension	Reasoning	Score
Conciseness	Lean body of tables and executable code with minimal prose; it does not explain concepts Claude already knows and every section earns its place.	3 / 3
Actionability	Provides fully executable TypeScript singleton/health-check/metrics/error-wrapper code and AlertManager YAML that is copy-paste ready, not pseudocode.	3 / 3
Workflow Clarity	Steps 1-6 are sequenced and the go-live timeline has review phases, but the implementation steps lack explicit validate-then-proceed feedback loops for a risky production-deployment operation, capping this at 2.	2 / 3
Progressive Disclosure	Sections are organized, but all code lives inline in a ~280-line monolith and the bundled references/implementation.md is never signaled or linked from the body, so content that should be split out is not navigable.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, third-person description with concrete actions, an explicit Use-when clause, and natural trigger terms scoped to a clear Deepgram-production niche. No first/second-person voice or vague fluff.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Execute Deepgram production deployment checklist', 'preparing for production launch', 'auditing production readiness', 'verifying deployment configurations' — rather than vague language.	3 / 3
Completeness	Clearly answers both what ('Execute Deepgram production deployment checklist') and when via an explicit 'Use when...' clause, satisfying the top anchor.	3 / 3
Trigger Term Quality	Explicit Trigger list ('deepgram production', 'deploy deepgram', 'deepgram prod checklist', 'deepgram go-live', 'production ready deepgram') gives good coverage of natural phrases a user would say.	3 / 3
Distinctiveness Conflict Risk	Deepgram-specific niche with distinct triggers makes it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 2 days 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.