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".
91
91%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured description with strong completeness and trigger term coverage. Its main weakness is the lack of specific concrete actions—it says 'checklist and go-live procedures' without detailing what those procedures actually entail (e.g., API key rotation, rate limit configuration, health check setup). The distinctiveness is excellent due to the Groq-specific focus.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Validates API configurations, sets rate limits, configures monitoring, runs health checks, and verifies error handling for Groq production deployments.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Groq production deployment) and mentions 'checklist and go-live procedures,' but doesn't list specific concrete actions like 'configure API keys, set rate limits, validate endpoints, enable monitoring.' The actions remain at a high level. | 2 / 3 |
Completeness | Clearly answers both 'what' (execute Groq production deployment checklist and go-live procedures) and 'when' (deploying Groq integrations to production, preparing for launch, implementing go-live procedures) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'groq production', 'deploy groq', 'groq go-live', 'groq launch checklist' which are natural terms a user would say. Also includes variations like 'deploying Groq integrations to production' and 'go-live procedures.' | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Groq' (a specific platform) with 'production deployment' and 'go-live' creates a very distinct niche. It's unlikely to conflict with other skills unless there are multiple Groq-related skills, and even then the production/deployment focus narrows it well. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality production checklist skill that is actionable, well-structured, and token-efficient. It provides concrete code examples, specific thresholds, and a clear deployment sequence with validation steps. The only minor weakness is that the content is somewhat lengthy for a single file, though the checklist format keeps it scannable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place—checklists are terse, code examples are functional and necessary, and there's no explanation of basic concepts. The skill assumes Claude knows what circuit breakers, exponential backoff, and health endpoints are. | 3 / 3 |
Actionability | Provides fully executable TypeScript code for fallback and health check, a complete bash verification script, specific model names, concrete threshold values (80% of limits, p95 > 1s), and copy-paste ready checklist items with specific patterns like `gsk_`. | 3 / 3 |
Workflow Clarity | The skill follows a clear sequence: prerequisites → pre-deployment checklist → go-live verification → error handling/alerting. The go-live verification script is an explicit validation checkpoint with numbered steps, and the fallback code includes a feedback loop (primary → fallback → graceful degradation). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and references to external resources, but the inline content is quite long (~150 lines). The incident runbook and upgrade migration are referenced as separate skills, but the monitoring setup, error handling table, and code examples could potentially be split out for better navigation. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
4dee593
- 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.