CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

delegate-to-ide

Delegate a task to another AI IDE's CLI (codex / claude / opencode / cursor-agent) through an isolated-context subagent. Use when the user says delegate to <ide>, have <ide> do <task>, or offload to <ide>. For one-shot relay use `ai-ide-runner`.

72

Quality

90%

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

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

Highly actionable routing instructions with concrete per-host invocation syntax, explicit failure/limitation handling, and a firm output contract. The main weakness is redundancy: the 'never run the child CLI inline' rule is repeated four times and could be consolidated to one prominent statement plus one backstop reminder.

Suggestions

Consolidate the 'never run the child CLI inline' rule: state it once prominently in the opening and keep one backstop reminder in the Output contract, removing the restatements from the Cursor bullet and Step 2 preface.

Merge the 'When to use this skill vs ai-ide-runner' guidance into the existing scope-boundaries section (or reference the description's routing sentence) to avoid covering the same disambiguation twice.

In Step 2, trim the Claude Code entry to a single current tool name (the `Agent` tool) since listing both 'Agent / Task' invites ambiguity on which to invoke.

DimensionReasoningScore

Conciseness

The core rule ("You are NOT the courier — the `worker` subagent is") is restated four times: the opening paragraph, the Cursor bullet ("that would defeat the context-isolation point that motivates this skill"), the Codex bullet ("do not run the child CLI inline"), and the closing "Do not, under any circumstances, run `claude -p` / `codex exec` ...". The content is otherwise efficient, but this repetition goes beyond the 'minor instances of over-explanation' of the level-4 anchor, fitting 'mostly efficient but could be tightened'.

3 / 5

Actionability

Fully executable per-host guidance: "use the `Agent` / `Task` tool with `subagent_type=worker`", the "`@worker <task prompt>`" mention syntax, "`spawn_agent` tool with `agent_type=\"worker\"` and `fork_turns=\"none\"`", a copy-paste worker prompt block with placeholders, and a concrete role-install check ("`ls \"${CODEX_HOME:-$HOME/.codex}/agents/\"`"). Common cases are covered with commands the agent can run directly.

5 / 5

Workflow Clarity

A clear three-step sequence (parse intent → invoke worker → relay reply) with explicit precondition checks (Codex worker.toml presence via `ls`, the Cursor no-dispatch case) and error-recovery paths ("an empty listing means the role is not installed — say so, do not run the child CLI inline"; "pass that message through and stop"). The Output contract adds a MUST checklist for the final message.

5 / 5

Progressive Disclosure

No bundle files exist, so all content lives in one file; it is well-sectioned (When to use vs ai-ide-runner, Workflow, Output contract, Scope boundaries) and nothing clearly warrants splitting. However, at ~105 lines it exceeds the under-50-line simple-skill exception that would allow a 5 on section organization alone, so it fits 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

95%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 description: concrete action, named targets, explicit trigger phrasings, and proactive disambiguation against the sibling ai-ide-runner skill. Third-person voice throughout, with no padding.

DimensionReasoningScore

Specificity

"Delegate a task to another AI IDE's CLI (codex / claude / opencode / cursor-agent) through an isolated-context subagent" names several specific concrete elements — the action, the mechanism, and all four target CLIs. It stops short of comprehensive coverage (e.g., it doesn't state that the result is relayed back to the user), matching the 'several specific actions; minor gaps' anchor rather than the fully comprehensive anchor.

4 / 5

Completeness

It explicitly answers both questions: the 'what' is "Delegate a task to another AI IDE's CLI ... through an isolated-context subagent" and the 'when' is given with concrete trigger phrases ("Use when the user says delegate to <ide>, have <ide> do <task>, or offload to <ide>"). It even adds routing guidance for the sibling case ("For one-shot relay use `ai-ide-runner`").

5 / 5

Trigger Term Quality

"Use when the user says delegate to <ide>, have <ide> do <task>, or offload to <ide>" provides three natural phrasing variants users would actually say, reinforced by the four concrete CLI names (codex, claude, opencode, cursor-agent). Coverage of natural terms and synonyms is comprehensive for this niche.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (delegating tasks to other AI IDE CLIs via an isolated-context subagent) and explicitly disambiguates from the nearest sibling skill ("For one-shot relay use `ai-ide-runner`"), leaving minimal overlap or wrong-skill trigger risk.

5 / 5

Total

19

/

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

korchasa/flowai-plugins

Path

plugins/flowai-beta/skills/delegate-to-ide/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.