CtrlK
BlogDocsLog inGet started
Tessl Logo

delegating-to-agents

How to delegate work to another AI agent (Pi, Codex, Claude Code, Hermes) — picking the right agent, sending prompts to TUI agents, polling progress. Read BEFORE any `cmux send`/`tmux send-keys` to an agent, or whenever delegating, relaying, spawning, or orchestrating agent-to-agent work.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable instruction skill: concrete commands, a clear numbered send sequence with polling loop and error-recovery notes, and well-organized sections with no padding or concept explanations. No bundle files exist, so disclosure is judged on section organization alone.

DimensionReasoningScore

Conciseness

Lean and dense — assumes Claude's competence, explains no basic concepts, and gives every rule as a tight actionable directive (e.g. 'Use ". " or "; " instead of line breaks'). Every token earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands — 'cmux send --surface surface:N "your prompt"', 'cmux send-key --surface surface:N enter', 'codex --yolo', 'claude --print --permission-mode bypassPermissions' — with no pseudocode.

3 / 3

Workflow Clarity

The 'Sending prompts to a TUI agent' section is a clear numbered 1-2-3 sequence and polling is a re-check loop with explicit error-recovery guidance ('If a send failed, the cause was the escaped \"'). Not a destructive/batch operation, so no feedback-loop cap applies.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed, organized into clearly signaled sections (Which agent to pick, Sending prompts, Polling, Remote VPS, The 4 agents, Driving interactive CLIs) — meeting the rubric's short-skill allowance for a 3.

3 / 3

Total

12

/

12

Passed

Description

100%

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 names concrete actions, the four supported agents, and explicit natural-language triggers covering both what the skill does and when to use it. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'picking the right agent, sending prompts to TUI agents, polling progress' — and names the four target agents, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('How to delegate work... picking the right agent, sending prompts... polling progress') and when ('Read BEFORE any cmux send/tmux send-keys... or whenever delegating, relaying, spawning, or orchestrating').

3 / 3

Trigger Term Quality

Covers natural orchestration terms a user would actually say — 'delegating, relaying, spawning, or orchestrating agent-to-agent work' plus concrete triggers 'cmux send' and 'tmux send-keys'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — delegating to TUI agents via cmux/tmux — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mishatojk/davidskills
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.