CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conductor-setup

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

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is a strong, executable runbook: complete scripts, exact paths, defensive skip-if-exists rules, and a verification checklist. The only notable gaps are a missing error-recovery loop after verification failures and minor repetition between the per-section existence checks and the Implementation Notes.

Suggestions

Add a feedback loop to the Verification section, e.g. 'If script/server fails, check port conflicts and Redis DB assignment, fix, and re-run before proceeding.'

Remove the duplicated existence checks by stating the skip-if-exists rule once in Implementation Notes instead of repeating it in every section.

DimensionReasoningScore

Conciseness

The body is lean: section headers, complete scripts, and targeted notes with no padding or explanation of concepts Claude already knows. It is not a 5 because of small redundancies — 'if it doesn't already exist' is repeated in each section and then restated in Implementation Notes, and 'Make it executable with chmod +x' appears twice.

4 / 5

Actionability

Every step is copy-paste ready: full bash scripts with port/Redis logic, exact file paths (conductor.json, bin/conductor-setup, script/server), chmod commands, and exact Ruby/YAML snippets for each Rails config. It clearly exceeds the 'mostly executable with minor gaps' anchor of 4.

5 / 5

Workflow Clarity

There is a clear numbered sequence (create 3 files, update 4 configs, verify) with explicit skip-if-exists guards and a Verification section with 3 checkpoints, so it is well above anchor 3. It falls short of 5 because there is no error-recovery feedback loop — e.g. what to do if 'script/server' fails to start or a config update breaks Rails.

4 / 5

Progressive Disclosure

The skill is self-contained (~100 lines) with no bundle files, and everything is appropriately inline — nothing that belongs in a separate file is present. Sections are well-organized and easy to navigate, matching the well-organized-structure standard for skills needing no external references.

5 / 5

Total

18

/

20

Passed

Description

61%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 and names a specific, niche integration (Conductor + Rails), giving it good trigger terms and distinctiveness. Its main weakness is the missing 'when to use' trigger clause and the single generic verb 'configure', which leave both completeness and specificity at the mid-level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up or onboarding a Rails project to use Conductor for parallel coding agents.'

Expand the action beyond the generic verb 'configure' to mention the concrete deliverables, e.g. 'Create conductor.json, setup and server scripts, and wire Redis isolation into Rails configs.'

Include natural synonyms users might say such as 'set up', 'onboard', or 'Mac app' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain clearly ('Rails project', 'Conductor') and one concrete action ('Configure'), with a clarifying parenthetical '(parallel coding agents)'. It fits the anchor for 1-2 concrete actions but is not comprehensive — it omits what configuration involves (creating files, updating Redis configs), keeping it below 4.

3 / 5

Completeness

The 'what' is clear (configure a Rails project to work with Conductor) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete and specific, not vague.

3 / 5

Trigger Term Quality

'Rails project', 'Conductor', and 'parallel coding agents' are natural terms a user would say when needing this skill. A few natural variations are missing ('set up', 'setup', 'Mac app'), which holds it just below the comprehensive-synonyms anchor of 5 and comfortably above the 'some relevant keywords but missing variations' anchor of 3.

4 / 5

Distinctiveness Conflict Risk

Naming the niche tool 'Conductor' with the Rails domain makes this mostly distinct with minimal conflict risk from other skills. It falls short of 5 because 'parallel coding agents' and 'configure Rails project' could weakly overlap with generic agent-orchestration or Rails-setup skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/conductor-setup/SKILL.md

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.