CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tool-use-orchestration

Use this skill when building agentic loops with Claude tool use — defining tools, handling tool calls, parallel execution, and multi-step reasoning.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A lean, code-first skill that teaches Claude tool-use orchestration through three complete, runnable patterns and a quick-reference table, with strong error-recovery feedback loops baked into the examples. Its weaknesses are minor: the parallel executor is not integrated into the main loop, and a hardcoded model version id introduces mild time sensitivity.

Suggestions

Show how execute_tools_parallel plugs into the main agentic loop (or note that handlers dict maps tool names to callables), so the snippets compose into one runnable program.

Replace the hardcoded model='claude-opus-4-6' with a model variable or note on current model ids to avoid version-sensitive drift, or move version guidance to a dedicated section.

DimensionReasoningScore

Conciseness

The body is almost entirely executable code with a one-sentence overview and a compact reference table; it assumes Claude's competence and explains no basic concepts. Matches anchor 5 ('Lean and efficient; every token earns its place'), not 4 since there is no over-explanation to trim.

5 / 5

Actionability

Complete, copy-paste-ready Python: full tool schema, a runnable agentic loop handling stop_reason, unknown tools, and exceptions, plus a parallel executor with is_error. Held at anchor 4 due to minor gaps — execute_tools_parallel is never wired into the main loop, tool_handlers wiring isn't shown, and model='claude-opus-4-6' is a hardcoded version-sensitive id — rather than 5's fully-covered common cases.

4 / 5

Workflow Clarity

The agentic loop is clearly sequenced with explicit error-recovery feedback: exceptions and unknown tools are returned as error tool_results for Claude to retry, and parallel execution uses return_exceptions=True with is_error. Not a destructive/batch operation, so no validation cap applies; matches anchor 5's explicit feedback loops.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers (Basic Tool Definition, Agentic Loop, Parallel Tool Execution, Quick Reference) and no buried or nested references. Anchor 4 rather than 5 because the body is ~125 lines (above the sub-50-line simple-skill exception) and advanced material like tool_choice usage is compressed into a table row with no reference structure for deeper content.

4 / 5

Total

18

/

20

Passed

Description

75%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.

A solid description that names the domain, lists four concrete capability areas, and includes an explicit 'Use this skill when...' trigger clause. Its main limitations are a 'when' clause that duplicates the 'what' instead of adding distinct trigger phrases, and missing natural synonyms such as 'function calling' or 'agents' that users might say.

Suggestions

Differentiate the 'when' clause from the 'what' clause with concrete user-facing triggers, e.g. 'Use when the user asks about tool calling, function calling, parallel tool calls, or building an agent/agent loop with Claude'.

Add common synonyms users naturally say — 'function calling', 'tool calling', 'agents', 'agent loop' — to improve trigger term coverage.

Mention error handling and forcing/restricting tools (tool_choice), which the skill body actually covers, to make the capability list more comprehensive.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'defining tools, handling tool calls, parallel execution, and multi-step reasoning' — matching anchor 4's 'several specific actions; minor gaps'. Not 5 because it omits capabilities the skill actually covers (error handling, tool_choice forcing), so coverage is not comprehensive.

4 / 5

Completeness

Explicitly answers both what ('defining tools, handling tool calls, parallel execution, and multi-step reasoning') and when ('Use this skill when building agentic loops with Claude tool use'). Falls short of 5 because the 'when' clause merely restates the 'what' rather than adding concrete, distinct trigger phrases users would mention.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('agentic loops', 'Claude tool use', 'tool calls', 'parallel execution') but misses common synonyms like 'function calling', 'tool calling', or 'agents'. Good coverage with a few natural terms missing — anchor 4, not 5 which requires synonym/extension-level breadth.

4 / 5

Distinctiveness Conflict Risk

The niche (agentic loop orchestration) is mostly distinct with clear triggers, but 'Claude tool use' terminology overlaps with general Claude API/SDK reference skills — anchor 4's 'minor overlap risk with closely related skills'. Not 3 since the agentic-loop framing is more specific than a broad 'works with X' claim.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

ProwlrBot/prowlr-marketplace

Path

external/anthropic-official/tool-use-orchestration/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.