conductor-setup

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

Quality

56%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-setup/SKILL.md

The canonical home for this skill is conductor-setup in sickn33/agentic-awesome-skills

Quality

Content

79%Scale 1-3

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, actionable skill with complete executable code for every file that needs to be created. It respects Claude's intelligence by not over-explaining concepts. The main weakness is the verification section, which could benefit from more explicit validation steps and error recovery guidance, particularly given that multiple config files are being modified.

Suggestions

Strengthen the verification section with specific validation commands (e.g., check port binding, verify Redis connectivity with a specific command, validate that ENV variables are being read correctly)

Add a brief error recovery note for common failure modes (e.g., what to do if bundle install fails in a worktree, or if Redis isn't running)

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. It doesn't explain what Rails, Redis, or Conductor are. Every section provides specific files to create with exact content. The implementation notes are brief and necessary constraints.	3 / 3
Actionability	Every file has complete, copy-paste ready content with exact paths. The bash scripts and Ruby/YAML config snippets are fully executable. Specific commands like chmod are included where needed.	3 / 3
Workflow Clarity	The steps are clearly sequenced (create files 1-4, then verify), but the verification section is weak — 'Run script/server to verify it starts without errors' lacks specific validation criteria or error recovery steps. For operations modifying multiple config files, there's no feedback loop for catching issues.	2 / 3
Progressive Disclosure	The content is well-structured with clear headers and numbered sections, but it's somewhat long for a single file. The Rails config updates section (4 sub-files) could potentially be referenced separately. However, for a skill of this size, inline content is reasonable.	2 / 3
	Total	10 / 12 Passed

Description

32%Scale 1-3

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 identifies a specific technology pairing (Rails + Conductor) but is too terse and lacks critical detail. It fails to include a 'Use when...' clause, lists no specific configuration actions, and doesn't provide enough trigger terms for reliable skill selection.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about setting up Conductor, configuring parallel coding agents in Rails, or mentions 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 say, such as 'multi-agent', 'parallel tasks', 'agent orchestration', 'Conductor setup', and 'Rails parallel agents'.

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	Answers '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 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 'setup', 'multi-agent', 'parallel tasks', 'Rails config', or 'agent orchestration'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Conductor' and 'parallel coding agents' provides some distinctiveness, but 'Configure a Rails project' is broad enough to 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-setup/SKILL.md
Commit: 7520423

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