managing-deployment-rollbacks
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-deployment-rollbacksDeploy use when you need to work with deployment and CI/CD. This skill provides deployment automation and orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill is a generic template masquerading as deployment rollback guidance. It contains no actual rollback-specific content—no commands for reverting deployments, no tool integrations (Kubernetes, Docker, cloud providers), no database rollback strategies, and no concrete examples. The content could apply to literally any IT task and provides zero value beyond what Claude already knows about general software development practices.
Suggestions
Add concrete rollback commands for specific platforms (e.g., `kubectl rollout undo deployment/app`, `aws ecs update-service --force-new-deployment`, `docker service rollback`)
Include executable code examples showing how to check deployment history, identify rollback targets, and verify rollback success
Replace generic prerequisites and steps with rollback-specific workflows including database migration reversal, feature flag toggling, and traffic shifting
Add specific validation checkpoints like 'Verify previous image/artifact exists: `docker images | grep app`' and 'Confirm health checks pass after rollback'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that Claude already knows. Phrases like 'Understanding of the system architecture' and 'Backup of critical data before making structural changes' are obvious prerequisites that waste tokens. The entire content reads like a template with no specific, actionable information about deployment rollbacks. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples anywhere. Every instruction is abstract ('Execute implementation', 'Run comprehensive tests', 'Monitor for any issues') with zero specifics about HOW to perform deployment rollbacks. No actual rollback commands, scripts, or tool-specific guidance. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic project management phases rather than specific rollback procedures. No validation checkpoints specific to rollbacks (e.g., 'verify previous deployment artifact exists', 'confirm database migration reversibility'). Missing critical rollback-specific feedback loops. | 2 / 3 |
Progressive Disclosure | References external files (templates, docs, examples) which is good structure, but the main content is a wall of generic text. The referenced files use placeholder paths ({baseDir}) and may not exist. The 'Overview' and 'Examples' sections at the bottom are empty placeholders. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
40%This description suffers from vague, buzzword-heavy language ('comprehensive guidance and automation') without specifying concrete capabilities. While it attempts to provide trigger phrases, the core functionality remains unclear, making it difficult for Claude to confidently select this skill over alternatives.
Suggestions
Replace 'comprehensive guidance and automation' with specific actions like 'Configure CI/CD pipelines, manage deployment rollbacks, set up staging environments, integrate with GitHub Actions/Jenkins'
Expand trigger terms to include common variations: 'CI/CD', 'release to production', 'GitHub Actions', 'deployment pipeline', 'continuous integration'
Specify supported platforms or tools to increase distinctiveness (e.g., 'Works with AWS, Kubernetes, Docker, GitHub Actions')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'deployment automation and orchestration' and 'comprehensive guidance' without listing concrete actions. No specific capabilities like 'configure CI/CD pipelines', 'manage rollbacks', or 'set up staging environments' are mentioned. | 1 / 3 |
Completeness | Has a 'Use when' clause and trigger phrases addressing 'when', but the 'what' is extremely vague ('comprehensive guidance and automation'). The description doesn't clearly explain what specific tasks the skill actually performs. | 2 / 3 |
Trigger Term Quality | Includes some relevant trigger phrases ('deploy application', 'create pipeline', 'automate deployment') but misses common variations users might say like 'CI/CD', 'release', 'push to production', 'GitHub Actions', 'Jenkins', or specific platform names. | 2 / 3 |
Distinctiveness Conflict Risk | The deployment/CI/CD domain is somewhat specific, but 'automation and orchestration' is broad enough to potentially overlap with infrastructure, DevOps, or general automation skills. Lacks specific differentiators. | 2 / 3 |
Total | 7 / 12 Passed |
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.