conductor-setup

Name: conductor-setup
Rating: 66 (1 reviews)
Author: sickn33

tessl i github:sickn33/antigravity-awesome-skills --skill conductor-setup

github.com/sickn33/antigravity-awesome-skills

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

Review Score

66%

Validation Score

13/16

Implementation Score

77%

Activation Score

33%

SKILL.md

Review

Evals

Generated

13 days ago

Warnings & errors only

Criteria	Score
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')
metadata_version	'metadata.version' is missing
license_field	'license' field is missing

Overall Assessment

This is a well-structured, highly actionable skill with excellent workflow clarity and state management. Its main weakness is length—the repetitive Q&A sections and inline templates inflate token count when these could be referenced from separate files. The skill successfully guides Claude through a complex multi-step interactive process with proper validation and error recovery.

Suggestions

Extract the Q&A question templates into a separate reference file (e.g., setup-questions.md) and reference it from the main skill to reduce token count
Move the artifact generation templates (index.md, product.md, etc.) to a templates/ directory and reference them rather than inlining the full content

Dimension	Score	Reasoning
Conciseness	2/3	The skill is comprehensive but includes some redundancy (e.g., repeated template structures, verbose suggested answer formats). The Q&A protocol sections could be more condensed since the pattern is repetitive across sections.
Actionability	3/3	Provides fully concrete guidance with specific JSON schemas, exact file paths, complete markdown templates, and explicit question formats. Claude can execute this without ambiguity.
Workflow Clarity	3/3	Excellent multi-step workflow with explicit pre-flight checks, state management after each step, verification of file writes, error handling procedures, and resume capability. Validation checkpoints are clearly defined throughout.
Progressive Disclosure	2/3	The skill is monolithic at ~300 lines when much of the Q&A protocol and template content could be split into separate reference files. References to external resources (implementation-playbook.md, templates/code_styleguides/) exist but the main content is dense.

Overall Assessment

The description provides a basic understanding of the skill's purpose but lacks explicit trigger guidance, which is critical for skill selection. It names specific artifacts which helps with distinctiveness, but the action vocabulary is limited to 'initialize' without explaining the full scope of capabilities or when this skill should be chosen over alternatives.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when starting a new Conductor project, setting up project scaffolding, or when the user mentions product definition, tech stack configuration, or workflow setup'
Include common user phrases and variations such as 'setup', 'bootstrap', 'start new project', 'create project structure', or 'project scaffolding'
Expand the action verbs to clarify what 'initialize' entails - e.g., 'Creates and configures Conductor artifacts including product definition, tech stack, workflow, and style guides'

Dimension	Score	Reasoning
Specificity	2/3	Names the domain (project initialization with Conductor) and lists specific artifacts (product definition, tech stack, workflow, style guides), but doesn't describe what actions are performed with these artifacts beyond 'initialize'.
Completeness	1/3	Describes what it does (initialize project with artifacts) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.
Trigger Term Quality	2/3	Includes some relevant terms like 'initialize project' and 'Conductor artifacts', but lacks common variations users might say like 'setup', 'start new project', 'bootstrap', or 'create project'.
Distinctiveness Conflict Risk	2/3	The mention of 'Conductor artifacts' and specific artifact types provides some distinctiveness, but 'initialize project' is generic enough to potentially conflict with other project setup or scaffolding skills.