shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
60
68%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/shipping-and-launch/SKILL.mdQuality
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 solid skill description that clearly communicates when it should be used through explicit trigger clauses and natural keywords. Its main weakness is that the core capability statement is somewhat high-level—it could benefit from listing more specific concrete actions beyond the trigger scenarios. Overall it performs well for skill selection purposes.
Suggestions
Expand the initial capability statement to list more specific concrete actions, e.g., 'Generates pre-launch checklists, configures monitoring dashboards, designs staged rollout plans, and creates rollback procedures for production deployments.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (production launches) and mentions some actions like 'pre-launch checklist', 'setting up monitoring', 'planning a staged rollout', and 'rollback strategy', but the primary capability statement 'Prepares production launches' is fairly high-level and doesn't list concrete detailed actions (e.g., it doesn't specify what the checklist covers, what monitoring tools, etc.). | 2 / 3 |
Completeness | Clearly answers both 'what' (prepares production launches) and 'when' with an explicit 'Use when...' clause listing multiple trigger scenarios: deploying to production, needing a pre-launch checklist, setting up monitoring, planning staged rollouts, or needing rollback strategies. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'deploy to production', 'pre-launch checklist', 'monitoring', 'staged rollout', 'rollback strategy'. These cover a good range of terms a user would naturally use when preparing for a production deployment. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around production deployment preparation with distinct triggers like 'pre-launch checklist', 'staged rollout', and 'rollback strategy' that are unlikely to conflict with other skills such as general DevOps or CI/CD pipeline skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a comprehensive launch workflow with strong sequencing and decision thresholds, but is far too verbose for a skill file. It includes extensive generic checklists (security, performance, accessibility) inline that duplicate the referenced external files and contain knowledge Claude already possesses. The motivational content and 'Common Rationalizations' table waste significant token budget.
Suggestions
Remove or drastically shorten the inline security, performance, and accessibility checklists since they're already referenced as external files — move that content to the bundle files instead.
Remove the 'Common Rationalizations' table and 'Red Flags' section entirely — these are motivational/cultural points Claude doesn't need.
Cut the 'When to Use' section and the overview paragraph — Claude can infer when to use a launch checklist from the skill description.
Remove the 'When to Roll Back' bullet list since the same information is already captured in the rollout decision thresholds table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~250+ lines. The 'Common Rationalizations' table, 'When to Use' section, and 'Red Flags' list explain things Claude already knows. The security, performance, and accessibility checklists are generic best-practice lists that don't add novel knowledge. Much of this content is motivational rather than instructional ('Ship with confidence', 'Rolling back is responsible engineering'). | 1 / 3 |
Actionability | Contains some concrete code examples (feature flag TypeScript, error boundary) and specific threshold tables for rollout decisions, which is good. However, much of the content is checklist items and general guidance rather than executable commands specific to a particular stack. The rollback plan is a template rather than executable steps. | 2 / 3 |
Workflow Clarity | The staged rollout sequence is clearly numbered with explicit validation checkpoints at each stage. The rollout decision thresholds table provides concrete advance/hold/rollback criteria. Post-launch verification steps are sequenced. The feature flag lifecycle is well-defined with clear progression and feedback loops. | 3 / 3 |
Progressive Disclosure | References to external files (references/security-checklist.md, references/performance-checklist.md, references/accessibility-checklist.md) are present but no bundle files exist to support them. The SKILL.md itself is monolithic with inline checklists for security, performance, and accessibility that could be in those referenced files instead, creating redundancy. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- addyosmani/agent-skills
- Commit
f17c6e8
- 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.