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 verbosity (boilerplate limitations section, redundant instructions about checking file existence), and the verification section lacks error recovery guidance. The conditional Rails config updates are well-handled with clear 'if exists' guards.

Suggestions

Remove the generic 'Limitations' boilerplate section — it adds no value specific to this skill and wastes tokens.

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).

Trim the 'When to Use' section — Claude can infer when to apply this skill from the description and content.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete code blocks, but includes some unnecessary verbosity like the 'When to Use' section (Claude can infer applicability), the generic 'Limitations' boilerplate at the end, and some redundant phrasing like 'Create the script directory if needed, then create script/server if it doesn't already exist' when the implementation notes already cover this.	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 if it fails? There's no feedback loop for fixing issues, which matters for a multi-step configuration 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 separate files with examples) could benefit from being split into a reference file, especially since they're conditional modifications. For a standalone skill with no bundle files, the organization is adequate but not optimal.	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 detailed capabilities and explicit trigger guidance. While it identifies a specific domain (Rails + Conductor), it fails to enumerate concrete actions or provide a 'Use when...' clause, making it difficult for Claude to reliably select this skill from a large pool.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about setting up Conductor, configuring parallel coding agents in Rails, or multi-agent workflows.'

List specific concrete actions such as 'Sets up Conductor configuration files, configures agent parallelism settings, installs required gems, and updates Rails environment for multi-agent support.'

Include natural keyword variations users might use, such as 'Ruby on Rails', 'multi-agent', 'parallel agents', 'Conductor setup', and 'agent orchestration'.

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 weak, so this scores 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 setup', 'agent parallelism', or 'Conductor setup'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Rails' and 'Conductor' is fairly specific and unlikely to conflict with many other skills, but 'configure a Rails project' is broad enough that it could overlap with general Rails setup or 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: 6042393

Reviewed: about 2 hours 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.