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.

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/android/android-legacy-navigation/SKILL.md

Quality

Content

64%

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

This is a concise, well-structured skill that correctly assumes Claude's Android knowledge and avoids unnecessary explanation. Its main weaknesses are the lack of any inline executable code examples (everything is deferred to a missing reference file) and the absence of validation/verification steps in the workflow. The missing bundle file undermines the progressive disclosure strategy.

Suggestions

Add at least one inline code example (e.g., a minimal NavHostFragment XML setup or a SafeArgs navigation call) so the skill is actionable even without the reference file.

Include the referenced `references/implementation.md` file in the bundle to support the progressive disclosure structure.

Add a verification step such as 'Build the project to confirm SafeArgs classes are generated in the `build/generated/` directory' to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It avoids explaining what Navigation Component or SafeArgs are, assumes Claude's competence with Android development, and every line serves a purpose.	3 / 3
Actionability	The skill provides specific guidance (use NavHostFragment, use SafeArgs, modularize graphs) but lacks any executable code examples directly in the SKILL.md. All concrete implementation is deferred to a reference file that doesn't exist in the bundle.	2 / 3
Workflow Clarity	Steps are numbered and sequenced (set up architecture → manage graphs → navigate with SafeArgs), but there are no validation checkpoints or verification steps. For a setup-oriented skill, confirming the navigation graph compiles or SafeArgs classes generate correctly would strengthen the workflow.	2 / 3
Progressive Disclosure	The skill appropriately references a separate implementation file for detailed examples, keeping the overview concise. However, the referenced file (references/implementation.md) is not present in the bundle, making the progressive disclosure structure unverifiable and potentially broken.	2 / 3
	Total	9 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly identifies its niche (XML-based Jetpack Navigation with SafeArgs) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the capability listing could be more granular—enumerating specific actions like creating nav graphs, defining destinations, passing typed arguments, and handling deep links would strengthen it further.

Suggestions

Expand the capabilities list with more specific actions, e.g., 'create navigation graphs, define fragment destinations, pass typed arguments between fragments, handle deep links'

Dimension	Reasoning	Score
Specificity	Names the domain (Jetpack Navigation Component) and some actions (implement XML graphs, SafeArgs, type-safe fragment navigation), but doesn't list multiple distinct concrete actions like creating nav graphs, defining destinations, passing arguments, handling deep links, etc.	2 / 3
Completeness	Clearly answers 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 an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Jetpack Navigation', 'XML graphs', 'SafeArgs', 'type-safe', 'fragment navigation', 'legacy Android projects', 'XML-based navigation'. These cover the terms a developer would naturally use when seeking help with this specific Android pattern.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: XML-based Jetpack Navigation with SafeArgs in legacy Android projects. The specificity to XML graphs (vs Compose navigation) and SafeArgs makes it unlikely to conflict with other Android or navigation skills.	3 / 3
	Total	11 / 12 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 — 9 / 11 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

	Total	9 / 11 Passed

Repository: HoangNguyen0403/agent-skills-standard
Commit: de793e9

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