conductor-revert
tessl i github:sickn33/antigravity-awesome-skills --skill conductor-revertGit-aware undo by logical work unit (track, phase, or task)
Review Score
66%
Validation Score
13/16
Implementation Score
77%
Activation Score
33%
Generated
Validation
Total
13/16Score
Passed| Criteria | Score |
|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') |
metadata_version | 'metadata.version' is missing |
license_field | 'license' field is missing |
Implementation
Suggestions 2
Score
77%Overall Assessment
This is a well-crafted skill with excellent actionability and workflow clarity, featuring concrete git commands, explicit safety rules, and proper validation checkpoints throughout the revert process. The main weaknesses are moderate verbosity in formatting/warnings and a monolithic structure that could benefit from splitting detailed sections into referenced files.
Suggestions
- Consider moving edge cases and the 'Undo the Revert' section to a separate reference file to reduce the main skill length
- Trim the ASCII box formatting and consolidate repeated warning patterns to improve token efficiency
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill is reasonably efficient but includes some verbose sections like the extensive ASCII box formatting and repeated warning blocks. Some explanatory text could be trimmed while preserving clarity. |
Actionability | 3/3 | Provides fully executable git commands, specific bash examples, and copy-paste ready code blocks. The argument formats, git log commands, and revert execution steps are concrete and immediately usable. |
Workflow Clarity | 3/3 | Excellent multi-step workflow with explicit validation checkpoints: pre-flight checks verify git state, execution plan requires explicit 'YES' confirmation, merge conflict handling halts immediately, and verification steps are clearly defined with numbered sequences. |
Progressive Disclosure | 2/3 | Content is well-structured with clear sections, but the skill is quite long and could benefit from splitting detailed edge cases or the execution plan display into separate reference files. The single reference to 'resources/implementation-playbook.md' is mentioned but not well-integrated. |
Activation
Suggestions 3
Score
33%Overall Assessment
The description identifies a specific niche (Git undo by work units) but suffers from missing explicit trigger guidance and relies on project-specific terminology that users may not naturally use. It needs a 'Use when...' clause and more natural trigger terms to help Claude reliably select this skill.
Suggestions
- Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to undo git changes by track, phase, or task, or mentions reverting work units'
- Include more natural trigger terms users might say, such as 'undo commits', 'revert changes', 'rollback work', 'undo last task'
- List specific concrete actions like 'reverts commits grouped by task', 'resets branches to phase boundaries', 'restores files by track'
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (Git) and a general action (undo by logical work unit), and mentions specific unit types (track, phase, task), but doesn't list concrete actions like 'revert commits', 'reset branches', or 'restore files'. |
Completeness | 1/3 | Describes what it does (Git-aware undo) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. |
Trigger Term Quality | 2/3 | Includes 'Git' and 'undo' which are natural terms, but 'logical work unit', 'track', 'phase', and 'task' are project-specific jargon that users may not naturally say when needing this skill. |
Distinctiveness Conflict Risk | 2/3 | The 'logical work unit' framing and specific terms (track, phase, task) provide some distinction from generic git skills, but could still overlap with other git undo or version control skills. |