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

Discovery

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 explicit trigger guidance and specific concrete actions. While it identifies a reasonably distinct niche (Rails + Conductor), the absence of a 'Use when...' clause and the lack of detailed capabilities make it insufficient for reliable skill selection among many options.

Suggestions

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

List specific concrete actions such as 'Sets up Conductor configuration files, configures agent parallelism settings, adjusts Rails project structure for multi-agent workflows.'

Include natural keyword variations users might say, such as 'multi-agent', 'parallel agents', 'Conductor setup', 'agent configuration', 'concurrent coding'.

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, or modifying specific settings.	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.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Rails', 'Conductor', and 'parallel coding agents', but misses common variations users might say such as 'setup', 'multi-agent', 'concurrent agents', or 'Rails configuration'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Rails' and 'Conductor' is fairly specific, but 'Configure a Rails project' is broad enough to potentially overlap with other Rails setup or configuration skills.	2 / 3
	Total	7 / 12 Passed

Implementation

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 every file that needs 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 specific error recovery guidance. The workflow is clear but could benefit from explicit validation checkpoints, especially around verifying Redis connectivity and port availability.

Suggestions

Remove the generic 'Limitations' boilerplate and the 'When to Use' section to improve conciseness — Claude can infer when to apply this skill from context.

Strengthen the verification section with specific validation commands and error recovery steps, e.g., 'If port conflict: check CONDUCTOR_PORT is set; if Redis connection fails: verify redis-server is running and REDIS_URL is correct.'

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 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 Redis configuration updates show exact code for each file.	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 steps are vague ('Run script/server to verify it starts without errors') without explicit error recovery or feedback loops for what to do if validation fails.	2 / 3
Progressive Disclosure	The content is well-structured with clear headers and sections, but it's a monolithic file with no references to external documentation. The Rails config updates section (4 sub-files) could potentially be split out, though for a skill of this size (~100 lines of meaningful content) it's borderline acceptable as inline.	2 / 3
	Total	9 / 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: f5dc9e3

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