conductor-status
tessl i github:sickn33/antigravity-awesome-skills --skill conductor-statusDisplay project status, active tracks, and next actions
Review Score
66%
Validation Score
13/16
Implementation Score
77%
Activation Score
33%
Generated
Validation
Total
13/16Score
Passed| Criteria | Score |
|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') |
metadata_version | 'metadata.version' is missing |
license_field | 'license' field is missing |
Implementation
Suggestions 2
Score
77%Overall Assessment
This is a well-structured, highly actionable skill for displaying project status. Its strengths are concrete file paths, explicit parsing patterns, and comprehensive error handling. The main weakness is its length - the detailed output format templates make it verbose, though much of this detail is necessary for the skill's purpose.
Suggestions
- Remove the generic 'Use this skill when' and 'Do not use this skill when' sections - they add no value for Claude
- Consider moving the detailed output format templates to a separate reference file (e.g., `status-formats.md`) and keeping only a brief example in the main skill
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill is fairly comprehensive but includes some redundancy (e.g., the 'Use this skill when' and 'Do not use this skill when' sections are generic boilerplate). The output format examples are detailed but necessarily so for a status display skill. |
Actionability | 3/3 | Provides highly concrete guidance with specific file paths, exact regex patterns for task counting, complete output format templates, and explicit calculation logic. The instructions are copy-paste ready and leave no ambiguity about implementation. |
Workflow Clarity | 3/3 | Clear sequential workflow with pre-flight checks, data collection steps, and explicit error states. The skill handles edge cases (no tracks, not initialized, track not found) with specific error messages and recovery suggestions. |
Progressive Disclosure | 2/3 | The skill is monolithic with all content inline. While it references `resources/implementation-playbook.md`, the main content could benefit from splitting detailed output formats into separate reference files. The JSON output and calculation logic sections could be externalized. |
Activation
Suggestions 3
Score
33%Overall Assessment
The description provides a basic list of capabilities but lacks the explicit 'Use when...' guidance critical for skill selection. The terminology ('active tracks') is somewhat specialized without context, and the description doesn't clearly differentiate itself from general project management or task tracking skills.
Suggestions
- Add a 'Use when...' clause with trigger terms like 'show status', 'what's next', 'project progress', 'pending tasks', or 'current work'
- Clarify what 'active tracks' means - is this a specific methodology or tool? Users won't search for this term naturally
- Expand with common user phrases: 'Use when the user asks about project progress, pending work, task priorities, or wants to see what to work on next'
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names specific actions ('display project status', 'active tracks', 'next actions') but lacks detail on what these mean or how they're performed. The terms are somewhat domain-specific without explanation. |
Completeness | 1/3 | Only describes 'what' (display status/tracks/actions) with no 'Use when...' clause or explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, but this also has a weak 'what' explanation. |
Trigger Term Quality | 2/3 | Contains some relevant keywords like 'project status' and 'next actions' that users might say, but 'active tracks' is jargon. Missing common variations like 'show progress', 'what's pending', 'todo list', or 'task overview'. |
Distinctiveness Conflict Risk | 2/3 | 'Project status' and 'next actions' could overlap with general task management, project management, or todo skills. 'Active tracks' adds some specificity but the overall scope is unclear enough to risk conflicts. |