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 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 error handling. The main weaknesses are moderate verbosity (boilerplate sections, verbose ASCII display templates) and a monolithic structure that could benefit from splitting edge cases and display templates into separate reference files.

Suggestions

Remove the generic boilerplate sections ('Use this skill when', 'Do not use this skill when', 'Limitations') which add ~20 lines of low-value content that Claude doesn't need.

Consider moving edge cases and display template examples into a separate reference file (e.g., `resources/edge-cases.md`) to reduce the main skill's length 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 for user-facing output. Some sections like 'Undo the Revert' could be tighter.	2 / 3
Actionability	The skill provides fully executable git commands, specific argument formats with examples, concrete bash commands for commit discovery, and detailed step-by-step procedures. The target selection parsing, commit discovery commands, and revert execution steps are all copy-paste ready and specific.	3 / 3
Workflow Clarity	The workflow is exceptionally well-sequenced: pre-flight checks → target selection → commit discovery → execution plan display → explicit confirmation → revert execution → plan updates → verification. It includes explicit validation checkpoints, merge conflict handling with halt behavior, and clear feedback loops for error recovery. Safety rules are prominently stated.	3 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed examples but no bundle files are provided to verify this. The content is largely monolithic — all edge cases, undo instructions, and detailed display templates are inline rather than split into referenced files. For a skill of this length (~250 lines), some 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 incomplete for skill selection. While it hints at a specific niche (undoing git changes by logical groupings), it doesn't explain concrete actions or provide natural trigger terms users would say. The domain-specific terms 'track', 'phase', and 'task' are unexplained and may not match user vocabulary.

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, e.g., 'Reverts commits, resets staged changes, and restores files associated with a specific track, phase, or task.'

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

Dimension	Reasoning	Score
Specificity	It names the domain (git undo) and mentions the concept of 'logical work unit' with examples (track, phase, 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 has no 'when' clause or explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' itself is vague enough to warrant a 1.	1 / 3
Trigger Term Quality	Includes 'git' and 'undo' 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', 'unstage'.	2 / 3
Distinctiveness Conflict Risk	The 'logical work unit (track, phase, or task)' qualifier provides some distinctiveness from generic git skills, but 'git undo' is broad enough to 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: sickn33/antigravity-awesome-skills
Commit: 88d1e11

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.