conductor-revert

Git-aware undo by logical work unit (track, phase, or task)

Quality

55%

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

77%Scale 1-3

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

This is a strong, highly actionable skill with excellent workflow clarity and safety guardrails for a destructive git operation. The multi-step process is well-sequenced with explicit validation checkpoints, confirmation requirements, and conflict handling. The main weaknesses are some boilerplate sections that don't add value and a monolithic structure that could benefit from splitting edge cases and templates into supporting files.

Suggestions

Remove the generic 'Use this skill when / Do not use this skill when' and 'Limitations' boilerplate sections—they add no value for this specific skill.

Move edge cases and display templates into a supporting file (e.g., resources/edge-cases.md or resources/templates.md) to reduce the main skill's token footprint and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill is fairly detailed and well-structured, but includes some unnecessary sections like the generic 'Use this skill when / Do not use this skill when' boilerplate and the 'Limitations' section which are filler. The ASCII art banners and verbose display templates add bulk. However, most content is genuinely instructive for a complex multi-step operation.	2 / 3
Actionability	The skill provides fully executable git commands (git log --oneline --grep, git revert --no-edit), specific argument formats with examples (auth_20250115:phase2, auth_20250115:task2.3), concrete display templates, and explicit decision trees for every scenario. The guidance is copy-paste ready and leaves no ambiguity about what to do.	3 / 3
Workflow Clarity	The workflow is exceptionally well-sequenced: pre-flight checks → target selection → commit discovery → execution plan display → explicit YES confirmation → revert execution → conflict handling with halt → plan.md updates → verification. Validation checkpoints are explicit throughout, with clear error recovery paths and a strict halt-on-conflict policy.	3 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` in the Instructions section but no bundle files are provided, making this reference unverifiable. The content is largely monolithic—all edge cases, display templates, and detailed workflows are inline rather than split into supporting files. For a skill of this length (~250 lines), some content like edge cases or display templates could be offloaded.	2 / 3
	Total	10 / 12 Passed

Description

32%Scale 1-3

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 too terse and lacks both concrete action details and explicit trigger guidance. While it hints at a specific niche (undoing git changes organized by logical work units), it doesn't explain what concrete operations it performs or when Claude should select it. The terminology 'track, phase, or task' is unclear without additional context.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to undo, revert, or rollback git changes grouped by track, phase, or task.'

List specific concrete actions the skill performs, e.g., 'Reverts commits, resets staged changes, and restores files organized by logical work units such as tracks, phases, or tasks.'

Include natural trigger terms users would say, such as 'revert', 'rollback', 'reset', 'undo changes', 'go back' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (git undo) and mentions organizing by 'logical work unit (track, phase, or task)', but doesn't list concrete actions like 'revert commits', 'reset staged changes', or 'restore files'.	2 / 3
Completeness	Provides a partial 'what' (git-aware undo by logical work unit) but completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'git' and 'undo' which are natural terms, but 'logical work unit', 'track', 'phase', and 'task' are domain-specific jargon that users may not naturally use. Missing common variations like 'revert', 'rollback', 'reset'.	2 / 3
Distinctiveness Conflict Risk	The 'logical work unit (track, phase, or task)' qualifier adds some distinctiveness from generic git skills, but 'git undo' is broad enough to potentially overlap with other git-related skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: popey/claude-code-skills
Path: skills/conductor-revert/SKILL.md
Commit: a5a6601

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