conductor-revert

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

1.60x

Quality

55%

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-claude/skills/conductor-revert/SKILL.md

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

Quality

Content

77%Scale 1-3

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-structured, highly actionable skill for git-aware revert operations with excellent workflow clarity and safety guardrails. The main weaknesses are moderate verbosity (especially in display templates) and a monolithic structure that could benefit from splitting detailed sections into referenced files. The safety rules and explicit confirmation requirements demonstrate good practice for destructive operations.

Suggestions

Consider moving the detailed ASCII-art display templates and edge cases to a separate reference file to reduce the main skill's token footprint

Trim explanatory text in sections like 'Use this skill when' and 'Do not use this skill when' which add little value for Claude

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some verbose sections like the extensive ASCII-art banners 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 commit discovery commands, revert execution steps, and verification procedures are all concrete and actionable.	3 / 3
Workflow Clarity	Excellent multi-step workflow with explicit validation checkpoints: pre-flight checks, confirmation gates requiring 'YES', halt-on-conflict behavior, and post-revert verification steps. Clear feedback loops for error recovery are present throughout.	3 / 3
Progressive Disclosure	Content is well-organized 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

Description

32%Scale 1-3

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 Git-related capability around undoing work by logical units, but lacks concrete action verbs and explicit trigger guidance. The terminology (track, phase, task) appears domain-specific without explanation, making it unclear when this skill should be selected over other Git-related skills.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to undo changes by track, phase, or task, or mentions reverting logical work units in Git'

List specific concrete actions such as 'reverts commits grouped by task ID', 'resets changes within a phase', or 'undoes all work in a track'

Briefly clarify what track/phase/task mean or add natural language alternatives users might say like 'undo feature work', 'revert task changes'

Dimension	Reasoning	Score
Specificity	Names the domain (Git) and a general action (undo by logical work unit), but doesn't list specific concrete actions like 'revert commits', 'reset branches', or 'restore files'.	2 / 3
Completeness	Describes what it does at a high level 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 'track', 'phase', and 'task' are project-specific jargon that users may not naturally use when seeking undo functionality.	2 / 3
Distinctiveness Conflict Risk	The 'logical work unit' concept with track/phase/task terminology provides some distinction, but 'Git undo' could overlap with general Git skills or version control tools.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-revert/SKILL.md
Commit: 7520423

Reviewed: ~16 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.