conductor-setup

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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 tight, fully-executable setup recipe with clear sequencing and verification, appropriately self-contained with no need for external references. It is strong across all dimensions and needs no changes.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward—executable bash/json/ruby/yaml blocks with only purposeful inline comments—and assumes Rails/Redis competence rather than explaining basics, matching the score-3 anchor where every token earns its place.	3 / 3
Actionability	It provides complete, copy-paste-ready scripts (conductor.json, bin/conductor-setup, script/server) plus exact Redis config snippets and chmod commands, matching the score-3 fully-executable anchor rather than the pseudocode at a 2.	3 / 3
Workflow Clarity	Creation is a numbered four-part sequence with conditional skip-guards ("if it doesn't already exist… skip and inform") and an explicit Verification checklist (confirm executables, run script/server, check REDIS_URL refs), satisfying the clear-sequence-with-validation anchor at 3.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single self-contained file is organized into well-signaled sections (When to Use, What to Create, Implementation Notes, Verification, Limitations) with no nested references, which per the rubric's simple-skill note earns a 3.	3 / 3
	Total	12 / 12 Passed

Description

72%

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 concrete and distinctive for a narrow product niche, but it states only the "what" and omits an explicit "Use when…" trigger clause, which caps completeness at 2. Adding a when-to-use clause would raise the weakest dimension.

Suggestions

Append an explicit trigger clause, e.g. "Use when setting up a Rails repo to run inside Conductor workspaces, or when the user mentions Conductor, parallel coding agents, or isolated workspace scaffolding."

Expand the action list beyond the single verb "Configure" to surface the concrete outputs (conductor.json, bin/conductor-setup, script/server, Redis isolation) that the body delivers, boosting specificity toward a 3.

Dimension	Reasoning	Score
Specificity	Quotes "Configure a Rails project to work with Conductor" name the domain and a single action, matching the score-2 anchor that names a domain and some actions without being comprehensive; it does not list multiple specific concrete actions required for a 3.	2 / 3
Completeness	The description clearly answers what ("Configure a Rails project to work with Conductor") but provides no "Use when…" trigger clause, so it sits at the score-2 anchor where "when" is missing or only implied rather than explicit.	2 / 3
Trigger Term Quality	"Rails project", "Conductor", and "parallel coding agents" are natural terms a user would say when needing this skill, giving good coverage of relevant triggers rather than the limited/technical wording of a 2.	3 / 3
Distinctiveness Conflict Risk	The Conductor-plus-Rails pairing is a clear niche with distinct triggers unlikely to conflict with other skills, matching the score-3 anchor; it is far more specific than the overlapping examples at a 2.	3 / 3
	Total	10 / 12 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
Commit: 5e71bba

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