skill-rollback

Roll back to a previous checkpoint via git — use when a change went wrong and you need to revert

Quality

87%

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

Quality

Content

92%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 copy-paste git commands and a well-sequenced 8-step rollback workflow reinforced by explicit validation (confirmation gate, safety checkpoint, STOP guard) and clear self-contained sectioning. The only notable weakness is mild repetition across the safety tables and inline emphasis notes.

Dimension	Reasoning	Score
Conciseness	Largely lean with copy-paste bash snippets and tables assuming Claude's git knowledge, but the Safety Measures table, Red Flags table, and inline CRITICAL notes repeat guidance already covered in the step sequence, and the Quick Reference repeats the mode-detection table.	4 / 5
Actionability	Provides fully executable, copy-paste-ready git commands with real flags (e.g. `git tag -l "octo-checkpoint-*" --sort=-creatordate --format=...` and `git checkout $CHECKPOINT_TAG -- .`) covering listing, validation, preview, safety checkpointing, execution, and reporting.	5 / 5
Workflow Clarity	An explicit 8-step sequence with strong validation checkpoints — tag-not-found leads to 'STOP. Do not proceed.', a mandatory 'ROLLBACK' confirmation, a pre-rollback safety checkpoint, and a preview of affected files — satisfying the destructive-operation validation requirement rather than triggering the cap.	5 / 5
Progressive Disclosure	No bundle files exist and none are needed; the skill is self-contained with clearly headed, well-organized sections (Subcommand Detection, LIST, ROLLBACK, Safety Measures, Red Flags, Tag Format, Quick Reference) that navigate easily, which the rubric permits to score 5 for well-structured single-file skills.	5 / 5
	Total	19 / 20 Passed

Description

82%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.

The description concisely and explicitly states both what the skill does (rollback to a git checkpoint) and when to use it (a change went wrong, need to revert), with natural trigger terms. Its only weakness is single-action specificity rather than comprehensive action coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (git checkpoint rollback) and one concrete action ('Roll back to a previous checkpoint via git') but does not list multiple specific actions, so it sits at the '1-2 concrete actions' anchor rather than comprehensive coverage.	3 / 5
Completeness	Explicitly answers both what ('Roll back to a previous checkpoint via git') and when ('use when a change went wrong and you need to revert') with a concrete trigger clause.	5 / 5
Trigger Term Quality	Includes natural phrases users say ('change went wrong', 'need to revert', 'roll back') with good coverage, though synonyms like 'undo' or 'go back to' are absent from the description text itself.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (git checkpoint rollback) with distinct triggers tied to checkpoint tags, giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nyldn/claude-octopus
Path: .claude/skills/skill-rollback/SKILL.md
Commit: 805d58c

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.