conductor-revert

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./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.

The body is highly actionable and well-sequenced with strong validation and safety checkpoints, but it is padded with decorative templates and generic boilerplate, and it remains a monolithic single file with no progressive disclosure.

Suggestions

Trim the decorative ASCII borders and remove the generic 'Use this skill when' / 'Instructions' boilerplate that restates what Claude already knows.

Compress the large display templates (execution plan, verification) to essentials, or extract them into a referenced file to reduce token load.

Split commit-discovery details or edge-case menus into a one-level-deep reference file so the main SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and useful, but decorative ASCII borders ('====...====') and generic boilerplate ('Working on revert track tasks or workflows', 'Clarify goals, constraints, and required inputs') add tokens that restate what Claude already knows.	2 / 3
Actionability	It provides fully executable, copy-paste-ready commands like 'git revert --no-edit abc1234' and 'git log --oneline --grep="{trackId}"' with concrete SHA examples, matching the score-3 anchor.	3 / 3
Workflow Clarity	A clear sequence (pre-flight -> discovery -> plan -> execute -> verify) is paired with explicit validation checkpoints, a required 'YES' confirmation, HALT-on-conflict feedback, and a Safety Rules checklist for a destructive batch operation.	3 / 3
Progressive Disclosure	It is a single ~370-line file with no bundle references; clear section headers provide structure, but nothing is split out into referenced files, so it stays monolithic rather than progressively disclosed.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 specific and distinct, naming a clear Conductor-scoped undo operation, but it omits any 'Use when...' trigger guidance and relies on a single action verb while missing common terms like 'revert'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to undo or revert Conductor tracks, phases, or tasks.'

Include the natural term 'revert' alongside 'undo' and add variations like 'rollback' to broaden trigger coverage.

Name concrete actions such as reverting commits and resetting plan.md task status to raise specificity toward multiple distinct actions.

Dimension	Reasoning	Score
Specificity	It names the action ('undo') and scopes ('track, phase, or task'), but lists a single action rather than multiple distinct concrete actions, matching the 'names domain and some actions' anchor rather than the score-3 'lists multiple specific concrete actions'.	2 / 3
Completeness	It clearly states what it does ('Git-aware undo by logical work unit (track, phase, or task)') but includes no 'Use when...' trigger clause, so the 'when' is missing and completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	'undo' and 'track, phase, task' are relevant natural terms, but the common term 'revert' (used throughout the body) and variations like 'rollback' are absent, leaving only partial keyword coverage.	2 / 3
Distinctiveness Conflict Risk	The Conductor-specific scope 'logical work unit (track, phase, or task)' gives it a clear niche that is unlikely to trigger for generic git skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/conductor-revert/SKILL.md
Commit: e63f7dd

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