conductor-setup

Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)

Quality

76%

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-setup/SKILL.md

Quality

Content

92%

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

The content is a well-engineered interactive workflow: concise, fully actionable, and sequenced with explicit validation and resume handling. The only weakness is progressive disclosure — everything lives in one large SKILL.md with inline templates rather than offloaded to reference files.

Suggestions

Move the larger inline templates (conductor/index.md and conductor/tracks.md) into separate reference files under a templates/ directory and link to them, keeping SKILL.md as an overview.

Extract the per-section question banks into a reference file so the main body can stay a concise protocol summary.

Consider a brief 'Quick start / Resume' overview at the top so the high-level flow is visible before the detailed Q&A sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what a tech stack or style guide is, and every section (pre-flight, Q&A protocol, artifact generation, state management) earns its place with no padding.	3 / 3
Actionability	It gives concrete executable guidance: exact question prompts, a full setup_state.json schema, specific file paths (conductor/product.md, etc.), and references to real tool calls (Glob, Read).	3 / 3
Workflow Clarity	The multi-step process is clearly sequenced with explicit validation checkpoints ('Validate file writes succeeded before continuing', 'Verify file exists with Read tool') plus error-handling and resume feedback loops for recovery.	3 / 3
Progressive Disclosure	There are no bundle files to defer to, and while the body is well-sectioned it is a single ~400-line monolith with large inline templates (index.md, tracks.md) that could be split out into separate reference files.	2 / 3
	Total	11 / 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 about what the skill produces, but lacks any explicit 'Use when' trigger guidance and leans on domain jargon rather than natural user phrasings. Completeness is the main limiter since the when-to-use context is entirely implicit.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up a new Conductor project or when the user asks to initialize project documentation/context.'

Include natural-language trigger terms users would say (e.g. 'project setup', 'bootstrap project', 'generate project docs') rather than only the Conductor artifact names.

Tighten distinctiveness by naming the Conductor workflow explicitly so it cannot be confused with general scaffolding skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete artifacts the skill creates — 'product definition, tech stack, workflow, style guides' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	It states what the skill does ('Initialize project with Conductor artifacts') but includes no 'Use when...' clause or explicit trigger, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Domain terms like 'Conductor', 'tech stack', 'workflow', and 'style guides' are relevant but miss common natural phrasings a user would actually say, putting it at 'some relevant keywords but missing variations'.	2 / 3
Distinctiveness Conflict Risk	The 'Conductor' niche is somewhat specific, but the surrounding artifact terms are generic enough that it could overlap with general project-setup skills.	2 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 5 missing	Warning

	Total	14 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/conductor-setup/SKILL.md
Commit: e63f7dd

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