conductor-setup
Configure a Rails project to work with Conductor (parallel coding agents)
56
48%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/conductor-setup/SKILL.mdQuality
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 specific concrete actions and explicit trigger guidance. While it identifies a reasonably distinct niche (Rails + Conductor), it fails to tell Claude when to select this skill and doesn't enumerate the specific configuration steps involved. Adding a 'Use when...' clause and listing concrete actions would significantly improve it.
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 'set up Conductor configuration files, configure agent parallelism settings, install required gems, modify Rails environment for multi-agent workflows'.
Include common term variations users might use, such as 'Ruby on Rails', 'multi-agent', 'agent orchestration', or 'parallel coding setup'.
| 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 | Describes what at a high level (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', 'agent setup', 'parallel development', 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 |
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 file contents that Claude can directly create. Its main weaknesses are a slightly verbose structure with some boilerplate sections (Limitations, When to Use) and a verification section that lacks specific validation checkpoints or error recovery steps. The Rails config updates are well-handled with conditional logic but add bulk that could be split out.
Suggestions
Remove the generic 'Limitations' boilerplate section — it adds no skill-specific value and wastes tokens.
Strengthen the Verification section with specific checks (e.g., `test -x bin/conductor-setup && echo 'OK'`, `grep REDIS_URL config/cable.yml`) and add error recovery guidance if script/server fails to start.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with concrete file contents, but the 'Limitations' boilerplate at the end is generic filler that adds no value. The 'When to Use' section also restates what's obvious from context. The Redis config examples are slightly repetitive but justified since each targets a different file. | 2 / 3 |
Actionability | Fully executable and copy-paste ready: complete file contents for conductor.json, bin/conductor-setup, and script/server are provided with exact code. Rails config updates include specific Ruby/YAML snippets for each file with clear patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (create files 1-4, then verify), but the verification section is weak — 'Run script/server to verify it starts without errors' lacks specifics on what success looks like. There's no error recovery guidance if setup or server start fails, and no validation between creating files and running the server. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear headers and numbered sections, making it easy to navigate. However, the four Rails config file updates could be referenced in a separate file since they're conditional modifications, and the skill is moderately long for a single SKILL.md with no external references. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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
93c57b2
- Reviewed
Table of Contents
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.