conductor-setup

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

Quality

70%

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.

The content is highly actionable and well-structured with executable scaffolding and a verification section. Main gaps are a missing failure-recovery feedback loop and minor trimming opportunities.

Suggestions

Add an explicit feedback loop in Verification: if `script/server` fails to start, re-check Redis URL export and port settings, fix, and re-run.

Tighten repeated "if it doesn't already exist" phrasing into a single upfront instruction.

Consider moving the four Rails-config patch recipes into a reference file linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean: executable scripts with purposeful inline comments and no padding about what Rails/Conductor/Redis are. Not a 5 because a few comments and the "if it doesn't already exist" repetitions could be trimmed further.	4 / 5
Actionability	Provides fully executable, copy-paste-ready artifacts: complete conductor.json, two bash scripts with chmod instructions, and exact Ruby/YAML snippets for each Rails config file. Covers the common cases concretely.	5 / 5
Workflow Clarity	Four clearly sequenced creation steps plus a Verification section listing checks; because validation is present the destructive-config cap at 3 does not apply. Not a 5 because there is no explicit validate->fix->retry feedback loop if `script/server` fails.	4 / 5
Progressive Disclosure	Well-organized into When to Use, What to Create, Implementation Notes, Verification, and Limitations with no nested references and all content appropriately inline. Not a 5 because it exceeds the simple-skill line count and the Rails-config patch list could conceivably live in a reference, though inline is defensible.	4 / 5
	Total	17 / 20 Passed

Description

57%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 specific and clearly distinct but lacks an explicit trigger clause and breadth of actions, capping completeness and trigger quality. Adding a "Use when..." phrase would most improve it.

Suggestions

Append an explicit trigger clause, e.g. "Use when setting up or onboarding a Rails repo to Conductor for parallel coding agents."

Broaden capability language beyond the single verb "Configure" (e.g., scaffold conductor.json, isolate Redis/ports, symlink secrets).

Add natural user phrasings like "parallel coding agents", "worktrees", or "set up" to improve trigger matching.

Dimension	Reasoning	Score
Specificity	"Configure a Rails project to work with Conductor (parallel coding agents)" names the domain (Rails, Conductor) and one concrete action (configure), but offers only that single action with no breadth of capabilities. Not a 2 because the integration target is specific rather than generic; not a 4 because only one action is listed.	3 / 5
Completeness	The "what" is clear (configure a Rails project for Conductor), but there is no explicit "Use when..." trigger clause, so per the guideline completeness is capped at 3. Not a 4 because the when is only weakly implied, not stated.	3 / 5
Trigger Term Quality	Includes relevant natural terms like "Rails project", "Conductor", and "parallel coding agents", but lacks common variations a user might say (e.g., "set up", "parallel agents", "worktrees") and any file/CLI trigger. Not a 4 because coverage of natural phrasings is thin.	3 / 5
Distinctiveness Conflict Risk	Targets a distinct niche — configuring Rails specifically for the Conductor app — with minimal overlap risk against other skills. Not at risk of triggering for unrelated skills.	5 / 5
	Total	14 / 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: b1aebac

Reviewed: ~17 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.