CtrlK
BlogDocsLog inGet started
Tessl Logo

dispatching-parallel-agents

当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用

57

Quality

67%

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 ./skills/dispatching-parallel-agents/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and workflow-clear, with concrete dispatch code and a strong verification checklist. Its main weakness is redundancy — repeated non-applicable-scenario and verification sections — which inflates length without adding value.

Suggestions

Merge the two '不适用场景' / '不适用的场景' sections into a single deduplicated list to cut redundancy

Consolidate the verification guidance so '审查与集成' and '验证' do not repeat the same review/conflict-check steps

Trim the worked example, which re-covers the abort/batch/race cases already illustrated in the '模式' section

DimensionReasoningScore

Conciseness

Mostly tight and instructional with no padding of basic concepts, but it repeats material: two overlapping '不适用场景' sections and verification content duplicated across '审查与集成' and '验证', so it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready executable Task('...') calls and a detailed agent prompt template with real test names and concrete remediation instructions, matching the 'fully executable; copy-paste ready' anchor.

3 / 3

Workflow Clarity

A clearly sequenced 4-step pattern (识别→创建→分派→审查集成) backed by an explicit validation checklist (review summaries, check conflicts, run full suite, spot-check), matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

A well-sectioned single file with no bundle files to reference, but at ~180 lines it exceeds the 'under 50 lines' allowance for a top score, and the duplicated sections mean organization could be improved.

2 / 3

Total

10

/

12

Passed

Description

57%

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 reads as a precise trigger clause but omits the core capability — what the skill actually does (dispatching parallel agents). It is distinctive but incomplete on the 'what' axis.

Suggestions

Add an explicit capability clause stating what the skill does, e.g. 'Dispatches multiple isolated agents to work on independent tasks in parallel'

Include natural trigger terms users would say ('并行', '多个任务', '同时处理') alongside the technical conditions

Combine into a single 'what + when' sentence so both axes are explicit, e.g. 'Dispatches isolated agents to fix independent problems in parallel. Use when you face 3+ independent failures with no shared state or ordering dependencies.'

DimensionReasoningScore

Specificity

Names a domain context ('2个以上可以独立进行、无共享状态或顺序依赖的任务') but lists no concrete actions — it never states what the skill does (dispatch parallel agents), so it falls short of the 'multiple specific concrete actions' anchor.

2 / 3

Completeness

It functions as a 'when' trigger but never answers 'what' the skill does, and a missing explicit what-clause caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Describes a recognizable condition but leans on technical phrasing ('无共享状态', '顺序依赖') and omits natural variations users would more commonly say ('并行', '多个任务', '同时处理'), matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The trigger ('2+ independent tasks, no shared state, no sequential dependency') is a specific, narrow niche unlikely to fire for other skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
jnMetaCode/superpowers-zh
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.