CtrlK
BlogDocsLog inGet started
Tessl Logo

react-navigation

Provides React Navigation UI patterns for stacks, tabs, drawers etc. Use when building navigation UIs with React Navigation, configuring headers, bottom sheets or handling safe areas and insets.

71

Quality

86%

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

86%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 an exemplary dispatcher: lean, well-structured, and pointing to eight verified one-level-deep references with a clear problem->skill map. Its only limitation is that it offers no inline executable patterns, relying entirely on the references for actionable detail.

DimensionReasoningScore

Conciseness

The body is lean overview content with no concept-explanation padding or library tutorials; every section earns its place, and the React Navigation 7 version note is justified time-sensitive guidance rather than fluff.

5 / 5

Actionability

Provides concrete, actionable routing via the problem->skill mapping and an explicit API-selection branch (existing vs new apps), but the body itself contains no inline executable code or config examples, delegating all patterns to the references.

4 / 5

Workflow Clarity

The API-selection branch and problem->skill table form an unambiguous decision/dispatch flow, but there is no multi-step validated workflow; as a dispatcher skill this is clear, just short of an explicit checkpointed sequence.

4 / 5

Progressive Disclosure

Clear overview with two well-organized tables and eight one-level-deep references, all of which are real files verified in references/; navigation is easy and nothing is deeply nested.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong: it pairs a clear statement of capability with explicit, natural trigger conditions tied to a named library. Minor gaps in action granularity and trigger synonyms keep specificity and trigger quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Names the domain and enumerates several concrete capability areas (stacks, tabs, drawers, headers, bottom sheets, safe areas), but uses 'etc.' and lists capability areas rather than discrete actions, falling short of comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ('Provides React Navigation UI patterns for stacks, tabs, drawers etc.') and when ('Use when building navigation UIs with React Navigation, configuring headers, bottom sheets or handling safe areas and insets') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural developer terms ('navigation UIs', 'React Navigation', 'headers', 'bottom sheets', 'safe areas and insets') but misses a few common synonyms like 'router', 'screen', or 'tab bar'.

4 / 5

Distinctiveness Conflict Risk

Anchored to the specific named library 'React Navigation', giving it a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
callstackincubator/agent-skills
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.