conductor-status

Display project status, active tracks, and next actions

1.76x

Quality

64%

Does it follow best practices?

Impact

99%

1.76x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-status/SKILL.md

The canonical home for this skill is conductor-status in sickn33/agentic-awesome-skills

Quality

Content

78%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 highly actionable and well-sequenced with concrete file paths, regex, and formulas, plus solid pre-flight validation and error states. Its main weaknesses are the broken reference to a non-existent playbook file and a monolithic single-file structure that could be split.

Suggestions

Fix or remove the dangling reference to `resources/implementation-playbook.md` (the path does not exist and uses `resources/` rather than the `references/` bundle convention).

Move the large ASCII output-format templates and/or calculation logic into a reference file, keeping SKILL.md as an overview that points one level deep.

Trim the duplicated progress-bar description (it appears in both the Output Format example and the Calculation Logic section).

Dimension	Reasoning	Score
Conciseness	The body is dense but almost entirely concrete specification (file paths, regex, output templates) rather than explanations of concepts Claude already knows. Not a 5 because the two large ASCII output templates and the duplicated progress-bar logic add tokens that could be trimmed.	4 / 5
Actionability	Guidance is fully executable: specific file paths to read, exact regex patterns for task counting ('/^- \[x\] Task/'), and a concrete progress-bar formula. The instruction-only format is not penalized because the guidance is specific and actionable.	5 / 5
Workflow Clarity	A clear sequence runs from Pre-flight Checks through Data Collection to Output Format, with explicit validation (missing files -> suggest /conductor:setup) and an Error States section. Not a 5 because, while appropriate for a read-only skill, there is no validate->fix->retry feedback loop.	4 / 5
Progressive Disclosure	No bundle files exist, yet the body references `resources/implementation-playbook.md` (a non-existent path), and the large output templates and calculation logic are all inlined in one ~330-line file rather than split out. Not a 4 because the single reference is broken and significant content that could live in separate files is inline.	3 / 5
	Total	16 / 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 'what' with a few concrete display targets but omits any 'when to use it' trigger guidance, which caps completeness at 3. Trigger terms are natural but lack synonyms, and distinctiveness suffers from the missing product name.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for project status, progress, active tracks, or next actions in a Conductor project.'

Mention 'Conductor' in the description to reduce overlap with generic status/reporting skills.

Add a few natural synonyms users might say ('progress', 'what's left to do', 'show status') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('project status') and three concrete display targets ('project status, active tracks, and next actions'), but all are variations of a single display action and coverage is not comprehensive. Not a 4 because the actions are uniform variants of 'display X' rather than several distinct operations.	3 / 5
Completeness	It clearly states what the skill does ('Display project status, active tracks, and next actions') but has no 'Use when...' clause or explicit trigger guidance, which caps completeness at 3 per the rubric. Not a 2 because the 'what' is clear rather than vague.	3 / 5
Trigger Term Quality	'project status', 'active tracks', and 'next actions' are reasonably natural phrases, but common variations or synonyms a user might say (e.g. 'progress', 'show status', 'what's left') are missing. Not a 4 because keyword coverage is partial rather than good.	3 / 5
Distinctiveness Conflict Risk	The description is tied to a project-tracking domain but does not mention 'Conductor', so it could overlap with other status/reporting skills. Not a 4 because without the product name the niche is not sharply distinct.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-status/SKILL.md
Commit: 57c135b

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