conductor-revert

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

Quality

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/conductor-revert/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.

This is a well-crafted, highly actionable skill with excellent workflow clarity, strong safety guardrails, and thorough edge case handling. Its main weaknesses are moderate verbosity (boilerplate sections, verbose ASCII display templates) and a monolithic structure that could benefit from splitting detailed edge cases and output templates into separate reference files. The reference to `resources/implementation-playbook.md` without a corresponding bundle file is a minor concern.

Suggestions

Remove the generic boilerplate sections ('Use this skill when', 'Do not use this skill when', 'Limitations') which add ~20 lines of filler content that doesn't help Claude execute the task.

Move edge cases and the 'Undo the Revert' section into a separate reference file (e.g., EDGE-CASES.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 boilerplate sections (e.g., 'Use this skill when' / 'Do not use this skill when' are generic filler, and the Limitations section is boilerplate). The ASCII art banners and verbose display templates add bulk, though they serve a purpose as output format specifications. Some sections like 'Undo the Revert' could be tighter.	2 / 3
Actionability	The skill provides fully executable git commands, specific bash examples for commit discovery, concrete argument format patterns with examples, and detailed step-by-step procedures. The commit discovery section has copy-paste ready commands, and the execution flow is specific and concrete.	3 / 3
Workflow Clarity	Excellent multi-step workflow with clear sequencing: pre-flight checks → target selection → commit discovery → execution plan display → confirmation → execution → plan updates → verification. Includes explicit validation checkpoints (pre-flight git status checks, mandatory 'YES' confirmation, halt on merge conflict, post-revert verification), feedback loops for error recovery (merge conflict handling, edge cases), and safety rules that prevent destructive operations.	3 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed examples but no bundle files are provided to verify this exists. The content is largely monolithic — all edge cases, undo instructions, and detailed output templates are inline rather than split into separate reference files. For a skill of this length (~250+ lines), more content could be offloaded to supporting files.	2 / 3
	Total	10 / 12 Passed

Description

32%

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 a 'Use when...' clause, making it difficult for Claude to know when to select this skill. While it hints at a specific niche (undoing git changes by logical groupings), it doesn't enumerate concrete actions or include natural trigger terms users would say. The domain-specific terminology ('track', 'phase', 'task') may not match how users phrase their requests.

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 a logical work unit such as a track, phase, or task.'

List specific concrete actions the skill performs, e.g., 'Reverts commits, resets staged changes, and restores files associated with a logical work unit (track, phase, or task).'

Include natural user-facing trigger terms like 'revert', 'rollback', 'reset', 'undo changes', 'go back' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (git-aware undo) and mentions the concept of logical work units with examples (track, phase, or task), but doesn't list concrete actions like 'revert commits', 'reset staged changes', or 'restore files'.	2 / 3
Completeness	It partially addresses '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 'undo' and 'git' which are natural terms, but 'track', 'phase', and 'task' are domain-specific jargon that users may not naturally use. Missing common variations like 'revert', 'rollback', 'reset', or 'unstage'.	2 / 3
Distinctiveness Conflict Risk	The concept of 'undo by logical work unit' is somewhat distinctive, but 'git-aware undo' could overlap with general git skills. The terms 'track', 'phase', 'task' add some specificity but are ambiguous without more context.	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: sickn33/antigravity-awesome-skills
Commit: 6042393

Reviewed: about 3 hours 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.