CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rollback-strategy-advisor

Suggests rollback strategies for failed deployments across different platforms and failure types. Use when deployments fail and need to be reverted, including application code rollbacks, database migration reversions, infrastructure changes, and configuration updates. Supports Docker/Docker Compose environments with step-by-step procedural guidance for safe and effective rollback execution.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The body is highly actionable with executable commands and a well-sequenced, validation-rich workflow that appropriately handles its destructive operations. Its main weaknesses are redundancy (duplicated best-practices lists, quick-reference restatements, generic communication templates) and inlining Docker platform detail that overlaps the provided platform_guides.md reference, plus a missing explicit failure-recovery loop after validation.

Suggestions

Merge the final 'Best Practices' section into Step 6's overlapping list and remove the 'Quick Reference' command restatements and generic Slack/incident templates (or move them to a reference file) to cut roughly 100 lines of duplication.

Defer Docker platform specifics in Step 3.3 (network, volume, compose revert procedures) and the rollback.sh script to references/platform_guides.md with a one-line pointer, keeping only the decision-relevant summary in the body.

Add an explicit feedback loop to Step 4: instruct that if post-rollback health checks or functional tests fail, restore the pg_dump backup taken in Step 3.4 and re-attempt with an alternate strategy before proceeding.

DimensionReasoningScore

Conciseness

The command blocks are lean and no basic concepts are re-explained, but the 542-line body contains several padded or duplicated sections: the 'Core Capabilities' preamble describing what the skill does, a final 'Best Practices' list of 10 items that largely repeats Step 6's list, a 'Quick Reference' that restates commands already shown in Steps 3.x, and generic Slack/incident-report templates Claude can produce unaided. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') better than anchor 4, whose over-explanation is only 'minor instances'.

3 / 5

Actionability

The guidance is fully executable with copy-paste-ready bash sequences for every rollback type (docker-compose stop/up, sed tag substitution, git checkout of prior configs, alembic downgrade, pg_dump backups), a complete runnable rollback.sh script, and concrete validation commands, covering the common cases exactly as anchor 5 requires. It is above anchor 4 because there are no meaningful gaps — placeholders like <service-name> are appropriate parameterization, not missing detail.

5 / 5

Workflow Clarity

A clear 6-step sequence (Assess → Choose → Execute → Validate → Document → Prevent) with a strategy decision tree, a dedicated Step 4 validation (health checks, functional tests, an explicit checklist), and validation commands embedded in each execution step, satisfying anchor 4. It falls short of anchor 5 because there is no explicit error-recovery feedback loop — nothing says what to do when post-rollback validation fails (e.g., restore from the pg_dump backup or try an alternate strategy).

4 / 5

Progressive Disclosure

Both bundle references (references/database_rollback_patterns.md and references/platform_guides.md) exist, are one level deep, and are clearly signaled with descriptions in a Resources section plus one inline pointer in Step 3.4, matching anchor 4. It is not anchor 5 because substantial Docker platform detail in the body (Step 3.3 network/volume/compose procedures, the rollback script) duplicates what platform_guides.md covers instead of deferring to it, and only one of the two references is pointed to inline where its topic is discussed.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

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

A strong description that explicitly answers both what it does and when to use it, with concrete failure-type triggers, third-person voice, and no filler. Minor deductions for a single advisory action rather than multiple concrete operations, a few missing trigger synonyms, and a slight 'across different platforms' over-claim given Docker-only support.

DimensionReasoningScore

Specificity

The description lists several specific capability areas ("application code rollbacks, database migration reversions, infrastructure changes, and configuration updates") plus a named platform ("Docker/Docker Compose"), matching anchor 4's 'several specific actions; minor gaps'. It falls short of anchor 5 because the core action is a single advisory one ('Suggests rollback strategies') applied to multiple object types rather than multiple distinct concrete operations, and 'across different platforms' slightly over-claims relative to the Docker-only support stated.

4 / 5

Completeness

Both questions are explicitly answered: what ("Suggests rollback strategies for failed deployments across different platforms and failure types") and when ("Use when deployments fail and need to be reverted, including application code rollbacks, database migration reversions...") with concrete trigger phrases, exactly matching anchor 5. The explicit 'Use when' clause with enumerated scenarios exceeds anchor 4's softer 'when'.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "deployments fail", "need to be reverted", "rollback", and concrete failure-type terms ("database migration", "configuration updates"), matching anchor 4's good keyword coverage. It is not anchor 5 because common synonyms such as "undo deploy", "revert to previous version", or "restore" are missing.

4 / 5

Distinctiveness Conflict Risk

"Rollback" and "failed deployments" form a clear niche with distinct triggers, but "deployments" is broad enough to overlap with general CI/CD or Docker deployment skills, matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (547 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

ArabelaTso/Skills-4-SE

Path

skills/rollback-strategy-advisor/SKILL.md

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.