conductor-status

Display project status, active tracks, and next actions

1.76x

Quality

55%

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

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

Quality

Content

77%Scale 1-3

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

This is a well-structured, highly actionable skill that provides Claude with everything needed to display project status, including exact file paths, parsing logic, output templates, and error handling. Its main weakness is length—the extensive inline output format templates and boilerplate sections make it less token-efficient than it could be. The output format specifications, while thorough, could be split into a referenced file to improve progressive disclosure.

Suggestions

Move the detailed output format templates (full status, single track status, error states) into a separate referenced file like 'resources/status-templates.md' to reduce the main skill's token footprint.

Remove the generic 'Use this skill when' / 'Do not use this skill when' sections—they add no value beyond what the skill title and description already convey.

Trim the initial Instructions section which contains vague generic advice ('Clarify goals, constraints, and required inputs') that doesn't apply to a status display command.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~200+ lines) with extensive output format templates that are largely illustrative. The 'Use this skill when' / 'Do not use this skill when' sections are generic boilerplate. However, the detailed output formats and calculation logic do serve as concrete specifications, so it's not purely verbose—just could be tightened significantly.	2 / 3
Actionability	The skill provides highly specific, concrete guidance: exact file paths to read, exact regex patterns for task counting, exact output formats with examples, calculation logic for progress bars, and clear error state handling. Claude would know exactly what to do at every step.	3 / 3
Workflow Clarity	The workflow is clearly sequenced: pre-flight checks → data collection (4 numbered steps) → output formatting. Pre-flight checks include validation (file existence) with error recovery paths. The multi-step data collection process is well-ordered with explicit sources for each piece of data.	3 / 3
Progressive Disclosure	The skill is monolithic—all output format templates, error states, calculation logic, quick mode, and JSON output are inline rather than split into referenced files. There's one reference to 'resources/implementation-playbook.md' but the bulk of content that could be in separate files (output templates, error templates) is embedded directly, making this a long single document.	2 / 3
	Total	10 / 12 Passed

Description

32%Scale 1-3

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 provides a basic sense of what the skill does—displaying project-related information—but lacks specificity about the concrete actions performed and entirely omits guidance on when Claude should select it. The trigger terms are moderately relevant but miss common user phrasings, and the description could easily conflict with other project management or task tracking skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about project status, progress updates, current tasks, or what to work on next.'

Include more natural trigger terms users would say, such as 'progress', 'what's next', 'todo', 'task list', 'dashboard', or 'overview'.

Clarify what 'active tracks' and 'next actions' mean concretely, or expand with specific actions like 'summarizes in-progress work items, lists pending tasks, and highlights blockers'.

Dimension	Reasoning	Score
Specificity	Names some actions ('display project status', 'active tracks', 'next actions') but these are somewhat vague—'active tracks' and 'next actions' are domain-specific terms without further elaboration of what concrete operations are performed.	2 / 3
Completeness	Describes what the skill does (display status/tracks/actions) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'project status' and 'next actions' that users might say, but misses common variations like 'progress', 'dashboard', 'todo', 'task list', 'what's next', or 'overview'.	2 / 3
Distinctiveness Conflict Risk	Terms like 'project status' and 'active tracks' provide some specificity to a project management domain, but could overlap with general project management, task tracking, or dashboard skills without clearer scoping.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/conductor-status/SKILL.md
Commit: 7520423

Reviewed: ~15 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.