CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

workspace-dispatch

Single-agent mission orchestrator. Decomposes a mission into tasks, spawns one worker per task using the default model, verifies exit criteria, and chains tasks with retry. No critic pattern — each worker self-verifies. Simple, fast, works with any model config.

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 ./skills/workspace-dispatch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 instruction-only skill with a well-sequenced validated workflow and clean self-contained section organization.

DimensionReasoningScore

Conciseness

Mostly lean with no over-explanation of concepts Claude already knows; the only redundancy is the closing 'Rules' section restating points (one worker per task, self-verify, no servers) already covered above.

4 / 5

Actionability

Provides executable guidance — a real `sessions_spawn(...)` call with parameters, concrete exit-criteria shell commands, and a copy-paste worker-prompt template — with only minor gaps (the dispatch loop is lightly pseudocode-ish).

4 / 5

Workflow Clarity

Clear numbered sequence with explicit validation checkpoints (verify exit criteria → approve/retry), a feedback loop (retry max 3 with error context), and a failure-handling table covering timeouts and exhausted retries.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is self-contained with well-organized sections (Flow, Decomposition Rules, Task Types, Dispatch Loop, Worker Prompt, Completion, Failure Handling) and no nested references.

5 / 5

Total

18

/

20

Passed

Description

58%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 conveys what the skill does with concrete actions and a distinct niche, but it lacks any explicit 'Use when...' trigger guidance and leans on technical jargon over natural user phrases.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to break down a multi-step mission into verified tasks that run unattended.'

Swap internal jargon ('worker', 'exit criteria') for natural user-facing synonyms ('delegate', 'machine-checkable goals').

Mention the task types the orchestrator handles (coding, research, review) to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions — 'Decomposes a mission into tasks, spawns one worker per task... verifies exit criteria, and chains tasks with retry' — with only minor coverage gaps (no example task types).

4 / 5

Completeness

The 'what' is clear (decompose, spawn, verify, chain with retry) but there is no 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Some relevant terms appear ('mission', 'tasks', 'worker', 'retry') but the natural phrases a user would say ('orchestrate', 'delegate', 'break work down') are missing, leaning on internal jargon.

3 / 5

Distinctiveness Conflict Risk

The single-agent worker-per-task-with-retry niche is fairly specific and the 'No critic pattern' framing distinguishes it, with only minor overlap risk against general orchestration skills.

4 / 5

Total

14

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

outsourc-e/hermes-workspace

Path

skills/workspace-dispatch/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.