CtrlK
BlogDocsLog inGet started
Tessl Logo

dispatching-coding-agents

Dispatch stateless coding agents (Claude Code or Codex) via Bash. Use when you're stuck, need a second opinion, or need parallel research on a hard problem. They have no memory — you must provide all context.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-structured guide with executable CLI references and clear dispatch patterns. Weakest on an explicit output-verification checkpoint and minor conciseness padding in the conceptual framing.

Suggestions

Add an explicit "Verify the subagent's output before applying changes" checkpoint to the dispatch workflow to strengthen validation.

Trim the motivational metaphor ("brilliant intern", "experienced manager") and de-duplicate the context-not-plan guidance that recurs across sections.

Consider moving the Claude Code and Codex flag tables into a separate reference file to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

Most of the body is efficient reference material (CLI flag tables, executable commands, prompt template), but motivational framing like "brilliant intern that showed up today" and repeated context-not-plan explanations are minor over-explanation that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready commands (e.g. `claude -p "..." --model opus --dangerously-skip-permissions`, `codex exec "..." --sandbox workspace-write -C /path/to/repo`), complete flag tables, and a concrete prompt template covering the common dispatch cases.

5 / 5

Workflow Clarity

A clear dispatch → background → check-with-TaskOutput → handle-failures sequence exists with recovery loops in "Handling Failures", but there is no explicit validation checkpoint to verify a subagent's output before applying it.

4 / 5

Progressive Disclosure

The single self-contained file (no bundle directories present) is well-organized with clear section headers; the two CLI flag tables could arguably live in a separate reference file, a minor organization gap that keeps it at 4.

4 / 5

Total

17

/

20

Passed

Description

83%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 strong, specific description that clearly communicates both capability and trigger conditions with natural language. The main improvement area is trigger-term breadth and tightening distinctiveness of the situational triggers.

Suggestions

Add a couple more natural trigger synonyms (e.g. "fresh eyes", "debug with me", "second pair of eyes") to broaden trigger-term coverage.

Tie the trigger phrases more tightly to the dispatch niche (e.g. "Use when a hard coding problem warrants dispatching a stateless subagent for fresh eyes") to reduce overlap with general advisory skills.

DimensionReasoningScore

Specificity

"Dispatch stateless coding agents (Claude Code or Codex) via Bash" names the domain and several concrete actions (second opinion, parallel research, providing context), but coverage is not fully comprehensive enough for a 5.

4 / 5

Completeness

It explicitly states what ("Dispatch stateless coding agents ... via Bash ... no memory — you must provide all context") and when (concrete "Use when you're stuck ..." trigger phrases), matching the anchor for both clearly answered.

5 / 5

Trigger Term Quality

"Use when you're stuck, need a second opinion, or need parallel research on a hard problem" supplies natural phrases a user would say; a few synonyms (e.g. "fresh eyes", "help me debug") are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The niche of shelling out to Claude Code/Codex via Bash is distinct, but the situational triggers "stuck" and "second opinion" carry minor overlap risk with general advisory or review skills, so it sits at 4 rather than 5.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
letta-ai/letta-code
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.