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.

Quality

68%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/shipping-and-launch/SKILL.md

Quality

Content

47%

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

This skill provides a comprehensive launch checklist with strong workflow clarity, particularly in the staged rollout sequence and decision thresholds. However, it is significantly too verbose—much of the content (common rationalizations, red flags, detailed security/accessibility checklists) is general knowledge Claude already possesses or duplicates referenced files. The skill would benefit greatly from aggressive trimming and better delegation to the referenced bundle files.

Suggestions

Remove the 'Common Rationalizations', 'Red Flags', and 'When to Use' sections entirely—Claude already knows these concepts and they consume significant tokens without adding actionable value.

Move the detailed Security, Performance, and Accessibility checklist sections into the referenced files (references/security-checklist.md, etc.) and keep only 1-2 line summaries with links in the main SKILL.md.

Remove the motivational Overview paragraph and replace with a single directive sentence like 'Follow this checklist for every production deployment.'

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 'Overview' paragraph is motivational fluff. Much of the checklist content (security headers, WCAG ratios, Core Web Vitals) is general knowledge Claude possesses. The skill could be cut by 50%+ without losing actionable value.	1 / 3
Actionability	Provides some concrete code examples (feature flag TypeScript, error boundary, rollback commands) and specific threshold tables, which is good. However, much of the content is checklist items and general guidance rather than executable, project-specific commands. The rollback plan is a template rather than executable steps, and many checklist items are generic reminders rather than actionable instructions.	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. The post-launch verification steps are sequenced with explicit checks. Feedback loops are present (monitor → decide → advance or roll back).	3 / 3
Progressive Disclosure	The 'See Also' section references three external files (security-checklist.md, performance-checklist.md, accessibility-checklist.md), which is good progressive disclosure. However, the main body contains extensive inline checklists for security, performance, and accessibility that duplicate what those referenced files presumably cover. The content that should be in those reference files is also inline, creating redundancy.	2 / 3
	Total	8 / 12 Passed

Description

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 its purpose and provides explicit trigger guidance through multiple 'Use when' clauses. The trigger terms are natural and well-chosen, covering the key scenarios a user would encounter. The main weakness is that the capability description could be more specific about concrete actions rather than listing high-level categories.

Suggestions

Make the opening statement more specific by listing concrete actions, e.g., 'Generates pre-launch checklists, configures monitoring dashboards, designs staged rollout plans, and creates rollback strategies for production deployments.'

Dimension	Reasoning	Score
Specificity	The description 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 opening 'Prepares production launches' is somewhat vague and the actions are more like categories than concrete specific tasks.	2 / 3
Completeness	Clearly answers both 'what' (prepares production launches) and 'when' with explicit 'Use when...' clauses covering 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

Validation

100%

Warnings & errors only

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: 5e262b2

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.