CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

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.

An exemplary lean lookup skill: fully executable commands, a clear sequenced workflow with fallback branches, and a useful slug index, all within ~45 lines with zero padding. The only minor gap is the absence of a validation checkpoint for confirming that retrieved docs match the installed framework version.

DimensionReasoningScore

Conciseness

The body is lean and operational — "Before implementing non-trivial Agent-Native functionality, read the version-matched docs installed with `@agent-native/core`" — with no concept explanations and every section carrying executable guidance. Every token earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: `pnpm action framework-search --pattern "<feature>"`, `pnpm action docs-search --slug <slug>`, `pnpm add -D @agent-native/core-corpus@<installed-core-version>`, plus concrete `rg` fallbacks. Placeholders like `<feature>` are appropriately parameterized, and the Useful Slugs table maps common needs to real slugs.

5 / 5

Workflow Clarity

A clear 7-step sequence with error-recovery fallbacks ("If it reports that template source is unavailable, install the matching corpus package"; "If the action runner is unavailable, search ... directly with `rg`"). It stops short of anchor 5 because there is no validation checkpoint confirming the found docs match the installed version or that a search returned the relevant result.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and is well-organized into Rule / How / Useful Slugs / Don't sections; the slug table functions as an in-skill index to the docs corpus. Per the rubric's simple-skill exception, well-organized sections without external references merit a 5.

5 / 5

Total

19

/

20

Passed

Description

73%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 with a clear what-and-when structure and strong distinctiveness. Its main weakness is limited action coverage — it names only two actions — and trigger phrasing that could include more natural synonyms like "documentation" or "API reference".

Suggestions

List the concrete lookup capabilities in the description (e.g., cross-corpus framework search, docs-search by slug, source-search) to raise specificity from 1-2 actions to several specific actions.

Add natural trigger synonyms such as "documentation", "API reference", or "source code" so users phrasing the need differently still match the skill.

DimensionReasoningScore

Specificity

"look up version-matched Agent-Native framework docs and source in node_modules" names the domain and two concrete actions (docs lookup, source lookup), matching the 1-2-concrete-actions anchor. It does not list several specific actions (e.g., framework/docs/source search or slug navigation), so it falls short of anchor 4.

3 / 5

Completeness

Explicitly answers what ("How to look up version-matched Agent-Native framework docs and source in node_modules") and when ("Use before coding against @agent-native/core APIs or advanced features"). The when-clause's "or advanced features" portion is vague, so it doesn't fully meet the concrete-trigger-phrases bar of anchor 5.

4 / 5

Trigger Term Quality

Includes natural terms like "docs", "source", "node_modules", "APIs", and the package name "@agent-native/core" that a framework user would naturally say. Missing common variations such as "documentation", "API reference", or "look up", keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to the @agent-native/core framework with distinct triggers ("@agent-native/core APIs", "Agent-Native framework docs"), giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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