conductor-status
Display project status, active tracks, and next actions
63
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/conductor-status/SKILL.mdQuality
Discovery
32%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 provides a basic sense of what the skill does—displaying project-related information—but lacks specificity about the concrete actions performed and entirely omits trigger guidance for when Claude should select it. The domain-specific terms 'active tracks' and 'next actions' are unexplained, and common user phrasings are not covered.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'show project status', 'what's next', 'progress update', 'task overview', or 'active tasks'.
Clarify domain-specific terms: explain what 'active tracks' and 'next actions' mean concretely (e.g., 'Display project status dashboard including active work streams, pending tasks, and prioritized next steps').
Include common user phrasing variations such as 'progress', 'dashboard', 'todo list', 'what should I work on next' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names some actions ('display project status', 'active tracks', 'next actions') but these are somewhat vague—'active tracks' and 'next actions' are domain-specific terms without further elaboration of what concrete operations are performed. | 2 / 3 |
Completeness | Describes what the skill does (display status/tracks/actions) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'project status' and 'next actions' that users might say, but misses common variations like 'progress', 'dashboard', 'todo', 'task list', 'what's next', or 'overview'. | 2 / 3 |
Distinctiveness Conflict Risk | Terms like 'project status' and 'active tracks' provide some specificity to a project management domain, but could overlap with general project management, task tracking, or dashboard skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%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 with clear workflows and comprehensive error handling. Its main weakness is verbosity — the extensive inline output templates and some boilerplate sections ('Use this skill when', generic 'Instructions', generic 'Limitations') inflate the token cost. The output format examples are valuable but could be referenced from a separate file to keep the main skill lean.
Suggestions
Remove the generic 'Instructions' bullet points (clarify goals, apply best practices, etc.) — they add no skill-specific value and waste tokens.
Move the detailed output format templates (full status, single track status, error states) to a referenced file like 'resources/status-templates.md' to reduce the main skill's token footprint.
Remove or condense the 'Use this skill when / Do not use this skill when' and 'Limitations' sections — these are generic boilerplate that Claude doesn't need.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~200+ lines) with some unnecessary sections like 'Use this skill when / Do not use this skill when' and generic limitations that don't add value. The output format templates are detailed and useful but could be more compact. The 'Instructions' section is vague boilerplate that wastes tokens. | 2 / 3 |
Actionability | The skill provides highly concrete, specific guidance: exact file paths to read, regex patterns for task counting, specific markdown parsing rules, complete output templates with examples, and pseudocode for progress bar calculation. Claude can execute this without ambiguity. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: pre-flight checks → data collection (4 numbered steps) → output formatting. Error states are explicitly handled with specific output templates. The pre-flight checks serve as validation gates before proceeding. | 3 / 3 |
Progressive Disclosure | The content is largely monolithic — all output format templates, error states, calculation logic, quick mode, and JSON output are inline in a single file. The reference to 'resources/implementation-playbook.md' is mentioned but the bulk of content that could be split (e.g., output templates, calculation logic) remains inline, making the file very long. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
- sickn33/antigravity-awesome-skills
- Commit
93c57b2
- Reviewed
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.