conductor-status

Display project status, active tracks, and next actions

1.76x

Quality

61%

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/skills/conductor-status/SKILL.md

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

Quality

Content

73%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 exceptionally actionable and well-sequenced with strong validation checkpoints, but it is a single monolithic file whose one cross-reference is a dangling path, hurting progressive disclosure.

Suggestions

Either create resources/implementation-playbook.md or remove the reference to it so navigation is not broken.

Move the two large output templates (full project status, single-track status) into a separate reference file and link to them from the body to reduce inline token weight.

Consolidate the Quick Mode, JSON Output, and Status Markers Legend into one 'Output variants' section to tighten the document.

Dimension	Reasoning	Score
Conciseness	The body is concrete and avoids over-explaining concepts, but ~330 lines dominated by two large ASCII output templates plus separate Quick Mode and JSON Output blocks could be tightened or factored out.	3 / 5
Actionability	Concrete file paths, exact counting regexes, an explicit progress-bar formula, and full output templates with named fields make the guidance copy-paste ready and cover the common single-track and full-status cases.	5 / 5
Workflow Clarity	Pre-flight Checks gate the flow with explicit validation (init check, tracks check, error states) and Data Collection is a clearly sequenced 1-4 process with phase-detection and blocker-detection checkpoints.	5 / 5
Progressive Disclosure	All content lives in one inlined file with large templates that belong in separate references, and the only external reference ('resources/implementation-playbook.md') points at a file that does not exist.	2 / 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 clearly states what the skill does but omits any explicit trigger guidance, and its action terms are broad nouns rather than crisp verbs. It is serviceable but undifferentiated from generic status-reporting skills.

Suggestions

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

Tighten the verb choices toward distinct actions (e.g. 'Render a project status dashboard showing track progress and next actions') instead of the single generic verb 'Display'.

Include natural synonyms users say aloud (progress, dashboard, blockers) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names three concrete display outputs ('project status, active tracks, and next actions') but the only verb is 'Display' and the outputs are passive nouns, so it stops at domain-plus-1-2-actions rather than comprehensive.	3 / 5
Completeness	The 'what' is clear (display project status/tracks/next actions) but there is no 'when' / 'Use when...' clause, which the guidelines cap at 3.	3 / 5
Trigger Term Quality	'project status', 'active tracks', and 'next actions' are relevant natural phrases, but there are no synonyms or common variations (e.g. 'progress', 'where am I'), leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	'active tracks' ties it to the Conductor domain, but 'project status' alone is generic enough to overlap with other status/progress 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/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.