conductor-manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup
74
62%
Does it follow best practices?
Impact
96%
2.23xAverage score across 3 eval scenarios
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-manage/SKILL.mdThe canonical home for this skill is conductor-manage in rmyndharis/antigravity-skills
Evaluation results
100%
56%Archive Completed Feature Track
Archive mode workflow
_archive dir created
100%
100%
metadata archived=true
0%
100%
metadata archived_at
0%
100%
metadata archive_reason
0%
100%
metadata status=archived
100%
100%
tracks.md completed removed
100%
100%
tracks.md archived entry
100%
100%
Archived entry Reason field
0%
100%
Archived entry date field
100%
100%
git commit message format
20%
100%
YES confirmation used
0%
100%
Archive reason selection
0%
100%
90%
40%Fix Track Naming to Match Conventions
Rename with ID validation
ID format validated
33%
100%
metadata id updated
100%
100%
metadata previous_ids
0%
100%
metadata renamed_at
0%
100%
plan.md header updated
100%
100%
tracks.md entry updated
100%
100%
tracks.md folder link updated
50%
0%
git commit message format
16%
100%
YES confirmation used
12%
100%
Conflict check
100%
100%
100%
65%Remove Abandoned Experimental Track
Delete mode safeguards
DELETE string required
0%
100%
PERMANENT DELETION WARNING
0%
100%
Archive alternative offered
40%
100%
In-progress WARNING shown
60%
100%
rm -rf used
100%
100%
tracks.md entry removed
100%
100%
git commit message format
0%
100%
Git history preserved note
0%
100%
Both locations checked
0%
100%
- Commit
57c135b
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.