CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch-sub-agent

Launch an intelligent sub-agent with automatic model selection based on task complexity, specialized agent matching, Zero-shot CoT reasoning, and mandatory self-critique verification

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/sadd/skills/launch-sub-agent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 content is well-structured and actionable with a clear phased workflow and strong verification gates, but it is substantially over-long and inlines large reusable prompt templates that should be externalized to reference files. Token efficiency and progressive disclosure are the main weaknesses.

Suggestions

Externalize the full Zero-shot CoT prefix and the 5-question self-critique suffix into reference files (e.g. references/cot-prefix.md and references/critique-suffix.md) and reference them by path, keeping only a one-line summary inline.

Trim generic explanations Claude already knows (e.g. 'What are edge cases', the definitional rows of the verification-question table) to reduce padding.

Replace the placeholder Task-tool dispatch block with a concrete, copy-paste-ready example invocation.

DimensionReasoningScore

Conciseness

The ~330-line body extensively explains concepts Claude already knows (decomposing tasks, what edge cases are, generic verification question templates) and pads with verbose CoT/critique scaffolding that could be stated in a few lines, matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor.

2 / 5

Actionability

It provides concrete, mostly-executable guidance: a model-selection table, a decision tree, named specialized agents, and copy-ready prompt templates with explicit required components, with only minor gaps (the Task-tool invocation block uses placeholders rather than literal executable commands).

4 / 5

Workflow Clarity

The five-phase process (analyze -> select model -> match agent -> construct prompt -> dispatch) is clearly sequenced with an explicit mandatory self-critique verification checkpoint and a revise/re-verify loop, missing only minor validation before dispatch.

4 / 5

Progressive Disclosure

No bundle files exist in references/scripts/assets, and the SKILL.md inlines a large monolithic block of reusable prompt scaffolding (the full CoT prefix and 5-question critique suffix) that clearly belongs in separate reference files, matching the 'content that clearly belongs in separate files is inlined' anchor.

2 / 5

Total

12

/

20

Passed

Description

55%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 is specific and mechanism-rich but reads as a feature list rather than trigger guidance: it states what the skill does internally but never tells Claude when to invoke it. Adding a 'Use when...' clause with natural user phrases would lift the two lowest dimensions.

Suggestions

Add an explicit 'Use when ...' trigger clause naming natural user requests (e.g. 'Use when the user wants to delegate a focused task to a sub-agent that auto-selects the best model').

Reword to include user-facing phrasing and synonyms (e.g. 'delegate a task', 'spin up a sub-agent', 'hand off work') rather than only internal mechanisms like 'Zero-shot CoT'.

Tighten the feature list so the lead phrase conveys the core action (dispatch a focused sub-agent) before enumerating capabilities.

DimensionReasoningScore

Specificity

Names the domain (sub-agent dispatch) and several concrete mechanisms ('automatic model selection', 'specialized agent matching', 'Zero-shot CoT reasoning', 'mandatory self-critique verification'), with only minor coverage gaps around the dispatch mechanics themselves.

4 / 5

Completeness

It clearly answers 'what does this do' (launches a sub-agent with model selection and verification) but lacks any 'Use when...' or equivalent trigger clause, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

It contains relevant terms ('sub-agent', 'task complexity', 'self-critique') but these are technical/system phrasings rather than the natural phrases a user would say ('implement a feature', 'research options'); common user-language synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The combination of automatic model selection plus CoT/critique is a fairly distinct niche with only minor overlap risk against a generic 'run sub-agent' skill, though the broad phrase 'Launch an intelligent sub-agent' has some overlap with built-in sub-agent tooling.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

NeoLabHQ/context-engineering-kit

Path

plugins/sadd/skills/launch-sub-agent/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.