CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

multi-agent

Multi-Agent Orchestration - 蚁群仿生设计,定义Agent角色、生命周期、信息素通信、任务分解、冲突解决。当需要多Agent并行协作时路由到此。

Quality

68%

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 ./templates/skills/orchestration/multi-agent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers genuinely actionable orchestration guidance — concrete templates, thresholds, communication formats, and a well-sequenced lifecycle with validation and error-recovery loops. However it is substantially overweight: redundant decision frameworks, restated lifecycle content, decorative flavor language, and material that belongs in reference files all inflate the token cost.

Suggestions

Consolidate the three overlapping decision frameworks (lifecycle table, TeamCreate decision tree, and the 满足任意1条 condition table) into a single decision section, and remove the flavor/decorative terminology that carries no operational meaning.

Move the role startup templates, the /ccg:team 8-phase pipeline, and the pheromone system details into separate reference files (e.g., references/roles.md, references/team-pipeline.md) linked from a lean SKILL.md overview.

Pick one canonical workflow (or state explicitly when the Codex protocol vs the /ccg:team pipeline applies) so the reader follows a single unambiguous execution sequence.

DimensionReasoningScore

Conciseness

The 533-line body contains several padded and duplicated sections: three overlapping decision frameworks (lifecycle table, TeamCreate decision tree, condition table), role startup templates that restate the lifecycle, parallel 'Codex 协议' and '蚁群生命周期' execution tracks, and flavor terminology ('天罗主修', '道基裂痕 +1') that adds tokens without instruction. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections') rather than 3, because the redundancy is pervasive rather than occasional.

2 / 5

Actionability

It provides copy-paste-ready instruction templates (Worker/Reviewer/Lead), concrete SendMessage formats with field specs, an executable git commit example, naming conventions, and specific thresholds (retry ≤2, 30s timeout, concurrency caps, 子任务膨胀 >30). It falls short of 5 because snippets like 'TaskUpdate(taskId, metadata: {...})' and 'spawn explorer/worker/awaiter' are pseudocode-style pseudo-API rather than verifiable executable syntax.

4 / 5

Workflow Clarity

The lifecycle is explicitly sequenced ('执行顺序(不可跳步)' 1-5) with a review→fix feedback loop capped at 2 rounds, file-integrity and cross-reference validation steps, and error handling with degradation paths — matching anchor 4. It misses 5 because three competing workflow tracks (basic ant lifecycle, Codex native protocol, /ccg:team 8-phase pipeline) coexist without explicit guidance on which applies when, and some checkpoints (429 recovery detection, what 'wait 收敛' verifies) are implicit.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but at 533 lines everything is inlined in SKILL.md with no bundle files at all; the role templates, the /ccg:team 8-phase pipeline, and the pheromone system reference are clear candidates for separate reference files. This matches anchor 3 ('some structure but content that should be separate is inline').

3 / 5

Total

13

/

20

Passed

Description

67%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 clearly states what the skill covers and when to route to it, with an explicit when-clause and a recognizable niche. Its main weaknesses are limited natural-language trigger coverage and capability labels that stay at the subtopic level rather than concrete operations.

Suggestions

Add English natural trigger synonyms users would actually say (e.g., 'agent team', 'parallel subagents', 'spawn multiple agents', 'delegate tasks to agents') so routing works regardless of language phrasing.

Make the when-clause more concrete with explicit trigger conditions, e.g., 'Use when a task involves ≥3 independent files/modules, needs ≥2 parallel workflows, or the user asks for a team of agents'.

DimensionReasoningScore

Specificity

The description enumerates five concrete capability areas ("定义Agent角色、生命周期、信息素通信、任务分解、冲突解决") matching the 'lists several specific actions; minor gaps' anchor. It falls short of 5 because these are subtopic labels rather than concrete operations, and "蚁群仿生设计" is decorative flavor.

4 / 5

Completeness

Both parts are explicit: what ("定义Agent角色、生命周期、信息素通信、任务分解、冲突解决") and when ("当需要多Agent并行协作时路由到此"). The when-clause is present but could be more specific with concrete trigger conditions (e.g., ≥3 independent files, user requests a team), matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

The when-clause "当需要多Agent并行协作时路由到此" supplies relevant keywords (multi-Agent, 并行协作, orchestration), but misses common natural variations (agent team, parallel tasks, spawn agents, task delegation) and mixes Chinese with English, narrowing the trigger surface. Not 4 because a user phrasing the need differently would likely not match.

3 / 5

Distinctiveness Conflict Risk

Multi-agent orchestration is a clear niche and the pheromone/stigmergy framing is distinctive, so it is mostly distinct with only minor overlap risk against general workflow or orchestration skills. It does not reach 5 because 'multi-agent parallel collaboration' could still overlap with sibling agent-coordination skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository

fengshao1227/ccg-workflow

Path

templates/skills/orchestration/multi-agent/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.