conductor-setup

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

Quality

73%

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 ./skills/conductor-setup/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

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

This is a strong, highly actionable skill body: complete executable scripts, exact config-edit guidance, sensible guardrails against overwriting existing files, and a verification section. The main improvement opportunities are trimming the boilerplate Limitations section and adding an explicit failure-recovery loop to the verification workflow.

Dimension	Reasoning	Score
Conciseness	The body is efficient: complete, purposeful scripts with only brief inline comments, no explanation of concepts Claude already knows. It is not level 5 because of small trims available — the opening sentence re-explains what Conductor is and the three generic boilerplate bullets in 'Limitations' add little skill-specific value.	4 / 5
Actionability	Every deliverable is copy-paste ready: a complete conductor.json, full bash scripts for bin/conductor-setup and script/server (including the cksum-based Redis DB derivation), exact chmod commands, and exact Ruby/YAML replacement snippets for four Rails config files. It is fully executable with the common cases covered, matching the top anchor rather than level 4's 'minor gaps'.	5 / 5
Workflow Clarity	A clear numbered sequence (conductor.json → bin/conductor-setup → script/server → Rails config updates), explicit non-destructive rules ("Don't overwrite existing files", "skip it gracefully"), and a Verification section including running script/server. It falls short of level 5 because there is no error-recovery feedback loop (e.g., what to do if script/server fails or a config check doesn't pass), though the operations are guarded against destructive changes.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent), and the body is a single well-organized one-level document with clear section headers covering one cohesive setup task, so nothing is misfiled. It does not reach level 5 because the body is ~113 lines with the full script and config-fallback content inlined; it is well above level 3 since all structure present is appropriate and nothing that clearly belongs in a separate file is buried.	4 / 5
	Total	17 / 20 Passed

Description

65%Weight 40%Scale 1-5

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 concise, specific to its niche, and uses the natural nouns (Rails, Conductor, parallel coding agents) a user would say. Its main weakness is the missing 'when to use' clause and the single generic action verb, which leave trigger conditions to inference. Adding an explicit 'Use when...' sentence with trigger phrases would raise both completeness and specificity.

Suggestions

Append a trigger clause such as 'Use when setting up Conductor for a Rails repo, or when the user mentions Conductor, parallel coding agents, or Conductor workspaces.'

Name one or two concrete deliverables (e.g., 'creating conductor.json, bin/conductor-setup, and script/server with port/Redis isolation') so the action list is more than a generic 'Configure'.

Include common user phrasings like 'set up' or 'onboard' as synonyms of 'Configure' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain clearly ("Rails project", "Conductor", "parallel coding agents") but offers only one generic action — "Configure" — so it matches the anchor of naming a domain with 1–2 concrete actions that are not comprehensive. It is above level 2 because the domain and target artifacts are specific rather than minimal, but below level 4 because no concrete artifacts (conductor.json, script/server, Redis isolation) are mentioned.	3 / 5
Completeness	The 'what' is clear ("Configure a Rails project to work with Conductor"), but there is no 'Use when...' clause or any trigger guidance, which per the judging guidelines caps completeness at 3. It is not level 4 because 'when' is entirely missing rather than merely implicit or underspecified.	3 / 5
Trigger Term Quality	"Rails", "Conductor", and "parallel coding agents" are natural terms a user with this need would say. It is below level 5 because common trigger phrasings like "set up", "workspaces", or "Conductor workspace" are absent, and above level 3 because the key nouns are the exact vocabulary users would use rather than partial synonyms.	4 / 5
Distinctiveness Conflict Risk	"Conductor (parallel coding agents)" carves out a clear niche with distinct triggers; virtually no other skill would fire on this request. The anchor for minimal conflict risk with distinct triggers is the best fit, and nothing suggests overlap with generic Rails skills since the Conductor pairing is explicit.	5 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/conductor-setup/SKILL.md
Commit: 7b534bc

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.