CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

delegate-to-agent

Route user-facing AI work through the app's agent chat. Use when adding an AI-powered button, workflow, research task, generation flow, or follow-up.

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

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

An exemplary instruction-only skill body: lean, app-specific, and immediately actionable, with a complete code example, precise parameter decision rules, and clean section structure. No bundle files exist or are needed.

DimensionReasoningScore

Conciseness

The ~50-line body explains nothing Claude already knows; every sentence is app-specific policy (parameter semantics, submit/background behavior, boundary rules), matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

The body provides a copy-paste-ready TypeScript snippet with its full import path, plus exact decision rules for each call variant ('submit: true' vs 'submit: false' prefill, 'background: true' with 'openSidebar: false') and explicit prohibitions (no provider SDKs, no hidden second agent), fully covering the common cases.

5 / 5

Workflow Clarity

This is a single-action routing skill and that action is unambiguous with clear variant-selection guidance; per the simple-skill guideline, workflow clarity can score 5, and no destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

The body is under 50 lines with no need for external references, organized into clear sections (Rule, Start a visible agent turn, Keep the boundary clear, Related skills), and its cross-skill pointers are one level deep and clearly signaled, satisfying the simple-skill exception for a top score.

5 / 5

Total

20

/

20

Passed

Description

78%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 well-crafted description with an explicit what-and-when structure and natural trigger phrases for AI-feature development work. Its main limitation is capability coverage: it states a single routing action rather than enumerating what the skill concretely enables (context passing, silent background tasks, composer prefill).

Suggestions

Enumerate one or two more concrete capabilities in the what-clause (e.g., passing selected-record context, running silent background tasks, prefilling the composer for review) to lift specificity beyond a single 'route' action.

Add natural synonyms users might say, such as 'AI feature', 'assistant', or 'LLM-powered', to broaden trigger-term coverage.

Qualify the broad 'workflow' and 'follow-up' triggers with AI-specific wording (e.g., 'AI workflow step', 'AI follow-up reply') to reduce overlap with generic workflow or UI skills.

DimensionReasoningScore

Specificity

The description names one concrete action — "Route user-facing AI work through the app's agent chat" — which matches the anchor for naming the domain with 1-2 concrete actions; the trigger list (button, workflow, research task, generation flow, follow-up) describes when-conditions rather than additional capabilities, so it falls short of 'lists several specific actions'.

3 / 5

Completeness

It explicitly answers both what ("Route user-facing AI work through the app's agent chat") and when ("Use when adding an AI-powered button, workflow, research task, generation flow, or follow-up") with concrete trigger phrases, matching the top anchor; the when-clause is already specific, so it is not the level-4 'could be more explicit' case.

5 / 5

Trigger Term Quality

Terms like "AI-powered button", "research task", "generation flow", and "follow-up" are natural phrases a developer would say when needing this skill, but common synonyms such as "AI feature", "assistant", or "LLM-powered" are missing, matching the 'good keyword coverage; a few natural terms missing' anchor rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The agent-chat delegation niche is clear with mostly distinct triggers, but "workflow" and "follow-up" are broad terms and the description overlaps trigger space with the closely related `actions` and `context-awareness` skills, matching 'mostly distinct; minor overlap risk' rather than 'minimal conflict risk'.

4 / 5

Total

16

/

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

BuilderIO/agent-native

Path

.agents/skills/delegate-to-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.