conductor-status

Display project status, active tracks, and next actions

Quality

56%

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

63%Weight 40%Scale 1-5

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

The body is a concrete, well-sequenced status-display skill with specific parsing rules and output templates, but it carries generic boilerplate framing and a broken reference to a missing bundle file. Tightening the filler sections and either creating or removing the referenced playbook would lift conciseness and progressive disclosure.

Suggestions

Remove or replace the generic "Use this skill when", "Do not use this skill when", "Instructions", and "Limitations" boilerplate with skill-specific guidance, or delete them entirely.

Resolve the dangling reference at line 28: either add resources/implementation-playbook.md to the bundle or remove the pointer.

Consider moving the large ASCII output-format templates and Calculation Logic into a reference file to reduce inline weight and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The core (Data Collection, Output Format, Calculation Logic, Error States) is dense and earns its tokens, but the generic framing sections ("Use this skill when", "Do not use this skill when", "Instructions", "Limitations") are boilerplate Claude already knows and could be trimmed.	3 / 5
Actionability	Guidance is highly concrete — exact file paths (conductor/tracks/{trackId}/plan.md), task-counting regex (/^- \[x\] Task/), a progress-bar formula, and full output/JSON templates — with only minor gaps around edge cases and placeholder fill-in keeping it just below a 5.	4 / 5
Workflow Clarity	A clear sequence runs from Pre-flight Checks (with init/track validation and error branches) through Data Collection to Output and Error States, but mid-process validation checkpoints are implicit rather than explicit, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	Sections are well-organized, but all content is inlined in one 345-line file and the single reference to resources/implementation-playbook.md (line 28) points to a file that does not exist in the bundle, making it a dangling reference rather than a clean one-level-deep pointer.	3 / 5
	Total	14 / 20 Passed

Description

50%Weight 40%Scale 1-5

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 third-person and states a clear capability, but it lacks any "Use when" trigger guidance and relies on one generic verb, leaving it at the midpoint across all dimensions. Adding explicit trigger phrases and naming the Conductor context would raise specificity, completeness, and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases (e.g., 'Use when the user asks for Conductor project status, track progress, or next actions').

Name the Conductor domain in the description to reduce overlap with generic project-status skills.

Vary the verbs beyond 'Display' (e.g., 'Summarize project progress, list active tracks, and recommend next actions') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Display project status, active tracks, and next actions" names the domain and three display targets, but every action shares the single generic verb "Display" rather than listing distinct concrete actions, so it is not comprehensive enough for a 4.	3 / 5
Completeness	The description gives a clear "what" (display project status, active tracks, next actions) but omits any "when"/"Use when" trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Terms like "project status", "active tracks", and "next actions" are somewhat natural, but coverage is narrow with no synonyms, file extensions, or an integrating "Use when" phrase, falling short of good keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The phrase is somewhat specific to project-status reporting, but without naming the Conductor domain it could overlap with other project-tracking or status skills, matching the "somewhat specific but could still overlap" anchor.	3 / 5
	Total	12 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/conductor-status/SKILL.md
Commit: 1f67c44

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