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

74%

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

66%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.

A thorough, well-validated interactive setup protocol with strong workflow clarity and good use of bundle assets. Its main weakness is conciseness: substantial meta-protocol and repetition inflate the body well beyond what the actionable content requires.

Suggestions

Condense the 'Operational Standards' section by merging the interaction, mode-selection, and sequential-questioning rules into a compact bullet list, and remove the full welcome-message example block in favor of a one-line instruction.

Deduplicate the 'Trust Disclosure' text in section 2.6 (the 1p/3p warning is stated twice near-identically) and factor the repeated 'Confirmation & Refinement Loop' wording into a single referenced pattern.

Move the full index.md markdown template and the curl install sequence into a reference file (e.g., assets/handshake.md) and link to it, reducing the inline body length.

Dimension	Reasoning	Score
Conciseness	The ~230-line body is noticeably verbose: extensive meta-protocol in 'Operational Standards' (interaction, mode-selection, sequential-questioning rules), a welcome-message example block, near-duplicate 'Trust Disclosure' text repeated in 2.6, and repeated 'Confirmation & Refinement Loop' phrasing across sections could all be tightened.	2 / 5
Actionability	Provides concrete, executable commands (`python3 scripts/resume.py`, `git status --porcelain`, `git ls-files`, `mkdir -p .agents/skills/<skill_name>` with an exact `curl -sSL` install) and a copy-paste index.md template; a few steps remain abstract ('Execute the copy command once the selection is confirmed').	4 / 5
Workflow Clarity	Sections 1-4 and 2.1-2.6 are clearly sequenced with explicit validation checkpoints (mandatory tool-call validation, resume/halt check, git-hygiene warning, index integrity check) and feedback loops (Approve/Revise/Refine, self-correct-once-then-halt), satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	Bundle references are real and one level deep (`assets/code_styleguides/`, `assets/workflow.md`, `assets/catalog.md`, `scripts/resume.py`) and clearly signaled, but the SKILL.md body itself is a heavy monolithic protocol that could offload some detail into reference files.	4 / 5
	Total	15 / 20 Passed

Description

82%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.

A clear, well-structured description that answers both what and when with natural trigger phrases and a distinct niche. Its only weakness is specificity: it summarizes the action at a high level rather than listing the concrete artifacts the scaffold produces.

Dimension	Reasoning	Score
Specificity	Names the domain ('Scaffolds the project and sets up the Conductor environment') with two concrete actions (scaffolds, sets up), but does not enumerate the several sub-artifacts it actually creates (product.md, tech-stack.md, workflow.md, style guides, index), so coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers both what ('Scaffolds the project and sets up the Conductor environment') and when ('Use this whenever a project needs to be initialized or if the Conductor configuration is missing') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases 'a project needs to be initialized' and 'the Conductor configuration is missing' match what a user would say, with only minor synonyms (e.g., 'set up Conductor', 'bootstrap') absent.	4 / 5
Distinctiveness Conflict Risk	The 'Conductor environment/configuration' niche is specific and its triggers (project initialization, missing Conductor config) are unlikely to collide with unrelated skills.	5 / 5
	Total	17 / 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: f06add3

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