conductor-setup

Configure a Rails project to work with Conductor (parallel coding agents)

Quality

48%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/conductor-setup/SKILL.md

Quality

Content

64%

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

This is a solid, actionable skill with complete executable code for all files that need to be created. Its main weaknesses are some unnecessary boilerplate (generic limitations section, 'When to Use' that restates the obvious) and a verification section that lacks error recovery guidance. The workflow is clear but could benefit from explicit feedback loops when modifying existing Rails config files.

Suggestions

Remove the generic 'Limitations' boilerplate and the 'When to Use' section — Claude can infer applicability from the skill description and content.

Add error recovery guidance to the verification section: what to check if `script/server` fails to start (e.g., missing dependencies, port conflicts, Redis not running).

Consider adding a validation step between modifying each Rails config file and proceeding to the next, such as checking syntax validity.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with concrete code blocks, but includes some unnecessary padding like the 'When to Use' section (Claude can infer applicability), the generic 'Limitations' boilerplate at the end, and some redundant explanatory text around the code blocks. The 'Implementation Notes' section partially repeats what's already implied by the instructions.	2 / 3
Actionability	Every file to create is shown with complete, copy-paste-ready content. The bash scripts and Ruby/YAML config snippets are fully executable. Specific commands like `chmod +x` are included, and the Rails config updates show exact code patterns to use.	3 / 3
Workflow Clarity	The steps are clearly sequenced (create conductor.json, then setup script, then server script, then update configs), and there's a verification section. However, the verification step 'Run script/server to verify it starts without errors' lacks error recovery guidance — what to do if it fails. For a workflow involving modifying multiple config files, there's no feedback loop for catching issues mid-process.	2 / 3
Progressive Disclosure	The content is well-structured with clear headers and sections, but everything is inline in a single file. The Rails config updates section (4 sub-files) could benefit from being separated or condensed. With no bundle files, there's no external reference structure, but the content length (~100 lines of substantive material) is borderline for needing separation.	2 / 3
	Total	9 / 12 Passed

Description

32%

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 too terse and lacks both specific concrete actions and explicit trigger guidance. While it identifies a reasonably specific domain (Rails + Conductor), it fails to explain what configuration steps are involved or when Claude should select this skill over other Rails-related skills.

Suggestions

Add a 'Use when...' clause with trigger terms like 'set up Conductor', 'parallel agents', 'multi-agent Rails', 'configure Rails for Conductor'.

List specific concrete actions such as 'Sets up worktree configuration, installs required gems, configures agent communication, and creates Conductor-compatible project structure'.

Include common term variations users might use, such as 'Ruby on Rails', 'multi-agent setup', 'parallel coding setup', and 'Conductor configuration'.

Dimension	Reasoning	Score
Specificity	Names the domain (Rails project configuration for Conductor/parallel coding agents) and a general action ('Configure'), but does not list specific concrete actions like setting up config files, installing gems, modifying environment settings, etc.	2 / 3
Completeness	Provides a brief 'what' (configure a Rails project for Conductor) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also quite thin, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'Rails', 'Conductor', and 'parallel coding agents', but misses common variations users might say such as 'Ruby on Rails', 'multi-agent', 'agent setup', 'parallel development', or 'conductor setup'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Rails' and 'Conductor' is somewhat distinctive, but 'Configure a Rails project' is broad enough to potentially overlap with other Rails setup or configuration skills. The mention of 'Conductor' adds some specificity but without more detail it could still conflict with general Rails configuration skills.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 88d1e11

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