CtrlK
BlogDocsLog inGet started
Tessl Logo

android-legacy-navigation

Implement Jetpack Navigation Component with XML graphs and SafeArgs for type-safe fragment navigation. Use when working with XML-based navigation or SafeArgs in legacy Android projects; defer drawer and other UI-chrome work to UI skills.

66

Quality

81%

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

80%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 well-structured, token-efficient body that defers executable detail to a single clearly signaled reference. The main gap is the absence of validation/feedback steps for the XML nav-graph editing workflow.

Suggestions

Add an explicit validation checkpoint (e.g., build the project and confirm SafeArgs generated classes compile, or verify the nav graph resolves in Android Studio's Navigation Editor) after graph edits.

Include one inline minimal SafeArgs Gradle snippet so the most critical setup step is executable without opening the reference.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven with no concept over-explanation; it assumes Claude's competence and lets concrete class/file names carry the meaning, so every token earns its place.

5 / 5

Actionability

Guidance is concrete and actionable (NavHostFragment, nav_auth.xml, <deepLink>, SafeArgs plugin) with executable code one reference away, but the body itself contains no inline copy-paste code, leaving a minor gap.

4 / 5

Workflow Clarity

A clear numbered sequence exists (set up architecture, manage graphs, navigate with SafeArgs) but there are no validation or verification checkpoints for the XML graph manipulation, which caps the score.

3 / 5

Progressive Disclosure

SKILL.md is a concise overview that points to one real, one-level-deep reference (references/implementation.md, which exists) via clearly signaled links and a References section, making navigation easy.

5 / 5

Total

17

/

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 strong, niche-scoped description with explicit what/when guidance and helpful boundary deferral. Its main weakness is specificity, where a single governing verb keeps it from listing multiple distinct concrete actions.

Suggestions

Expand the capability list into multiple distinct verbs (e.g., "Build XML nav graphs, wire SafeArgs, set up deep links, and navigate between fragments") to lift specificity.

Add a couple of natural synonyms or file markers (e.g., "navgraph XML", ".xml nav graphs") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and a couple concrete mechanisms ("XML graphs", "SafeArgs", "type-safe fragment navigation") but they sit under a single verb ("Implement") rather than a list of distinct actions, so coverage is not comprehensive.

3 / 5

Completeness

It explicitly states both what ("Implement Jetpack Navigation Component with XML graphs and SafeArgs for type-safe fragment navigation") and when ("Use when working with XML-based navigation or SafeArgs in legacy Android projects") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"XML-based navigation", "SafeArgs", and "legacy Android projects" are natural terms a developer would say, giving good keyword coverage, though common synonyms or file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (XML/SafeArgs legacy Android navigation) and explicitly defers drawer/UI-chrome work to other skills, minimizing overlap with sibling skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

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