CtrlK
BlogDocsLog inGet started
Tessl Logo

actions

How to create and run agent actions. Actions are the single source of truth for app operations — the agent calls them as tools and frontend code calls them through client hooks. Use when creating a new action, adding an API integration, or wiring up frontend data fetching.

68

Quality

86%

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

The canonical home for this skill is actions in BuilderIO/agent-native

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 unusually dense, high-signal skill body: executable examples throughout, an explicit decision order with a stop trigger, and a clean one-level-deep reference split. The only trimmable fat is a few long rationale-heavy Do/Don't bullets, and the creation workflow lacks an explicit verification checkpoint.

DimensionReasoningScore

Conciseness

Nearly every sentence carries project-specific constraints Claude could not know (registry keys by filename, fail() vs bare throw semantics, retry-breaker constants, auto-refresh rules), so there is little padding. It misses 5 because several Do/Don't bullets (the 32%-cost anecdote, the four-round-trip explanation) run to paragraph length and could be trimmed.

4 / 5

Actionability

The body gives a copy-paste-ready defineAction example with schema, an http option table, frontend hook examples with inferred types, the pnpm action CLI command, and concrete fail(message, { errorCode, statusCode }) guidance. These cover the common creation, calling, and error cases fully.

5 / 5

Workflow Clarity

The decision order (existing action → extend/create a defineAction → custom route as last resort) plus a stop trigger and a Troubleshooting section give a clear sequence with error-recovery feedback loops. Not 5: there is no explicit post-creation validation step (e.g., verifying the action registered or appears in .generated/action-types.d.ts).

4 / 5

Progressive Disclosure

SKILL.md is a proper overview and pushes sharp edges (outputSchema, authorize, needsApproval, _agentImages, provider wiring) into three well-signaled references that all exist and are cited inline with what each covers. References are exactly one level deep (they point only back to SKILL.md and AGENTS.md), matching the top anchor.

5 / 5

Total

18

/

20

Passed

Description

83%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-constructed description with an explicit, concrete use-when clause and a clear statement of what actions are and how they are consumed. Its only weaknesses are modest keyword coverage of synonyms/variations and slight overlap risk on the API-integration trigger.

DimensionReasoningScore

Specificity

"How to create and run agent actions" plus "the agent calls them as tools and frontend code calls them through client hooks" lists several concrete capabilities with only minor gaps. It stays at 4 rather than 5 because coverage of the action surface (schema, HTTP exposure, hooks detail) is thinner than a comprehensive enumeration, and above 3 because it goes beyond naming just 1-2 actions.

4 / 5

Completeness

It explicitly answers both: the what ("create and run agent actions... the single source of truth for app operations") and the when ("Use when creating a new action, adding an API integration, or wiring up frontend data fetching") with concrete trigger phrases. The when-clause is specific, so this fits the 5 anchor better than the 4 anchor.

5 / 5

Trigger Term Quality

"Use when creating a new action, adding an API integration, or wiring up frontend data fetching" gives natural phrases a user would plausibly say. Not 5 because common variations (e.g. "tool", "endpoint", "calling an action from the frontend", file/extension terms) are absent.

4 / 5

Distinctiveness Conflict Risk

"Agent actions" framed as "the single source of truth for app operations" carves a clear niche with minimal conflict risk. Score 4 rather than 5 because "adding an API integration" could bleed into a provider-integration skill's territory.

4 / 5

Total

17

/

20

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.

Validation — 13 / 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.