CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-prod-checklist

Execute Groq production deployment checklist and go-live procedures. Use when deploying Groq integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "groq production", "deploy groq", "groq go-live", "groq launch checklist".

70

Quality

87%

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

92%Weight 40%Scale 1-5

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

A high-quality, actionable production-deployment checklist with clear gated sequencing, explicit validation, and well-structured one-level-deep references. The only knock is minor redundancy between the inline alert table and the Section 6 monitoring alerts.

Suggestions

Consolidate the 'Error Handling' alert matrix with the Section 6 monitoring alerts into a single source of truth to remove the duplication and tighten conciseness toward 5.

DimensionReasoningScore

Conciseness

The body is a lean checklist that assumes Claude's competence and avoids explaining known concepts, but the alert matrix in 'Error Handling' partly duplicates the Section 6 monitoring alerts, a minor redundancy that could be trimmed.

4 / 5

Actionability

Checklist items are concrete (named model IDs, exact thresholds like 'p95 > 1s' and 'error rate > 5%', a pre-commit `gsk_` hook), the inline TypeScript fallback skeleton is copy-paste ready, and references hold complete executable scripts.

5 / 5

Workflow Clarity

Nine gates are sequenced top-to-bottom as explicit validation checkpoints ('each section is a gate that must be green before the go-live verification runs'), with a final pre-flight verification, a go/no-go decision rule, and severity-graded blockers — a checklist with feedback loops for a risky go-live.

5 / 5

Progressive Disclosure

SKILL.md is a scannable overview and the deep code (fallback function, health endpoint, go-live script) is split into one-level-deep references (implementation.md, go-live.md) that are linked inline at the relevant steps; no nested reference chains exist.

5 / 5

Total

19

/

20

Passed

Description

82%Weight 40%Scale 1-5

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 well-formed trigger-focused description that clearly states what the skill does and when to use it, with natural trigger phrases and a distinct niche. Its only weakness is specificity: the action summary under-represents the breadth of gates the body actually covers.

Suggestions

Expand the action clause to hint at the full scope, e.g. 'Execute Groq production deployment checklist covering API key security, model selection, rate limits, fallback, and monitoring' — this would lift specificity toward 4-5 without padding.

DimensionReasoningScore

Specificity

The description names the domain ('Groq production deployment') and two concrete actions ('Execute ... checklist and go-live procedures'), but the action list is not comprehensive — the body covers key security, rate limits, fallback, and monitoring, none of which surface here.

3 / 5

Completeness

It explicitly answers both 'what' ('Execute Groq production deployment checklist and go-live procedures') and 'when' ('Use when deploying Groq integrations to production, preparing for launch, or implementing go-live procedures') with concrete trigger phrases.

5 / 5

Trigger Term Quality

It supplies four natural phrases a user would plausibly say ('groq production', 'deploy groq', 'groq go-live', 'groq launch checklist'); coverage is good but lacks synonyms or obvious variants a user might also try.

4 / 5

Distinctiveness Conflict Risk

The Groq-production-deployment niche is narrow and the triggers are Groq-specific, so overlap with unrelated skills is minimal; voice is correctly third person.

5 / 5

Total

17

/

20

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.