managing-deployment-rollbacks

Deploy 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".

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/devops/deployment-rollback-manager/skills/managing-deployment-rollbacks/SKILL.md

Quality

Content

77%

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

The body is concise, well-structured, and has a clear validated workflow with feedback loops, scoring well on conciseness and workflow clarity. Its main weakness is actionability and progressive disclosure: the bundled scripts and templates that should carry the executable detail are not referenced or invoked anywhere in SKILL.md.

Suggestions

Reference and invoke the bundled scripts in the relevant steps, e.g. 'Run `python scripts/get_previous_version.py` to identify the target revision' and 'Execute `python scripts/rollback_deployment.py`'.

Link the templates the body claims as outputs, e.g. 'Post-incident report: see [assets/rollback_report_template.md](assets/rollback_report_template.md)'.

Add concrete commands for ECS and Lambda rollback (e.g. aws ecs update-service / aws lambda update-alias) instead of descriptive steps.

Dimension	Reasoning	Score
Conciseness	The body is lean and information-dense — prerequisites, numbered steps, an error-handling table, and resource links — without explaining concepts Claude already knows (kubectl, ECS, Lambda). Every section earns its place.	3 / 3
Actionability	One concrete command appears ('kubectl rollout undo deployment/<name>'), but ECS ('update the service to use the previous task definition revision') and Lambda ('point the alias back') are descriptive, and the bundled scripts (rollback_deployment.py, verify_deployment.py) are never invoked or referenced.	2 / 3
Workflow Clarity	A clear 9-step sequence runs detect → assess → rollback → verify DB compatibility → confirm success → report → automate, with explicit validation checkpoints (steps 6 and 7) and an error-handling table providing feedback loops for this risky operation.	3 / 3
Progressive Disclosure	Sections are well organized, but bundle files that clearly map to stated deliverables — scripts/rollback_deployment.py, assets/rollback_report_template.md, assets/rollback_template.yml — exist yet are never linked or signaled from the body, so navigation to the executable content is missing.	2 / 3
	Total	10 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has explicit trigger phrasing but is vague on capabilities, over-claims ('comprehensive guidance and automation'), and critically omits 'rollback' — the skill's actual purpose — creating a mismatch between description and skill. Trigger terms are natural but incomplete.

Suggestions

Lead with the core capability, e.g. 'Detect failed deployments and revert to the last known good version for Kubernetes, ECS, Lambda, and cloud VMs.'

Replace vague 'automation and orchestration with comprehensive guidance and automation' with concrete actions: rollback, verify health, generate post-incident reports.

Add rollback-oriented trigger phrases users would actually say: 'rollback deployment', 'revert to previous version', 'undo a failed deploy'.

Dimension	Reasoning	Score
Specificity	Names the deployment/CI-CD domain and a few actions ('deploy application', 'create pipeline', 'automate deployment'), but the capability statement 'deployment automation and orchestration with comprehensive guidance and automation' is vague, redundant, and over-claiming rather than listing multiple concrete actions.	2 / 3
Completeness	Explicit 'when' trigger guidance is present ('Trigger with phrases like...'), but the 'what' is weak — it never mentions rollback, the skill's core function — so it does not clearly answer both what and when at the top anchor.	2 / 3
Trigger Term Quality	Phrases like 'deploy application', 'create pipeline', 'automate deployment' are natural, but coverage is limited and notably omits the skill's actual purpose (rollback/revert/undo deployment), so common variations are missing.	2 / 3
Distinctiveness Conflict Risk	'Deployment and CI/CD' with triggers like 'create pipeline' and 'automate deployment' is broad DevOps territory that could overlap with many general deployment/pipeline skills, and nothing distinguishes the rollback niche.	2 / 3
	Total	8 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/deployment-rollback-manager/skills/managing-deployment-rollbacks/SKILL.md
Commit: 15940c5

Reviewed: 4 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.