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

Content

39%

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

This skill has a well-structured workflow with clear sequencing and error handling, but is severely bloated with verbose output templates and trivial logic explanations that Claude doesn't need spelled out. The content would benefit greatly from being split across multiple files, with SKILL.md serving as a concise overview pointing to detailed templates and format specifications elsewhere.

Suggestions

Move the detailed output format templates (Full Project Status, Single Track Status, JSON Output) into separate reference files and link to them from SKILL.md to reduce the main file to under 80 lines.

Remove the Calculation Logic section entirely—Claude can count regex matches and build progress bars without pseudocode instructions for floor division and string repetition.

Remove the boilerplate 'Use this skill when / Do not use this skill when / Limitations' sections, which add no actionable information beyond what the skill title and instructions already convey.

Replace pseudocode patterns with actual tool invocations (e.g., specify using Read tool to open conductor/tracks.md) to make the data collection steps fully executable.

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 exhaustively spells out output templates that Claude could generate from a brief specification. The calculation logic for progress bars and task counting explains trivial operations Claude already knows.	1 / 3
Actionability	The skill provides concrete file paths, regex patterns for task counting, and detailed output format templates, which is useful. However, there's no executable code—the 'Calculation Logic' section uses pseudocode, and the instructions rely on Claude reading markdown files without specifying exact tool calls or commands to use.	2 / 3
Workflow Clarity	The workflow is clearly sequenced: pre-flight checks → data collection (4 numbered steps) → output formatting, with error states well-defined. The pre-flight checks serve as validation checkpoints, and error states provide clear recovery paths (e.g., suggesting /conductor:setup if not initialized).	3 / 3
Progressive Disclosure	The entire skill is a monolithic wall of text with no references to supporting files despite mentioning `resources/implementation-playbook.md`. The detailed output templates (full project status, single track status, JSON output, quick mode) could easily be split into separate reference files. No bundle files are provided to support the content.	1 / 3
	Total	7 / 12 Passed

Description

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, making it incomplete for skill selection. The terms used are somewhat specific to a project tracking domain but could benefit from more concrete actions and explicit trigger guidance.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Use when the user asks about project status, progress updates, current tasks, or what to work on next'.

Expand the description with more concrete actions, e.g., 'Displays project status dashboards, lists active work tracks with progress, and surfaces prioritized next actions from the project plan'.

Include natural keyword variations users might say, such as 'progress', 'dashboard', 'what's next', 'task overview', or 'project summary'.

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', 'task list', 'what's next', 'todo', or 'overview'.	2 / 3
Distinctiveness Conflict Risk	'Project status' and 'active tracks' provide some specificity to a project management domain, but 'next actions' is generic enough to overlap with task management, GTD, or general planning skills.	2 / 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: 6042393

Reviewed: about 6 hours 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.