agent-native-docs

How to look up version-matched Agent Native framework docs and source in node_modules. Use before coding against @agent-native/core APIs or advanced features.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./packages/core/docs/SKILL.md

Quality

Content

93%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 tight, highly actionable lookup workflow with concrete commands, a useful slug table, and a sensible fallback. The only gap is the absence of an explicit verification checkpoint confirming a relevant doc/source was actually located.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: a short rule, numbered commands, a compact slug table, and a terse Don't list, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Fully executable commands with concrete flags (e.g. `pnpm action framework-search --pattern`, `--scope docs`, `--mode glob`) plus an explicit `rg` fallback path and real slugs, covering the common cases copy-paste ready.	5 / 5
Workflow Clarity	Clear 7-step sequence with an explicit fallback branch (step 6), but no validation/checkpoint to confirm a doc or source hit was actually found before proceeding.	4 / 5
Progressive Disclosure	Under 50 lines with no external references needed; well-organized into Rule, How, Useful Slugs, and Don't sections that are easy to navigate.	5 / 5
	Total	19 / 20 Passed

Description

66%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 is specific to a well-defined niche and answers both what and when, but relies on technical jargon for triggers and lacks comprehensive action coverage. Tightening the trigger language with more natural phrasings would lift the weaker dimensions.

Suggestions

Add natural trigger phrases a user would actually say (e.g. 'Use when the user asks about Agent Native APIs, framework features, or how something in @agent-native/core works').

Broaden the action list beyond 'look up' to include searching, reading specific doc pages, and inspecting source examples.

Include synonyms/variations of trigger terms (e.g. 'Agent Native docs', 'framework reference', 'core APIs').

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('look up version-matched... docs and source in node_modules') but coverage is not comprehensive — no mention of searching, reading specific pages, or inspecting patterns.	3 / 5
Completeness	Clearly states what it does (look up version-matched docs and source) and when to use it ('Use before coding against @agent-native/core APIs or advanced features'), but the 'when' could be more explicit with concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant terms ('coding against @agent-native/core APIs', 'advanced features') but leans on technical jargon and misses common natural phrasings a user would say, with no synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Agent Native framework docs in node_modules) with distinct triggers tied to @agent-native/core, giving minimal conflict risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: BuilderIO/agent-native
Path: packages/core/docs/SKILL.md
Commit: bb282b1

Reviewed: ~21 hours 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.