conductor-revert
Git-aware undo by logical work unit (track, phase, or task)
63
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/conductor-revert/SKILL.mdQuality
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 is too terse and lacks both concrete action verbs and explicit trigger guidance. While it hints at a specific niche (undoing git changes by logical groupings), it fails to explain what concrete operations it performs or when Claude should select it. The domain-specific terms 'track', 'phase', and 'task' are unexplained and unlikely to match natural user language.
Suggestions
Add a 'Use when...' clause with natural trigger terms like 'undo last task', 'revert changes', 'rollback commits', 'git reset'.
List specific concrete actions such as 'reverts commits, resets staged changes, and restores files grouped by logical work units (tracks, phases, or tasks)'.
Include common user phrasings and synonyms like 'undo', 'revert', 'rollback', 'go back to previous state' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git undo) and mentions the concept of logical work units with examples (track, phase, 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. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also weak, warranting 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', or 'unstage'. | 2 / 3 |
Distinctiveness Conflict Risk | The concept of 'logical work unit (track, phase, or task)' provides some distinctiveness from generic git skills, but 'git undo' is broad enough to overlap with general git workflow 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 strong, highly actionable skill with excellent workflow clarity and safety guardrails for a destructive operation. The multi-step process is well-sequenced with explicit validation checkpoints, confirmation requirements, and error handling. The main weaknesses are moderate verbosity (generic boilerplate sections, decorative ASCII formatting) and the monolithic structure that could benefit from splitting some sections into referenced files.
Suggestions
Remove the generic 'Use this skill when' / 'Do not use this skill when' / 'Limitations' boilerplate sections, which add no domain-specific value and waste tokens.
Consider moving edge cases and the 'Undo the Revert' section 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 long (~250 lines) with some boilerplate sections ('Use this skill when'/'Do not use this skill when' are generic and add little value). The ASCII box art in execution plan displays is verbose. However, most content is genuinely instructive and specific to the domain, so it's not egregiously padded. | 2 / 3 |
Actionability | 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 plan.md update instructions, and exact conflict resolution workflows. The guidance is copy-paste ready and leaves no ambiguity about what to execute. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit validation checkpoints: pre-flight checks (git status, uncommitted changes, merge/rebase state), execution plan display requiring explicit 'YES' confirmation, step-by-step revert execution with per-commit success/failure tracking, halt-on-conflict with clear options, and post-revert verification including test commands. Feedback loops are well-defined throughout. | 3 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` for detailed examples, which is good. However, the main file itself is quite long and could benefit from splitting edge cases, undo instructions, or the detailed execution plan display into separate reference files. The content is well-structured with clear headers but is borderline monolithic. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
93c57b2
- 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.