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

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

Quality

Content

76%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 concise, with executable scripts and exact config snippets. Its main weakness is workflow clarity: the file-creation and config-modification flow lacks an explicit validation feedback loop, which the rubric caps at 3 for batch/destructive operations.

Suggestions

Add an explicit validate-then-fix loop, e.g. after creating files, check executability and rerun any failing step before proceeding.

Surface per-step existence checks inline in the creation steps rather than deferring them all to Implementation Notes.

Tighten the Implementation Notes section to avoid restating checks already implied by the step instructions.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and code-block-driven with no over-explanation of Rails/Conductor concepts; only minor restatement between the step sections and Implementation Notes keeps it from a 5.	4 / 5
Actionability	It provides fully executable bash scripts, exact file paths, and copy-paste-ready Rails config snippets covering the common cases.	5 / 5
Workflow Clarity	Numbered creation steps and a Verification section give a clear sequence, but file creation/modification is a batch-ish operation lacking a validate-then-fix feedback loop, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The single self-contained SKILL.md is well-organized into clear sections with no external references needed; no bundle files exist to evaluate, and minor organization overlap between sections keeps it at 4.	4 / 5
	Total	16 / 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 distinct and uses natural trigger terms but is incomplete: it states what the skill does without an explicit "when to use" clause and lists only a single high-level action. Adding a "Use when..." clause and one or two more concrete actions would raise specificity and completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when setting up a Rails project for Conductor or when the user mentions parallel coding agents."

Add 1-2 concrete actions to the description (e.g. creating conductor.json, wiring Redis isolation) to broaden capability coverage.

Include common synonyms/variants (e.g. "Conductor app", "parallel agents") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Configure a Rails project to work with Conductor" names the domain (Rails, Conductor) and one concrete action, but does not enumerate several specific actions for comprehensive coverage.	3 / 5
Completeness	It gives a clear "what" (configure a Rails project for Conductor) but provides no explicit "Use when..." trigger clause, so completeness is capped at 3 per the missing-trigger-guidance rule.	3 / 5
Trigger Term Quality	"Rails project", "Conductor", and "parallel coding agents" are natural terms a user with this need would say, giving good keyword coverage, though a few synonyms or variants are missing.	4 / 5
Distinctiveness Conflict Risk	"Conductor (parallel coding agents)" is a distinct proper-noun niche with clear triggers and minimal risk of overlapping with other skills.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/conductor-setup/SKILL.md
Commit: 57c135b

Reviewed: 3 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.