conductor-revert
Git-aware undo by logical work unit (track, phase, or task)
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill conductor-revert66
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 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 | Reasoning | Score |
|---|---|---|
Specificity | 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'. | 2 / 3 |
Completeness | 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. | 1 / 3 |
Trigger Term Quality | 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. | 2 / 3 |
Distinctiveness Conflict Risk | 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. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
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 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 | Reasoning | Score |
|---|---|---|
Conciseness | 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. | 2 / 3 |
Actionability | 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. | 3 / 3 |
Workflow Clarity | 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. | 3 / 3 |
Progressive Disclosure | 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. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- Reviewed
Table of Contents
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.