conductor-revert

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 with concrete git commands and a well-sequenced, checkpointed workflow suited to a destructive operation. Its main weaknesses are verbose mock dialog templates and a broken reference to a non-existent playbook file.

Suggestions

Trim or factor out the large ASCII mock dialog/output templates, which consume tokens without adding proportional guidance value.

Create the referenced `resources/implementation-playbook.md` (or remove the reference) so signaled references resolve to real files.

Consider moving the detailed execution-plan and verification templates into a referenced file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The prose instructions are lean and avoid explaining known concepts, but the large verbatim ASCII dialog/output templates are token-heavy padding that could be tightened.	2 / 3
Actionability	Provides concrete, executable git commands with real flags (e.g., `git log --oneline --grep="{trackId}" --grep="Task {X.Y}" --all-match`, `git revert --no-edit <sha>`) and specific plan.md update steps that are copy-paste ready.	3 / 3
Workflow Clarity	Clear sequence (pre-flight checks -> target selection -> commit discovery -> plan display -> execution -> updates -> verification) with explicit validation checkpoints, a 'YES' confirmation gate, and halt-on-conflict feedback loops appropriate for destructive batch operations.	3 / 3
Progressive Disclosure	Has clear sections but is a single monolithic file with large inline templates that could be split out, and its one signaled reference (`resources/implementation-playbook.md`) does not exist in the bundle.	2 / 3
	Total	10 / 12 Passed

Description

60%

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 about what it does and at what granularity, but lacks an explicit use-when trigger and leans on domain jargon ("logical work unit") over natural user terms. It is distinguishable but not sharply differentiated from general git undo skills.

Suggestions

Add an explicit "Use when..." clause stating when to invoke this skill (e.g., when the user wants to undo Conductor track/phase/task work).

Include natural trigger terms users would actually say, such as "revert", "rollback", or "undo a track/phase/task".

Replace "logical work unit" jargon with plain language to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	Names the concrete action ("Git-aware undo") and enumerates specific granular work units ("track, phase, or task"), listing multiple concrete units rather than a vague domain.	3 / 3
Completeness	Clearly states what it does but provides no "Use when..." trigger guidance, so the "when" is only implied — capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	"undo" and "git" are natural user terms, but "logical work unit" is jargon and common variations like "revert" or "rollback" are missing.	2 / 3
Distinctiveness Conflict Risk	The track/phase/task scoping gives it a niche, but "git undo" could still overlap with generic git-revert skills and there is no explicit distinct trigger language.	2 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 615669b

Reviewed: 3 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.