conductor-status

Display project status, active tracks, and next actions

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with a clear, validated workflow, concrete file paths, and precise output templates. Its weaknesses are generic boilerplate that pads token usage and a monolithic structure with a dangling reference instead of genuine progressive disclosure.

Suggestions

Remove or condense the generic "Use this skill when", "Instructions", and "Limitations" boilerplate that restates what Claude already knows.

Move the large ASCII output-format templates into a referenced file (e.g. references/output-templates.md) and link to it, or remove the non-existent resources/implementation-playbook.md reference.

Verify any referenced bundle paths actually exist before pointing Claude to them.

Dimension	Reasoning	Score
Conciseness	The core (file paths, parsing rules, output templates, calculation logic) is concrete, but generic boilerplate sections like "Use this skill when", "Instructions" ("Apply relevant best practices and validate outcomes"), and "Limitations" add filler Claude already knows and could be trimmed.	2 / 3
Actionability	It specifies exact files to read (conductor/product.md, tracks/{trackId}/plan.md), regex-based task counting, an explicit progress-bar formula, and copy-paste output templates, giving fully actionable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	A clear sequence runs from Pre-flight Checks (verify product.md/tracks.md exist) through Data Collection to output, with explicit validation checkpoints and dedicated Error States for not-initialized, no-tracks, and track-not-found recovery.	3 / 3
Progressive Disclosure	The body is well-sectioned but monolithic—everything lives inline in SKILL.md—and its single reference to resources/implementation-playbook.md is not clearly signaled and points to a file that does not exist in the bundle.	2 / 3
	Total	10 / 12 Passed

Description

60%

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 is concrete and third-person, clearly stating what the skill displays, but it lacks an explicit "Use when..." trigger clause and relies on partly generic terms. Adding trigger phrasing and more natural variations would lift completeness, trigger quality, and distinctiveness.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks for project status, progress overview, or what to work on next in a Conductor project."

Add natural keyword variations users might say (e.g. "progress", "what's next", "track overview") to improve trigger-term coverage.

Tie the trigger more tightly to the Conductor context to reduce overlap with generic status skills.

Dimension	Reasoning	Score
Specificity	"Display project status, active tracks, and next actions" lists multiple concrete actions (project status, active tracks, next actions) rather than vague language, matching the multiple-specific-actions anchor; third-person voice is correct so no specificity penalty applies.	3 / 3
Completeness	The description clearly answers what it does (display status/tracks/next actions) but provides no "when" guidance; per the judging guidelines a missing "Use when..." clause caps completeness at 2.	2 / 3
Trigger Term Quality	"project status" and "active tracks" are relevant keywords a Conductor user might say, but the description omits an explicit trigger clause and common variations, so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	"active tracks" gives it a Conductor-specific niche, but "project status" is generic and could overlap with other status-style skills, and the absence of explicit triggers keeps it from being clearly distinct.	2 / 3
	Total	9 / 12 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/antigravity-awesome-skills
Commit: 615669b

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.