conductor-setup

Scaffolds the project and sets up the Conductor environment. Use this whenever a project needs to be initialized or if the Conductor configuration is missing.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/conductor-setup/SKILL.md

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 highly actionable with concrete commands, templates, and strong validation/feedback checkpoints across a well-sequenced workflow, and it externalizes bulky assets appropriately. Its main liability is verbosity from duplicated sections and repetitive emphasis that could be consolidated.

Suggestions

De-duplicate the resume/fast-forward logic (present in both 1.2 and section 2 step 3) and the third-party trust disclosure (stated twice in 2.6) to remove padding.

Consolidate the recurring single-choice/multiple-choice/Yes-No question-mode instructions (2.1-2.5) into one shared protocol reference instead of restating per section.

Trim generic emphasis ('You MUST', 'CRITICAL') where the imperative verb already conveys the requirement, preserving clarity without the overhead.

Dimension	Reasoning	Score
Conciseness	The ~240-line protocol is noticeably verbose: the resume/fast-forward logic is stated twice (1.2 and step 3 of section 2), the third-party trust disclosure is repeated verbatim in 2.6, and mode-selection instructions recur across 2.1-2.5 with heavy 'You MUST'/'CRITICAL' emphasis that could be tightened.	2 / 5
Actionability	Fully executable guidance throughout: copy-paste commands (`python3 scripts/resume.py`, `git status --porcelain`, `git ls-files`, the exact `curl -sSL <URL>SKILL.md -o ...` sequence), concrete file paths (`conductor/product.md`), and a literal markdown template for `index.md`.	5 / 5
Workflow Clarity	Clear sequenced sections (1-4) with explicit validation checkpoints and feedback loops: HALT when setup_complete is true, 'Tool Validation' self-correct-or-halt rule, the 'Integrity Check' verifying all linked files exist, and the resumption/fast-forward logic for partial setups.	5 / 5
Progressive Disclosure	Heavy referenceable content is correctly externalized into real, one-level-deep bundle files (assets/code_styleguides/, assets/workflow.md, assets/catalog.md, scripts/resume.py) with clearly signaled paths, but the SKILL.md body itself inlines a long operational protocol rather than reading as a lean overview, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

62%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 is well-formed: third-person voice, explicit trigger clause, and a clear niche via the Conductor branding. Its main weakness is that the capability verbs are high-level and the trigger terms rely on the brand name rather than natural user language.

Suggestions

Add a couple of more concrete actions (e.g., 'creates product, tech-stack, and workflow artifacts under conductor/') to lift specificity toward anchor 4-5.

Broaden trigger terms with natural user phrasings like 'start a new Conductor project', 'set up Conductor', or 'initialize SDD scaffolding' instead of relying on the brand name alone.

Dimension	Reasoning	Score
Specificity	Names the domain (Conductor) and two concrete actions ('Scaffolds the project', 'sets up the Conductor environment'), but the actions are high-level and not comprehensive, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	Clearly states what it does and includes an explicit 'Use this whenever...' trigger with two concrete conditions; the 'when' is present and fairly explicit but the 'what' (scaffolds/sets up) is somewhat abstract, so it sits below the fully concrete anchor 5.	4 / 5
Trigger Term Quality	Includes relevant trigger phrases ('project needs to be initialized', 'Conductor configuration is missing') but leans on the brand name 'Conductor' and misses common synonyms or natural variations a user would say.	3 / 5
Distinctiveness Conflict Risk	The 'Conductor' branding and the 'Conductor configuration is missing' trigger carve a clear niche with minimal conflict risk, though the generic 'project needs to be initialized' phrasing leaves minor overlap with other scaffolding skills.	4 / 5
	Total	14 / 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
relative_links	Relative link issues: 5 missing, 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: gemini-cli-extensions/conductor
Path: skills/conductor-setup/SKILL.md
Commit: 6e8f9a8

Reviewed: 14 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.