agent-native-docs

How to find version-matched Agent-Native framework docs and source bundled in node_modules. Use before implementing or answering questions about @agent-native/core APIs, generated apps, workspaces, templates, or advanced features.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-native-docs/SKILL.md

Quality

Content

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

A highly actionable, well-structured lookup skill dominated by concrete executable commands and a clear search-then-read workflow. Its main weakness is mild redundancy across sections plus a tangential final section that dilutes the doc-lookup focus.

Suggestions

Consolidate the 'version-matched installed source outranks memory' rationale into the Why section and reference it rather than restating it in Rule and Reuse Proven Patterns.

Move the 'Authoring visual docs blocks' section into a separate reference file or a different skill, since it is unrelated to looking up Agent-Native docs and source.

Make the workflow sequence explicit with numbered steps (unified search -> focused reader -> direct rg fallback) and a short note on when to stop refining a bounded search result.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and avoids explaining basics Claude already knows, but the 'version-matched installed source outranks web docs or memory' rationale is restated across the Rule, Why, and Reuse sections, and the closing 'Authoring visual docs blocks' section is tangential to a docs-lookup skill, so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready executable commands throughout — `pnpm action framework-search --pattern ...`, `rg -n ... node_modules/@agent-native/core/...`, and `cp .../archive-email.ts actions/archive-item.ts` — covering the common search, read, and reuse cases.	5 / 5
Workflow Clarity	There is a clear sequenced workflow (unified framework-search first, then focused readers, then a direct rg fallback when the runner is unavailable) with most steps explicit; because this is a read-only lookup rather than a destructive/batch operation, the validation-cap anchor does not apply, but explicit checkpoints are still only implicit.	4 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md carries everything; it is well-organized into clear sections (Rule, Why, How, Reuse Proven Patterns, Useful Slugs, Don't) with no nested references, though the off-topic 'Authoring visual docs blocks' section is inlined where separation would help.	4 / 5
	Total	16 / 20 Passed

Description

82%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 concise, third-person description that clearly states both what the skill does and when to use it, with strong trigger specificity for the Agent-Native niche. Its only weakness is listing a single find action rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the concrete domain and action — 'find version-matched Agent-Native framework docs and source bundled in node_modules' — but it is essentially a single find action rather than a comprehensive list of several distinct capabilities, so it sits at the 1-2 concrete actions anchor rather than the multi-action anchors above.	3 / 5
Completeness	It explicitly answers both 'what' ('find version-matched Agent-Native framework docs and source bundled in node_modules') and 'when' with a concrete trigger clause ('Use before implementing or answering questions about @agent-native/core APIs...'), matching the anchor for clear what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	Includes natural framework-specific terms a user would say — '@agent-native/core APIs, generated apps, workspaces, templates' — giving good keyword coverage, though a few common synonyms or extension variants are absent.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (version-matched Agent-Native docs/source lookup in node_modules) with distinct triggers tied to the named framework, so overlap with other skills is minimal.	5 / 5
	Total	17 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
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
Path: .agents/skills/agent-native-docs/SKILL.md
Commit: cc2a915

Reviewed: 3 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.