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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable reference with executable examples and a clear decision workflow, but it is a long monolithic document that would benefit from splitting detailed sections into reference files and tightening the prose-heavy provider-API section.

Suggestions

Split the longer detail sections (Flexible Provider APIs, _agentImages, outputSchema, needsApproval) into one-level-deep reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Tighten the "Flexible Provider APIs" section: convert the multi-paragraph prose into bullet points or a shorter rule plus a code example to reduce token cost.

Consider moving the Common Patterns and Legacy Pattern code blocks into a reference file, keeping SKILL.md as a concise overview pointing to them.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and framework-specific (no padding with concepts Claude already knows), but at ~530 lines it is long and the "Flexible Provider APIs" section is a prose wall that could be tightened, fitting the "mostly efficient but could be tighter" anchor rather than lean.	2 / 3
Actionability	It provides copy-paste-ready, executable code throughout (defineAction with Zod, useActionQuery/useActionMutation, callAction, common patterns) plus concrete commands like `pnpm action my-action --input …`, matching the fully-executable anchor.	3 / 3
Workflow Clarity	The numbered Decision Order (use existing → create/extend defineAction → custom route only for route-only concerns) plus the explicit "Stop trigger" checkpoint (check the exception list before adding server/routes/api/) gives a clearly sequenced workflow with an explicit validation gate.	3 / 3
Progressive Disclosure	No bundle files exist and the entire ~530-line reference lives inline in SKILL.md; sections are well-organized with headers, but at this length content such as Flexible Provider APIs, _agentImages, outputSchema, and needsApproval could be split into one-level-deep reference files, fitting the "content that should be separate is inline" anchor.	2 / 3
	Total	10 / 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 description: third-person, concrete, with an explicit Use-when trigger clause and a distinct, well-scoped niche. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete operations — "create and run agent actions", "adding an API integration", "wiring up frontend data fetching" — matching the anchor for several specific concrete actions rather than vague language.	3 / 3
Completeness	It explicitly answers both what ("single source of truth for app operations… agent calls them as tools and frontend… through client hooks") and when (explicit "Use when…" triggers), satisfying the highest anchor.	3 / 3
Trigger Term Quality	The "Use when creating a new action, adding an API integration, or wiring up frontend data fetching" clause uses the natural developer terms a user of this framework would actually say, giving good trigger coverage.	3 / 3
Distinctiveness Conflict Risk	"Agent actions" with its specific tool/hook framing is a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

68%

Warnings & errors only

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

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (531 lines); consider splitting into references/ and linking	Warning
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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	11 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/actions/SKILL.md
Commit: c1ee18b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.