conductor-status

Display project status, active tracks, and next actions

Quality

60%

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

70%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 operational core is excellent — precise data-collection steps, parsing rules, formulas, output templates, and error handling make it fully executable with a well-validated workflow. However, the skill is padded with generic boilerplate sections, and its single external reference is both buried and broken (no resources/ directory exists in the bundle). Trimming the boilerplate and fixing or removing the dead reference would move it toward top marks.

Suggestions

Delete the boilerplate sections ('Use this skill when', 'Do not use this skill when', the generic 'Instructions' bullets, and 'Limitations') — they restate scope already covered by the frontmatter and add no skill-specific value.

Fix the broken reference: either add resources/implementation-playbook.md to the bundle or remove the pointer, since the file does not exist.

Consider moving the two large ASCII output templates to a single reference file (e.g. references/output-templates.md) with a clearly signaled link, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	Several sections are pure padding that assume Claude lacks competence it has: "Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes", the circular "Use this skill when... Working on conductor status tasks", and a generic Limitations section — matching anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections') rather than anchor 3's 'some' unnecessary explanation.	2 / 5
Actionability	Guidance is fully executable for an instruction-only skill: exact file paths to read, concrete parsing regexes (/^- \[x\] Task/), explicit calculation formulas ("filled = floor((completed / total) * 20)"), complete output templates, error-state outputs, and a JSON schema — copy-paste ready with common cases covered.	5 / 5
Workflow Clarity	The sequence is explicit with validation checkpoints and error recovery: numbered pre-flight checks (verify product.md/tracks.md exist) with fallback actions, sequenced data collection (project info → tracks → per-track analysis → blocker detection), and dedicated error states for each failure mode (not initialized → 'Run /conductor:setup', track not found → list available tracks). This is a read-only display skill, so no destructive-operation cap applies.	5 / 5
Progressive Disclosure	Section structure is clear with headers, but the only external reference — "open `resources/implementation-playbook.md`" — is buried mid-section, unsignaled, and points to a file that does not exist in the bundle, while large output templates are fully inlined; this fits anchor 3 ('some structure... references present but not clearly signaled') rather than anchor 4's 'references mostly clear'.	3 / 5
	Total	15 / 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 states a clear but shallow 'what' with three high-level actions, and entirely omits any 'when to use' trigger guidance. It also never mentions Conductor, the tool ecosystem it belongs to, weakening both trigger quality and distinctiveness. A trigger clause and domain grounding would lift most dimensions by a full point.

Suggestions

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

Ground the description in its domain by naming Conductor and clarifying what a 'track' is (e.g. 'Display Conductor project status: overall progress, active tracks, current task, and next actions').

Include natural trigger phrases and synonyms users would say — 'progress', 'overview', 'current task', 'roadmap' — to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists three actions ("Display project status, active tracks, and next actions") but they are high-level and ungrounded — it never names the Conductor domain or what a 'track' is, matching anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') rather than anchor 4's several specific actions.	3 / 5
Completeness	The 'what' is stated (display status, tracks, next actions) but there is no 'Use when...' clause or any trigger guidance, which caps completeness at 3 per the rubric guideline; not score 2 because the 'what' is clear rather than vague.	3 / 5
Trigger Term Quality	Phrases like "project status" and "next actions" are relevant keywords, but common variations users would naturally say — "progress", "overview", "what am I working on", or even the word "Conductor" — are absent, matching anchor 3 ('some relevant keywords but missing common variations or synonyms').	3 / 5
Distinctiveness Conflict Risk	"Display project status" without the Conductor naming could overlap with generic status/progress skills (git status, CI health, project overviews), though "active tracks" and "next actions" add some distinctiveness — anchor 3 ('somewhat specific but could still overlap with similar skills').	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/agentic-awesome-skills
Path: skills/conductor-status/SKILL.md
Commit: 7b534bc

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