conductor-status

Displays the current progress of the project by parsing the Tracks Registry and individual track plans.

Quality

64%

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

75%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 content is a well-structured, actionable instruction-only skill with clear sequencing and validation checkpoints. Its main weaknesses are minor verbosity in the operational-standards boilerplate and a few under-specified output details.

Suggestions

Specify the concrete output format for the status report (e.g., a markdown template) so the 'Present Status Overview' step is copy-paste ready.

Clarify how to obtain the 'current timestamp' (terminal command) and how to compute the progress percentage from checkbox markers.

Tighten the 'Operational Standards' section by moving shared interaction/protocol rules into a referenced file or trimming boilerplate that restates general agent behavior.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with numbered steps and no over-explanation of concepts Claude already knows, but the 'Operational Standards' block contains some generic boilerplate that could be trimmed, fitting the 'efficient; minor instances' anchor rather than fully lean.	4 / 5
Actionability	It gives concrete, executable guidance with specific paths ('conductor/index.md', 'conductor/tracks/<track_id>/plan.md') and exact parsing patterns ('- [ ] **Track:', '## [ ] Track:'), with only minor gaps in output formatting; as an instruction-only skill the absence of code is not penalized.	4 / 5
Workflow Clarity	The workflow is clearly sequenced (Handshake, Read, Parse, Present) with validation checkpoints ('verify every linked file actually exists', 'HALT immediately'), but it has minor gaps such as the unspecified source of the 'current timestamp' and no explicit parse-failure recovery loop.	4 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and is well-organized into numbered sections, but the inlined 'Operational Standards' material is somewhat separable and the body slightly exceeds the simple-skill line, leaving minor organization gaps short of a 5.	4 / 5
	Total	16 / 20 Passed

Description

53%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 clearly states what the skill does but omits any 'when to use' trigger guidance, which limits its discoverability and completeness scores. It is reasonably specific to the Conductor project-management niche.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks for a project status report, progress overview, or what to work on next.'

Broaden trigger terms with natural synonyms such as 'status report', 'project status', 'progress overview', and 'track plan'.

Optionally enumerate the concrete actions (read the Tracks Registry, parse track plans, summarize phase/task progress) to lift specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain ('current progress of the project', 'Tracks Registry') and two concrete actions ('parsing the Tracks Registry' and 'individual track plans'), matching the '1-2 concrete actions' anchor; it does not list several actions, so it stays below 4.	3 / 5
Completeness	It gives a clear 'what' (display progress by parsing registry and track plans) but has no 'Use when...' trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It includes some natural terms ('current progress', 'project') but lacks common variations or synonyms a user would say ('status report', 'where are we', 'project status'), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Tracks Registry' and 'track plans' niche is mostly distinct with only minor overlap risk against generic project-status tools, fitting the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: gemini-cli-extensions/conductor
Path: skills/conductor-status/SKILL.md
Commit: f06add3

Reviewed: 12 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.