CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flow-parallel

Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/flow-parallel/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 exceptionally actionable and the workflow is clearly sequenced with validation gates and error-recovery loops throughout — a model orchestration procedure. Its weaknesses are structural: significant repetition (prohibitions restating inline rules, per-step blocking reminders, version annotations) and a monolithic single-file layout where large script templates and examples would be better split into referenced files.

Suggestions

Move the launch.sh template, dependency-validation script, and usage examples into reference files (e.g., references/launch-template.sh, references/examples.md) linked from SKILL.md to cut the main file's size substantially.

Remove the duplicated Prohibitions section or reduce it to rules not already stated inline, and drop the repeated per-step "DO NOT PROCEED" banners in favor of the frontmatter validation_gates list.

Relocate version annotations (v8.44.0, v8.32.0, v8.45.0) into a changelog/deprecated section or remove them, since inline version numbers are time-sensitive and add tokens without guiding execution.

DimensionReasoningScore

Conciseness

The body is dense operational content with no explanations of concepts Claude already knows, but contains noticeable padding: a 12-bullet Prohibitions section largely restating rules already stated inline, "DO NOT PROCEED TO STEP X until..." repeated after every step, a decorative banner template, and scattered version annotations ("v8.44.0", "v8.32.0", "v8.45.0") that are time-sensitive and not placed in a deprecated/old-patterns section. It sits above anchor 2 (the core scripts are tight and justified) but below anchor 4 because several sections could be trimmed or consolidated.

3 / 5

Actionability

Fully executable throughout: a copy-paste-ready bash launch script with fail-safe exit paths, a complete Python dependency-validation and wave-assignment script, explicit templates with every placeholder called out and replacement instructions, and four worked examples covering the common cases (auth system, migration, multi-issue fixes, independent tools). Matches anchor 5.

5 / 5

Workflow Clarity

A clear mandated 7-step sequence with explicit validation gates after each step (wbs_generated, instructions_written, processes_launched, all_work_packages_complete), per-wave dependency checks, and error-recovery feedback loops (retry only the failed WP, timeout handling, missing-CLI handling). As a batch operation it has extensive validation, matching anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist and everything (~950 lines, including a ~120-line launch.sh template and the full dependency-validation script) is inlined in a single SKILL.md. Section headers and flow are clear (above anchor 2's minimal structure), but content that clearly belongs in separate files (the launch script template, dependency validation code, examples) is inline with no skill-bundle references, matching anchor 3.

3 / 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 communicates a clear, specific capability set with natural trigger terms, but it omits any explicit "when to use" guidance, which both caps completeness and weakens its triggering behavior. Adding a "Use when..." clause with synonyms (e.g., batch, concurrently) would address the two weakest aspects.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to parallelize, batch, or concurrently execute a large change, migration, or multiple issue fixes."

Include natural synonyms users would say ("batch", "in bulk", "at the same time") in the description itself rather than only as frontmatter aliases.

Briefly state the end-to-end outcome (decompose → parallel workers → merged/validated results) so the "what" covers the full capability.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Decompose and execute" "large changes, migrations, or multi-issue fixes" "in parallel with quality gates" — applied to named target types. It matches anchor 4 (several specific actions, minor coverage gaps): not 5 because downstream actions like merging/aggregating results are unstated, and not 3 because it goes beyond 1-2 actions over a generic domain.

4 / 5

Completeness

The "what" is clearly stated ("Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates") but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural phrases users would say are present: "migrations", "multi-issue fixes", "parallel", "large changes". This matches anchor 4 (good keyword coverage, a few natural terms missing): not 5 because common synonyms like "batch", "in bulk", "concurrently", or "refactor" are absent from the description (they exist only as frontmatter aliases), and not 3 because multiple relevant natural terms are covered.

4 / 5

Distinctiveness Conflict Risk

The parallel decomposition of compound tasks into work packages is a fairly distinct niche with minor overlap risk against single-issue fix skills or general orchestration/migration skills, since "large changes" is somewhat broad. This matches anchor 4 (mostly distinct, minor overlap risk) rather than 5's clear-niche bar.

4 / 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

skill_md_line_count

SKILL.md is long (947 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

nyldn/claude-octopus

Path

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