CtrlK
BlogDocsLog inGet started
Tessl Logo

delegate-to-agent

How to delegate all AI work to the agent chat. Use when delegating AI work from UI or scripts to the agent, when a user asks for agent behavior or LLM-powered features, when tempted to add inline LLM calls, or when sending messages to the agent from application code.

73

Quality

92%

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

85%

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 skill body anchored by executable code and clear decision guidance. Its main weakness is conciseness — the sub-agent and rationale prose is longer than necessary.

Suggestions

Tighten the 'Why' and sub-agent prose: replace the 'shadow AI' rationale and fan-out/synthesis paragraphs with terse bullet rules, cutting explanatory framing Claude can infer.

Consider moving the 'Delegating to a Sub-Agent (Agent Teams)' section into a separate reference file, leaving SKILL.md as a leaner overview that links to it — this also strengthens progressive disclosure.

Trim redundant restatements of the rule (e.g. the 'Don't' list partly re-explains the opening Rule section); keep the Don'ts as a flat negative checklist without rationale repetition.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code throughout, but the prose around sub-agent teams (fan-out/synthesis discipline, the 'shadow AI' rationale) could be tightened and the ~250-line body carries explanatory framing Claude could largely infer.

2 / 3

Actionability

Provides multiple copy-paste-ready, executable examples with real imports and signatures — sendToAgentChat with full options, completeText, useAgentChatGenerating, callAgent, and a full Popover pattern.

3 / 3

Workflow Clarity

Decisions are clearly sequenced — a submit-vs-prefill table keyed to risk, an explicit 4-item briefing contract checklist, fan-out caps, and synthesis rules — giving unambiguous steerage across the delegation axes.

3 / 3

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep cross-skill references ('See the a2a-protocol skill for the full pattern') and a Related Skills list; no nested reference chains.

3 / 3

Total

11

/

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, third-person description that states the capability concretely and provides an explicit, multi-trigger 'Use when' clause. It is specific, distinct, and free of fluff.

DimensionReasoningScore

Specificity

Names concrete actions — 'delegate all AI work to the agent chat', 'delegating AI work from UI or scripts to the agent', 'sending messages to the agent from application code' — rather than vague language.

3 / 3

Completeness

Explicitly answers what ('How to delegate all AI work to the agent chat') and when via a clear 'Use when ...' clause with multiple concrete triggers, satisfying both halves.

3 / 3

Trigger Term Quality

Covers natural developer phrasings a user would actually say: 'delegating AI work', 'agent behavior', 'LLM-powered features', 'inline LLM calls', 'sending messages to the agent'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — routing AI work through the agent chat vs inline LLM calls — with triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
BuilderIO/agent-native
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.