exa-prod-checklist
Execute Exa production deployment checklist with pre-flight, deploy, and rollback. Use when deploying Exa integrations to production, preparing for launch, or verifying production readiness. Trigger with phrases like "exa production", "deploy exa to prod", "exa go-live", "exa launch checklist", "exa production ready".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that clearly defines its scope (Exa production deployment), lists concrete actions (pre-flight, deploy, rollback), and provides explicit trigger guidance with natural user phrases. It uses proper third-person voice and is concise without being vague. The description would perform well in a large skill library due to its distinctive Exa-specific focus.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'pre-flight, deploy, and rollback' as part of a production deployment checklist. These are distinct, actionable phases of a deployment process. | 3 / 3 |
Completeness | Clearly answers both 'what' (execute deployment checklist with pre-flight, deploy, and rollback) and 'when' (deploying to production, preparing for launch, verifying production readiness) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'exa production', 'deploy exa to prod', 'exa go-live', 'exa launch checklist', 'exa production ready', plus contextual phrases like 'deploying Exa integrations to production' and 'production readiness'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Exa' product name and 'production deployment checklist' scope. The trigger terms are narrowly scoped to Exa production deployments, making conflicts with other skills very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable production deployment skill with excellent workflow clarity and concrete, executable code at every step. Its main weakness is moderate verbosity—some content could be offloaded to supporting files—and minor redundancy between the checklist and error handling sections. The sequential deploy procedure with validation gates and rollback is well-designed for a high-stakes operation.
Suggestions
Remove the overview paragraph—the title and structure already communicate the purpose clearly.
Consider extracting the detailed checklists (Security, Code Quality, Performance, Monitoring) and reference tables into a separate CHECKLIST.md to keep SKILL.md as a lean workflow guide with pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some sections that could be tightened—the checklist items are well-structured but the error handling table partially duplicates information already covered in the checklist. The overview paragraph is unnecessary. Overall mostly lean but not maximally token-efficient. | 2 / 3 |
Actionability | Provides fully executable bash scripts, TypeScript code for health checks, concrete kubectl commands for rollout and rollback, and specific curl commands for verification. All code is copy-paste ready with real API endpoints and proper error handling (set -euo pipefail, exit codes). | 3 / 3 |
Workflow Clarity | The deploy procedure is clearly sequenced (pre-flight → health check → gradual rollout → post-deployment verification → rollback) with explicit validation at each step. The canary pattern includes a monitoring pause before full rollout, and the rollback procedure is clearly defined with verification. Feedback loops are present (tests must pass before proceeding, health checks gate rollout). | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's a fairly long monolithic file with no bundle files to offload detailed content. The references to 'exa-upgrade-migration' and 'exa-incident-runbook' at the end suggest related skills but these aren't provided. The alert thresholds table and error handling table could potentially be separate references for a cleaner overview. | 2 / 3 |
Total | 10 / 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
3a2d27d
- 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.