conductor-setup

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

Quality

43%

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 ./plugins/antigravity-awesome-skills-claude/skills/conductor-setup/SKILL.md

Quality

Content

64%Scale 1-3

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 config updates or server startup fail.

Suggestions

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

Add error recovery guidance to the Verification section, e.g., 'If script/server fails, check that PORT is not in use and REDIS_URL is reachable' to improve workflow clarity.

Dimension	Reasoning	Score
Conciseness	The skill 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 clear from 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 provide 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 guidance on what to do if it fails, and there's no explicit feedback loop for error recovery during the config update steps.	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 potentially be split out for cleaner navigation. However, given no bundle files exist and the skill is moderately sized, the inline approach is acceptable but not optimal.	2 / 3
	Total	9 / 12 Passed

Description

22%Scale 1-3

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 narrow domain (Rails + Conductor), it fails to explain what configuration steps are involved or when Claude should select this skill. It reads more like a task title than a skill description.

Suggestions

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

List specific concrete actions such as 'Sets up .conductor.yml, configures file locking, adjusts database settings for parallel agent access'.

Include natural keyword variations users might say, such as 'setup', 'initialize', 'multi-agent development', or 'parallel coding setup'.

Dimension	Reasoning	Score
Specificity	The description says 'Configure a Rails project to work with Conductor' which names a domain (Rails + Conductor) but describes only one vague action ('configure'). It doesn't list specific concrete actions like setting up config files, installing gems, modifying environment settings, etc.	1 / 3
Completeness	The description partially answers 'what' (configure Rails for Conductor) but has no 'Use when...' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	It includes 'Rails', 'Conductor', and 'parallel coding agents' which are relevant keywords. However, it misses natural variations users might say like 'setup', 'multi-agent', 'parallel development', 'agent configuration', or specific tool names associated with Conductor.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Rails' and 'Conductor' is fairly specific and unlikely to conflict with generic Rails skills, but 'configure' is broad enough that it could overlap with other Rails configuration or setup skills.	2 / 3
	Total	6 / 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: popey/claude-code-skills
Path: plugins/antigravity-awesome-skills-claude/skills/conductor-setup/SKILL.md
Commit: a5a6601

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.