conductor-revert

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

1.60x

Quality

65%

Does it follow best practices?

Impact

96%

1.60x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/conductor-revert/SKILL.md

The canonical home for this skill is conductor-revert in sickn33/agentic-awesome-skills

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a well-sequenced, validation-rich destructive-operation workflow and concrete git commands throughout. Its main weaknesses are padding (generic boilerplate and verbose ASCII banners) and a broken, buried external reference with no actual bundle files.

Suggestions

Remove the generic 'Instructions' boilerplate ('Clarify goals...', 'Apply relevant best practices...') or replace it with skill-specific guidance.

Fix or remove the dangling `resources/implementation-playbook.md` reference, and move the large display templates into a bundled reference file so SKILL.md stays a lean overview.

Trim the decorative ASCII banners in the execution/verification blocks to reduce token cost without losing the structured output.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete git commands and assumes git knowledge, but the generic 'Instructions' section ('Clarify goals...', 'Apply relevant best practices...') and numerous large decorative ASCII banners could be trimmed, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready executable git commands (e.g. `git log --oneline --grep="{trackId}" --grep="Task {X.Y}" --all-match`, `git revert --no-edit abc1234`) with worked examples for every common case (task, phase, full track), matching 'fully executable; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The destructive revert workflow is clearly sequenced (pre-flight → selection → discovery → plan → execute → plan.md update → verify) with explicit validation checkpoints (explicit 'YES' confirmation, halt-on-conflict feedback loop, verification step) and a safety-rules checklist, matching the top anchor.	5 / 5
Progressive Disclosure	Section structure is reasonable, but the only external reference (`resources/implementation-playbook.md`) is buried in the Instructions section and the file does not exist, and large output-template blocks are inlined rather than split out, fitting 'some structure; references present but not clearly signaled'.	3 / 5
	Total	16 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 concise and names a concrete, fairly distinct capability, but it omits any explicit 'when to use' trigger guidance and lacks synonyms like 'revert'/'rollback' that users would naturally say. Adding a 'Use when...' clause would raise both completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user wants to undo, revert, or roll back a Conductor track, phase, or task.'

Add natural synonyms ('revert', 'roll back') so the description matches phrasings users actually say.

Mention the Conductor/git context explicitly to sharpen distinctiveness from generic git-revert skills.

Dimension	Reasoning	Score
Specificity	The description names a concrete action ("undo") and three concrete granularity units ("track, phase, or task") but covers only a single action rather than several, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It gives a clear 'what' (git-aware undo by work unit) but no 'Use when...' clause or equivalent trigger guidance, so per the guideline completeness is capped at 3 with 'when' only weakly implied.	3 / 5
Trigger Term Quality	It includes relevant terms ("Git-aware undo", "track, phase, or task") but misses common synonyms a user might say such as 'revert' or 'rollback', fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The Conductor-specific scope (tracks/phases/tasks) gives it a clear niche with minimal overlap, though 'git-aware undo' could brush against a generic git-revert skill, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/conductor-revert/SKILL.md
Commit: 57c135b

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.