tessl i github:sickn33/antigravity-awesome-skills --skill conductor-manageManage track lifecycle: archive, restore, delete, rename, and cleanup
Validation
63%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
Implementation
50%The skill is concise but sacrifices actionability by providing only abstract guidance without concrete commands, code, or examples. It relies too heavily on an external playbook without giving Claude enough information to understand or execute track management operations. The safety considerations are mentioned but lack specific implementation details.
Suggestions
Add concrete command examples for each operation mode (archive, restore, delete, rename, cleanup) showing exact file paths and commands
Include a brief example workflow showing the actual steps for at least one common operation (e.g., archiving a track)
Add explicit validation checkpoints for destructive operations, such as 'Run X command to verify backup exists before proceeding'
Provide a quick reference of the expected conductor/ directory structure and key files that should exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations. Every section serves a clear purpose without padding or explaining concepts Claude would already understand. | 3 / 3 |
Actionability | The skill provides only vague, abstract guidance with no concrete commands, code examples, or specific steps. Instructions like 'Verify conductor/ structure' and 'Determine the operation mode' lack any executable detail. | 1 / 3 |
Workflow Clarity | Steps are listed but lack specific validation checkpoints and concrete sequences. The instruction to 'Confirm destructive actions' is mentioned but no explicit feedback loop or verification process is defined for risky operations like delete/cleanup. | 2 / 3 |
Progressive Disclosure | References to external resources exist (implementation-playbook.md), but the main content is too sparse to serve as a useful overview. The skill essentially defers all real guidance to another file without providing enough context to understand the operations. | 2 / 3 |
Total | 8 / 12 Passed |
Activation
N/ASomething went wrong
Reviewed
Table of Contents
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.