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

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, giving complete executable scripts and exact config edits with a clear create-then-verify workflow and explicit validation checkpoints. It stays lean without padding and is well organized for a self-contained setup skill.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no 'Rails is a framework...' padding) and every script comment carries real rationale (e.g. 'never use ln -sf' on symlink preservation); it is efficient overall, though the opening frontmatter-policy paragraph and the somewhat dense Limitations section could be trimmed slightly.

4 / 5

Actionability

Every artifact is given as complete, copy-paste-ready content — full executable bash for 'bin/conductor-setup' and 'script/server', the exact conductor.json JSON, and exact Ruby/YAML one-liners per Rails config file — plus explicit conditional handling ('if it doesn't already exist', 'if [[ -f package-lock.json ]]'), fully covering the common cases.

5 / 5

Workflow Clarity

The sequence is clear (create files 1-4, apply config updates, then verify), and the Verification section lists explicit checkpoints ('Validate script syntax first', 'verify actual port/Redis separation across workspaces', 'Check that Rails configs properly reference ENV['REDIS_URL']'), but there is no explicit validate-fail-retry feedback loop, so it sits just below the level-5 anchor.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body is well organized under clear headers (When to Use, What to Create, Implementation Notes, Verification, Limitations) with everything appropriately inline for a single setup task. Structure is good with no buried references or misfiled content, though the ~130-line body of code blocks could arguably be split into reference files.

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 short, third-person, and highly distinctive thanks to the 'Conductor' trigger term, but it consists of a single generic action verb with no explicit 'when to use' guidance. Adding a 'Use when...' clause and enumerating the concrete artifacts it creates would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to set up or run a Rails project inside Conductor workspaces.'

Enumerate the concrete actions/artifacts — e.g. 'Create conductor.json, bin/conductor-setup, and script/server, and update Redis config to use ENV["REDIS_URL"]' — instead of the single generic verb 'Configure'.

Include common user phrasings like 'set up Conductor' or 'parallel agent workspaces' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The phrase 'Configure a Rails project to work with Conductor (parallel coding agents)' names the domain precisely (Rails, Conductor, parallel agents) but offers only the single generic verb 'Configure' — matching the anchor for domain plus 1-2 concrete actions, not the level above which requires several specific actions.

3 / 5

Completeness

The 'what' is clear (configure a Rails project for Conductor), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the parenthetical '(parallel coding agents)' only weakly implies the 'when', which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'Rails', 'Conductor', and 'parallel coding agents' are exactly the natural terms a user needing this skill would say, giving good keyword coverage; a few common variations like 'set up' or 'workspaces' are missing, so it falls just short of comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The proprietary trigger 'Conductor' plus the Rails-specific scope carves out a clear niche with distinct triggers and minimal risk of firing for the wrong skill; generic Rails setup skills would not claim the Conductor/workspace domain.

5 / 5

Total

15

/

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

sickn33/agentic-awesome-skills

Path

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.