conductor-status

Display project status, active tracks, and next actions

Quality

36%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/conductor-status/SKILL.md

Quality

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 a 'Use when...' clause, which is critical for Claude to know when to select it. The trigger terms are moderately relevant but miss common user phrasings, and the terminology ('active tracks') may be too niche without additional context.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about project status, progress, what to work on next, or wants an overview of active work.'

Include more natural trigger terms users would say, such as 'progress', 'what's next', 'todo', 'task overview', 'dashboard', or 'summary'.

Clarify what 'active tracks' means or replace with more universally understood terminology to reduce ambiguity and improve distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names a domain (project management) and lists some actions ('display project status, active tracks, and next actions'), but these are somewhat vague—'active tracks' and 'next actions' are not universally understood terms and the scope of what 'display' entails is unclear.	2 / 3
Completeness	The description answers 'what' (display project status, tracks, actions) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak enough to warrant a 1.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'project status' and 'next actions' that users might say, but misses common variations like 'progress', 'task list', 'todo', 'what's next', 'dashboard', or 'overview'. 'Active tracks' is somewhat niche terminology.	2 / 3
Distinctiveness Conflict Risk	The combination of 'project status', 'active tracks', and 'next actions' provides some specificity, but 'project status' is generic enough to overlap with other project management or reporting skills. The lack of explicit context about what kind of project or system makes it somewhat ambiguous.	2 / 3
	Total	7 / 12 Passed

Implementation

39%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides a thorough specification for displaying project status with good workflow sequencing and error handling. However, it is excessively verbose—the output format templates alone consume the majority of the document and could be referenced externally. The generic boilerplate sections and explanation of trivial logic (regex counting, progress bar math) waste tokens on things Claude already knows.

Suggestions

Move the large output format templates (full status, single track status, error states, JSON output) into separate reference files and link to them from the main SKILL.md to dramatically reduce token usage.

Remove the generic boilerplate sections ('Use this skill when', 'Do not use this skill when', 'Limitations') and the vague instructions ('Clarify goals, constraints', 'Apply relevant best practices') that add no actionable value.

Remove the Calculation Logic section—Claude doesn't need to be taught how to count regex matches, compute floor division, or repeat characters.

If referencing 'resources/implementation-playbook.md', ensure it exists in the bundle or remove the reference.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~200+ lines. It includes boilerplate sections ('Use this skill when', 'Do not use this skill when', 'Limitations') that add no value, and the massive ASCII-art output templates could be much more concisely specified. The calculation logic section explains trivially simple concepts (counting regex matches, floor division) that Claude already knows.	1 / 3
Actionability	The skill provides concrete file paths, regex patterns for task counting, and detailed output format templates, which is helpful. However, the actual instructions are still somewhat vague ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') and there's no executable code—just pseudocode for counting and progress bars. The regex patterns are given but not in a fully executable context.	2 / 3
Workflow Clarity	The workflow is clearly sequenced: pre-flight checks → data collection (4 numbered stages) → output formatting, with explicit error states for each failure mode (no tracks, not initialized, track not found). The pre-flight checks serve as validation checkpoints before proceeding.	3 / 3
Progressive Disclosure	This is a monolithic wall of text with everything inline. The massive output format templates (full project status, single track status, error states, JSON output, quick mode) should be in separate reference files. There's a reference to 'resources/implementation-playbook.md' but no bundle files exist to support it, and the bulk of content that could be externalized remains inline.	1 / 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: sickn33/antigravity-awesome-skills
Commit: f5dc9e3

Reviewed: 3 days 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.