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

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A highly actionable, token-efficient production checklist with executable code, a gated go-live verification step, and concrete thresholds. The main gap is progressive disclosure: all detail sits in one monolithic file with no reference bundle to split it out.

Suggestions

Move the full TypeScript fallback/health-check implementations and the alert-threshold table into a references/ file, keeping SKILL.md as a lean overview with one-level-deep links.

Resolve the duplicate "## Error Handling" header (the checklist section and the alert table share the same title) to avoid navigation ambiguity.

DimensionReasoningScore

Conciseness

The body is almost entirely dense, actionable checklists and complete code/bash snippets with no padding or explanation of concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

It provides copy-paste-ready TypeScript fallback and health-check code, concrete model IDs, specific alert thresholds, and an executable bash go-live verification script with real curl/jq commands.

3 / 3

Workflow Clarity

The structure sequences Prerequisites → Pre-Deployment Checklist → Go-Live Verification, and the go-live script is an explicit validation gate with `set -euo pipefail` and numbered pre-flight checks plus a feedback/fallback loop.

3 / 3

Progressive Disclosure

Content is well organized into clear sections but everything lives inline in a single ~190-line SKILL.md with no bundle files to offload detail; cross-skill references like `groq-incident-runbook` are signaled but no progressive file structure exists.

2 / 3

Total

11

/

12

Passed

Description

90%

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 description that clearly conveys both purpose and trigger conditions in third person with natural trigger phrases. It is only slightly limited on specificity, listing two broad actions rather than several concrete ones.

Suggestions

Expand the capability statement beyond the two broad actions (e.g. add verifying API keys, configuring rate-limit backoff, and setting up monitoring) to reach the multi-action specificity anchor.

DimensionReasoningScore

Specificity

Names the domain and two actions ("Execute Groq production deployment checklist" and "go-live procedures") but does not enumerate multiple distinct concrete capabilities, falling short of the comprehensive multi-action anchor.

2 / 3

Completeness

It states 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 explicit triggers.

3 / 3

Trigger Term Quality

Explicit trigger phrases like "groq production", "deploy groq", "groq go-live", and "groq launch checklist" are natural terms a user would actually say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The Groq-production niche with distinctive "groq go-live" / "groq launch checklist" triggers is unlikely to collide with other skills.

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.