CtrlK
BlogDocsLog inGet started
Tessl Logo

native-navigation

Use when adding or reviewing UI navigation so internal routes preserve normal SPA behavior plus Cmd/Ctrl-click and middle-click new-tab semantics.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

An exemplary compact skill: lean, executable, with a sequenced review workflow including verification checkpoints and clean section organization needing no bundle files.

DimensionReasoningScore

Conciseness

The body is lean across Rule/Why/How/Review with no padded concept explanations; even the brief 'Why' frames the rule rather than lecturing, and every section earns its tokens.

3 / 3

Actionability

Provides copy-paste-ready TSX (Link, Button asChild, <a> with rel='noopener noreferrer') plus concrete review search strings and exact verification commands (oxfmt, focused tests/typechecks).

3 / 3

Workflow Clarity

The Review section sequences the work — search candidates, 'confirm whether it is pure navigation or a stateful workflow before changing it', verify the DOM exposes an href across click variants, then run oxfmt and tests — with explicit checkpoints.

3 / 3

Progressive Disclosure

A sub-50-line single-purpose skill with no external references and well-organized sections (Rule/Why/How/Review/Related Skills); the sibling-skill pointers aid navigation without nested references.

3 / 3

Total

12

/

12

Passed

Description

85%

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 tight, well-targeted description with an explicit trigger and concrete preserved behaviors; its only weakness is slightly technical phrasing and missing natural synonyms in the trigger terms.

Suggestions

Add plain-language synonyms users actually say, e.g. 'links', 'open in new tab', or 'React Router', alongside the current technical terms.

Soften jargon like 'SPA behavior' and 'new-tab semantics' toward phrasing a developer would naturally request.

Consider naming the review angle ('reviewing UI navigation') more concretely, e.g. 'auditing navigation calls for hidden destinations'.

DimensionReasoningScore

Specificity

Names multiple concrete actions/behaviors — 'adding or reviewing UI navigation' and preserving 'normal SPA behavior plus Cmd/Ctrl-click and middle-click new-tab semantics' — rather than vague abstractions.

3 / 3

Completeness

Opens with an explicit 'Use when...' trigger and states the goal (preserving SPA + modifier/middle-click semantics), clearly answering both what and when.

3 / 3

Trigger Term Quality

Includes relevant terms like 'UI navigation', 'Cmd/Ctrl-click', and 'middle-click', but leans technical ('SPA behavior', 'new-tab semantics') and omits common natural variations such as 'link', 'router', or 'open in new tab'.

2 / 3

Distinctiveness Conflict Risk

The modifier-click/new-tab navigation niche is specific and unlikely to fire for unrelated skills, with triggers distinct from generic routing or styling skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

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.