CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-orchestration-skill

当主 Agent 面临多步骤复杂任务并正在判断要不要 / 怎样把子任务外包给内置子代理(browser / doc-editor / data-analyst / extractor / canvas-designer / coder 等)时触发。**不用于**:单步问答 / 读取 / 简单副作用(主 Agent 直接做)、已经明确要用 `Agent` 且知道 subagent_type 的场景。

64

Quality

77%

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 ./apps/server/src/ai/builtin-skills/agent-orchestration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an efficient, actionable overview of subagent delegation with a clear decision tree, concrete call templates, and explicit system limits. The main gap is the absence of validation/verification checkpoints in the parallel fan-out and result-aggregation workflow.

Suggestions

Add an explicit verification step in the parallel fan-out workflow (e.g. check each subagent returned successfully and inspect outputs before aggregating) to support the batch-operation pattern.

Consider moving the six-subagent capability table and system-limits table into a reference file if the skill grows, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Lean tables and compact sections assume Claude's competence; only minor justificatory prose ('委派本身会引入上下文传递开销…', token-growth rationale) could be trimmed.

4 / 5

Actionability

Provides concrete, copy-paste-ready tool-call templates for Agent and SendMessage and a parallel fan-out example, with only placeholder prompt bodies as a minor gap.

4 / 5

Workflow Clarity

The delegation decision flowchart and parallel fan-out sequence are clearly laid out with explicit system limits, but no explicit verification of subagent results before aggregation is shown.

4 / 5

Progressive Disclosure

Single self-contained SKILL.md with well-organized, clearly headed sections and no nested references; content is appropriately overview-level so the lack of external files is acceptable, though some reference-style tables could optionally be split out.

4 / 5

Total

16

/

20

Passed

Description

80%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 is specific, complete, and distinct, giving clear positive and negative trigger guidance in third person. Its main weakness is trigger-term quality: the keywords describe task categories for Claude's decision rather than natural phrases users would say.

Suggestions

Add a 'Use when the user asks for…' clause with natural user phrasings (e.g. 'scrape a website', 'edit a long document', 'analyze a spreadsheet') to improve trigger-term naturalness.

Include common synonyms or file extensions alongside the subagent trigger terms to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the delegation domain and lists six concrete subagent types (browser / doc-editor / data-analyst / extractor / canvas-designer / coder) plus concrete trigger scenarios, with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (outsource subtasks to built-in subagents via Agent) and when ('当主 Agent 面临多步骤复杂任务…时触发'), reinforced by an explicit '不用于' negative-trigger clause.

5 / 5

Trigger Term Quality

Relevant task-category keywords ('多步骤复杂任务', subagent names, '单步问答/读取') are present but framed for Claude's internal decision rather than as natural user utterances, and common synonym variations are missing.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (subagent delegation via the Agent tool) with explicit positive and negative triggers, minimizing overlap with other skills.

5 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
itsablabla/openloaf-web
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.