CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

an

Open and operate Agent-Native workspace apps through Dispatch MCP, with inline app surfaces, browser-session authentication, and current screen state.

Quality

73%

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 ./.agents/plugins/agent-native/skills/an/SKILL.md

The canonical home for this skill is an in BuilderIO/skills

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.

The body is a strong operational guide: concrete tool names, a ready-to-use open_app payload, explicit readback validation, and a dedicated failure-handling section. Its only weaknesses are minor repetition of the readback/view-screen rules and no progressive disclosure of longer reference material. Suggestions are omitted as the result is strong overall.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and free of explanations of concepts Claude already knows; only minor repetition (the view-screen-before-edit and read-back-writes points each restated across sections) keeps it from a 5.

4 / 5

Actionability

Gives exact tool names (open_app, list_apps, view-screen, read_view, ask_app), a copy-paste JSON payload for open_app, an exact connector URL, and a concrete retry app id; only open_app is shown as an example payload, leaving minor gaps for other calls.

4 / 5

Workflow Clarity

Sequences are explicit (list_apps if uncertain -> open_app -> verify surface; view-screen -> smallest atomic change -> read back) with explicit validation ('A queued ask_app_status task is not proof an edit completed', confirm writes with readback) and recovery loops in the failure-handling section (check grant, retry once).

5 / 5

Progressive Disclosure

Five well-labeled sections with no dead or nested references and all guidance self-contained; at roughly 107 lines (above the 50-line simple-skill exception) some material (host/connector setup, failure handling) could arguably live in a separate reference file, so structure is good but not optimal.

4 / 5

Total

17

/

20

Passed

Description

53%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 clearly states what the skill does within a distinct niche, but it reads as a feature list rather than trigger guidance. It lacks any 'when to use' clause and natural trigger phrasing, which limits discoverability at invocation time.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to open or work in an Agent-Native app (e.g. slides) beside the conversation, or mentions Dispatch.'

Replace generic verbs with several concrete actions (open apps inline, view current screen state, make selection-aware edits, navigate the open panel) instead of the single catch-all 'operate'.

Include natural user phrasings and app-name examples ('/an slides', 'open the Slides app', 'Dispatch apps') so the description matches what users actually say.

DimensionReasoningScore

Specificity

Names the domain (Agent-Native workspace apps, Dispatch MCP) with one concrete action ('Open') and one generic verb ('operate'); the trailing phrases ('inline app surfaces, browser-session authentication, and current screen state') describe features rather than actions, so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (open and operate Agent-Native apps through Dispatch MCP), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains relevant ecosystem keywords ('Agent-Native', 'workspace apps', 'Dispatch MCP') but they lean technical-jargon and miss natural user phrasings such as specific app names (e.g. 'slides') or casual variations like 'open the app'.

3 / 5

Distinctiveness Conflict Risk

The Dispatch MCP / Agent-Native niche is specific and largely distinct from other skills, but 'workspace apps' is somewhat broad and no distinct trigger phrases are given, leaving minor overlap risk.

4 / 5

Total

13

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/plugins/agent-native/skills/an/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.