CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ac-parallel-coordinator

Coordinate parallel autonomous operations. Use when running parallel features, managing concurrent work, coordinating multiple agents, or optimizing throughput.

Quality

75%

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 ./.claude/skills/ac-parallel-coordinator/SKILL.md

The canonical home for this skill is ac-parallel-coordinator in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 lean overview with a verified, executable Quick Start and an appropriately one-level-deep pointer to the implementation script. Its main weakness is workflow guidance: for a batch-execution skill it documents no validation loop (checking ParallelResult.failed, re-running failures) and omits the feature_list.json prerequisite that makes the Quick Start actually runnable.

Suggestions

Add a validation step after execution, e.g., "Check results.failed and results.completed; re-run or investigate failed features before proceeding," to satisfy the batch-operation feedback-loop requirement.

Document the prerequisite input: a brief example of the feature_list.json schema (id, dependencies, category, passes) that _load_features expects, without which find_parallel_opportunities returns an empty list.

Drop the redundant restatement of purpose (the opening line and Purpose section repeat the H1 and description) and fold that space into result interpretation instead.

DimensionReasoningScore

Conciseness

The ~25-line body is lean, but the H1, the opening line "Coordinate parallel autonomous operations.", and the Purpose section all restate the same intent — a few redundant tokens that could be trimmed, matching anchor 4 rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

The Quick Start is real, executable code whose API matches the actual scripts/parallel_coordinator.py implementation (ParallelCoordinator(project_dir), find_parallel_opportunities(), execute_parallel(group)); it misses anchor 5 because prerequisites are absent — no feature_list.json input format, no async context for the await calls, and no guidance on interpreting results.

4 / 5

Workflow Clarity

A rough sequence is implied (find groups → execute a group → inspect results) but there are no validation checkpoints and no error-recovery guidance for failures or timeouts; since execute_parallel is a batch operation, the rubric's cap for missing validation applies, keeping this at anchor 3.

3 / 5

Progressive Disclosure

The under-50-line body is a clear overview with well-organized sections, and its single reference — "See `scripts/parallel_coordinator.py` for full implementation" — points to a real file that is one level deep and clearly signaled, matching the anchor-5 pattern.

5 / 5

Total

16

/

20

Passed

Description

66%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 correctly pairs a what-statement with an explicit multi-scenario "Use when" clause in third person, but the capability statement is a single abstract action and the trigger terms overlap with common agent-orchestration vocabulary. Solid, but it could enumerate the concrete operations (grouping independent features, executing them in parallel, handling failures) that the bundled script actually performs.

Suggestions

Replace the abstract "Coordinate parallel autonomous operations" with the concrete capabilities, e.g., "Groups independent features by dependency and category, executes them in parallel with timeout handling, and reports completed vs. failed features."

Sharpen distinctiveness by scoping the when-clause to a concrete trigger artifact, e.g., "Use when a feature_list.json of pending features exists and you need to identify which can safely run concurrently."

Add natural trigger variations such as "run features simultaneously" or "which features can run at the same time" to broaden keyword coverage.

DimensionReasoningScore

Specificity

The what is a single action — "Coordinate parallel autonomous operations" — naming the domain plus one concrete action, like anchor 3's two-action example; it is not anchor 4 because the trigger clause ("running parallel features, managing concurrent work") lists use-cases rather than several distinct capabilities.

3 / 5

Completeness

Both what ("Coordinate parallel autonomous operations") and an explicit "Use when..." clause with four trigger scenarios are present; it falls short of anchor 5 because the what is a single abstract action without the multiple concrete capabilities in the anchor-5 example.

4 / 5

Trigger Term Quality

Good natural-term coverage via "running parallel features, managing concurrent work, coordinating multiple agents, or optimizing throughput"; not anchor 5 because common synonyms (e.g., "simultaneously", "at the same time") and any concrete file or protocol triggers are missing.

4 / 5

Distinctiveness Conflict Risk

Triggers like "coordinating multiple agents" and "managing concurrent work" risk overlap with agent-orchestration and general concurrency skills, matching anchor 3; it is more specific than anchor 2's broad phrasing but lacks anchor 4's tight niche.

3 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fernandezbaptiste/Skrillz

Path

.claude/skills/ac-parallel-coordinator/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.