fleet-orchestration
Orchestrates multi-session workflows via Fleet API. Use when spawning child sessions for parallel or delegated work.
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/fleet-orchestration/SKILL.mdQuality
Discovery
75%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 concise and well-structured with a clear 'Use when' clause and a distinct niche (Fleet API orchestration). However, it could benefit from listing more specific concrete actions beyond 'spawning child sessions' and including more natural trigger terms that users might use when they need this capability.
Suggestions
Add more specific concrete actions, e.g., 'Spawns child sessions, monitors task progress, collects results, and handles failures across parallel workflows via Fleet API.'
Expand trigger terms with natural user language variations, e.g., 'Use when spawning child sessions, running tasks in parallel, delegating work to multiple agents, or fan-out processing.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Fleet API, multi-session workflows) and some actions (spawning child sessions, parallel/delegated work), but doesn't list multiple concrete actions like creating sessions, monitoring progress, collecting results, or handling failures. | 2 / 3 |
Completeness | Clearly answers both 'what' (orchestrates multi-session workflows via Fleet API) and 'when' (use when spawning child sessions for parallel or delegated work) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'Fleet API', 'child sessions', 'parallel', and 'delegated work', but these are somewhat technical. Missing natural user terms like 'run in parallel', 'background tasks', 'multiple agents', 'fan-out', or 'concurrent sessions'. | 2 / 3 |
Distinctiveness Conflict Risk | Fleet API and multi-session orchestration is a very specific niche. The mention of 'child sessions' and 'Fleet API' makes this clearly distinguishable from other skills and unlikely to conflict. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent workflow clarity and concrete executable examples throughout. Its main weakness is moderate verbosity — some sections explain things Claude could infer (parallelizability heuristics, communication examples) and the content could be more token-efficient. The progressive disclosure could also be improved by extracting reference tables and detailed examples into linked files.
Suggestions
Trim the 'Communicate Your Decision' subsection and example quotes — Claude knows how to communicate decisions to users without scripted examples.
Consider extracting the isolation strategy table and the parallelizability decision framework into a linked reference file to keep the main skill leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes some unnecessary verbosity — e.g., the 'When to Orchestrate' section explains obvious heuristics Claude could infer, the 'Communicate Your Decision' section with example quotes is padding, and some tables repeat information. The content could be tightened by ~30% without losing clarity. | 2 / 3 |
Actionability | Every step includes concrete, executable curl commands with realistic payloads, clear field mappings showing where to source values, and specific API endpoints. The callback format examples show exactly what to expect. This is copy-paste ready. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Steps 0-6) with explicit validation checkpoints: Step 0 mandates parallelizability analysis before spawning, Step 5 includes a post-completion conflict check, and Step 6 provides error handling with retry/escalate decision flow. Feedback loops are present for error recovery. | 3 / 3 |
Progressive Disclosure | The content is entirely self-contained in one file with no references to external documentation. While the step-based structure provides good internal organization, the skill is quite long (~200 lines of substantive content) and could benefit from splitting detailed reference material (e.g., isolation strategy details, API response formats) into separate files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- pgermishuys/weave-agent-fleet
- Commit
5ff2c3a
- 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.