conductor-revert

Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.

Quality

70%

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 ./skills/conductor-revert/SKILL.md

Quality

Content

81%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 content is a well-structured, executable workflow with strong validation checkpoints and clear handling of a destructive operation. It is lean and actionable, with only minor repetition and a few abstract steps.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes Claude's competence; no over-explanation of Git basics. Minor instances of repeated phrasing (e.g., re-stating the Default Paths resolution protocol in multiple sections) could be trimmed. Not a 5 due to that repetition; not a 3 because the bulk is lean.	4 / 5
Actionability	Provides concrete executable commands ('git revert --no-edit <sha>', 'git reset --hard <base_sha>', 'git log -- <path>') with specific file paths and menu options. Not a 5 because some steps remain abstract ('Search the Git log for a commit with a highly similar message') without exact commands.	4 / 5
Workflow Clarity	Five clearly sequenced phases with explicit validation checkpoints, halt-on-failure conditions, conflict-handling feedback loops, and prominent warnings around the destructive reset operation. This matches the anchor for clear sequence with explicit validation and error-recovery loops.	5 / 5
Progressive Disclosure	Single self-contained file with well-organized, clearly headed sections and no nested references; appropriate for a skill of this size. Not a 5 only because there is no overview-to-detail split that would benefit from offloading reference material.	4 / 5
	Total	17 / 20 Passed

Description

58%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 is specific and action-oriented but omits any 'Use when...' trigger guidance, which caps its completeness. It is distinctive within the Conductor framework and names concrete Git revert actions.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases such as 'Use when the user wants to undo, revert, or rollback Conductor tracks, phases, or tasks.'

Broaden trigger-term coverage with natural synonyms users say ('undo my work', 'rollback', 'revert these commits').

Mention the safety distinction (safe revert vs. destructive reset) to sharpen specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('identifying associated commits', 'performing Git reverts') scoped to tracks, phases, and tasks, with minor gaps around strategy choice and conflict handling. Not a 5 because it omits verification and strategy actions; not a 3 because it goes beyond 1-2 actions.	4 / 5
Completeness	Clearly states what the skill does (reverts work by finding commits and running Git reverts), but provides no 'Use when...' trigger clause. Per the rubric guideline, a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural keywords like 'reverts' and 'Git reverts' and 'commits', but lacks common synonyms users would say (e.g., 'undo', 'rollback') and any file extensions. Solid but missing natural variations.	3 / 5
Distinctiveness Conflict Risk	Targets a specific niche (Conductor-tracked work reverted via Git), mostly distinct with only minor overlap risk against a generic git-revert skill. Not a 5 because Git reverts alone is a broadly applicable concept.	4 / 5
	Total	14 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: gemini-cli-extensions/conductor
Path: skills/conductor-revert/SKILL.md
Commit: f06add3

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