conductor-setup

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

Quality

73%

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 with complete executable scaffolding and a clear, well-structured workflow including verification. Minor gains are possible by tightening boilerplate and adding interleaved validation checkpoints.

Suggestions

Trim the generic Limitations boilerplate ("Do not treat the output as a substitute for...expert review") to keep the skill lean.

Add an interleaved validation step after file creation (e.g. verify bin/conductor-setup runs before proceeding to script/server) to strengthen the feedback loop for this file-mutating skill.

Consider extracting the Redis config update recipes into a references file so the SKILL.md body stays a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is efficient with concrete file specs and complete fenced code blocks and no padding about Rails/Redis concepts, but the generic "Limitations" boilerplate is mild over-explanation that could be trimmed, so it sits at 4 rather than 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready bash scripts, a complete conductor.json, exact Rails config snippets using ENV.fetch('REDIS_URL', ...), and concrete chmod commands covering the common cases.	5 / 5
Workflow Clarity	A clear numbered creation sequence plus a final Verification section with checkpoints is present, but validation is a final check rather than interleaved per-step validate→fix→retry loops, matching anchor 4.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized section headers (When to Use, numbered What to Create, Implementation Notes, Verification, Limitations) and clear navigation, placing it at anchor 4.	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 specific and distinctive but lacks an explicit "when to use" trigger clause, which caps completeness. It names a clear niche (Rails + Conductor) with concrete, natural trigger terms.

Suggestions

Add an explicit "Use when..." clause to the description, e.g. "Use when setting up or onboarding a Rails project for use with Conductor."

Expand the action beyond the single verb "Configure" to list the concrete deliverables (e.g. "creates conductor.json, bin/conductor-setup, and script/server") to lift specificity.

Include common trigger synonyms like "parallel agents", "Conductor workspaces", or "Conductor setup" to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Rails project", "Conductor") and a concrete action ("Configure"), matching anchor 3, but the single action is high-level and not comprehensive so it does not reach 4.	3 / 5
Completeness	A clear "what" is present ("Configure a Rails project to work with Conductor") but there is no "Use when..." clause in the description, so per the guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	"Rails project" and the product name "Conductor (parallel coding agents)" are natural terms users would say, giving good keyword coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product "Conductor" tied to "Rails" creates a clear niche with distinct triggers and minimal risk of firing for the wrong skill.	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: sickn33/antigravity-awesome-skills
Path: skills/conductor-setup/SKILL.md
Commit: 1f67c44

Reviewed: about 15 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.