conductor-status

Display project status, active tracks, and next actions

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/conductor-status/SKILL.md

Quality

Content

77%

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

The body is highly actionable and workflow-clear, with concrete file paths, regex logic, and full output templates plus error states. Its weaknesses are minor generic boilerplate in the Instructions section and a monolithic structure where the large output-format blocks could be factored into referenced files.

Suggestions

Remove the generic Instructions bullets ("Clarify goals…", "Apply relevant best practices…") that restate what Claude already knows.

Consider moving the long full/single-track output-format templates into a referenced file (e.g. templates/STATUS_FORMAT.md) with a concise inline summary to improve progressive disclosure.

Tighten the 'Use this skill when' / 'Do not use this skill when' sections to conductor-specific triggers rather than generic phrasing.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete output templates and calculation logic, but it includes generic boilerplate Claude already knows ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") that could be trimmed, matching the level-2 anchor.	2 / 3
Actionability	It provides fully executable guidance: exact file paths (conductor/tracks/{trackId}/plan.md), regex patterns for task counting, a progress-bar formula, and complete copy-paste-ready output templates for every mode, matching the level-3 anchor.	3 / 3
Workflow Clarity	The process is clearly sequenced (pre-flight checks → data collection → output) with explicit validation checkpoints (verify product.md/tracks.md exist) and dedicated error-state sections for recovery, matching the level-3 anchor.	3 / 3
Progressive Disclosure	The skill is a single monolithic ~330-line file with no external references; sections are well-organized but the large output-format templates could be split into referenced files, matching the level-2 anchor for content that could be separate being inline.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 is clear and in third person but stays at level 2 across all dimensions because it omits any explicit "Use when…" trigger guidance and uses a narrow set of display-only action verbs. Adding concrete trigger terms and a use-when clause would lift it to level 3.

Suggestions

Add an explicit 'Use when…' clause naming natural triggers, e.g. 'Use when the user asks for project status, progress, or what to work on next in Conductor.'

Broaden the action list beyond display verbs (e.g. 'summarizes', 'reports') and add common terms like 'progress' and 'status' to improve trigger-term coverage.

Include the Conductor domain explicitly in the description to reduce overlap with generic status/reporting skills.

Dimension	Reasoning	Score
Specificity	The description names the domain and several actions ("Display project status, active tracks, and next actions"), but the actions are all "display" variants and not comprehensive, fitting the level-2 anchor rather than level 3.	2 / 3
Completeness	It answers "what" (display project status, active tracks, next actions) but provides no "Use when…" clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes some relevant natural keywords ("project status", "active tracks", "next actions") but lacks common variations users would say such as "progress" or simply "status", matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The conductor-status niche is somewhat specific, but the description text alone ("project status, active tracks, and next actions") could overlap with other project-tracking or status skills, matching the level-2 anchor.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/conductor-status/SKILL.md
Commit: e63f7dd

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