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.
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/android/android-legacy-navigation/SKILL.mdQuality
Discovery
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 specificity of concrete actions could be improved by listing more distinct operations beyond just 'implement'. Overall it performs well for skill selection purposes.
Suggestions
Expand the concrete actions listed, e.g., 'Create navigation graphs, define destinations, pass typed arguments between fragments, handle deep links' to improve specificity.
| 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 feature. | 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 |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, correctly assuming Claude's knowledge of Android development concepts. However, it over-relies on a reference file (`references/implementation.md`) that is not present in the bundle, leaving the skill without any concrete code examples or executable guidance in either the main file or supporting materials. Adding inline code snippets or ensuring the referenced file exists would significantly improve actionability.
Suggestions
Add at least one inline executable code example (e.g., NavHostFragment XML setup or SafeArgs navigation call) so the skill is actionable even without the reference file.
Include the `references/implementation.md` file in the bundle, or inline its critical content, since the skill delegates most concrete guidance there.
Add a validation step such as 'Build the project to verify SafeArgs classes are generated under `build/generated/source/navigation-args/`' to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Navigation Component, SafeArgs, or fragments are—concepts Claude already knows. Every section adds specific, non-obvious guidance (e.g., use deep links in graph not manifest, no manual fragment commit). | 3 / 3 |
Actionability | The skill provides clear directives (use SafeArgs, use NavController, nested graphs) but lacks any inline executable code or concrete examples. All implementation details are deferred to a reference file that doesn't exist in the bundle, leaving the main skill without copy-paste ready guidance. | 2 / 3 |
Workflow Clarity | The numbered sections imply a sequence (set up architecture → manage graphs → navigate with SafeArgs), but there are no validation checkpoints or verification steps. For a setup workflow involving build configuration and XML graph creation, explicit validation (e.g., build and verify SafeArgs classes generated) would be expected. | 2 / 3 |
Progressive Disclosure | The skill references `references/implementation.md` appropriately and keeps the overview concise, which is good structure. However, the referenced file is not present in the bundle, making the progressive disclosure non-functional. The references are one-level deep and clearly signaled, but without the actual bundle file, the navigation promise is broken. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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
3df717f
- 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.