android-legacy-navigation
Implement Jetpack Navigation Component with XML graphs and SafeArgs for type-safe fragment navigation. Use when working with XML-based Navigation Component or SafeArgs in Android. (triggers: navigation/*.xml, findNavController, NavDirections, navArgs)
83
78%
Does it follow best practices?
Impact
Pending
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
100%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 an excellent skill description that clearly defines its scope (Jetpack Navigation Component with XML graphs and SafeArgs), provides explicit 'Use when' guidance, and includes highly specific trigger terms that match real developer usage patterns. It is concise, uses third-person voice, and would be easily distinguishable from other Android-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Implement Jetpack Navigation Component with XML graphs and SafeArgs for type-safe fragment navigation.' This names the specific technology (Jetpack Navigation Component), the format (XML graphs), the plugin (SafeArgs), and the purpose (type-safe fragment navigation). | 3 / 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 Component or SafeArgs in Android), plus provides explicit trigger terms in parentheses. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that developers would actually use: 'navigation/*.xml', 'findNavController', 'NavDirections', 'navArgs', 'SafeArgs', 'Navigation Component'. These cover file patterns, API calls, and class names a developer would encounter or mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: XML-based Jetpack Navigation with SafeArgs. The specific trigger terms like 'findNavController', 'NavDirections', and 'navArgs' are unique to this Android navigation pattern and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%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 with good progressive disclosure to a reference file, but it critically lacks actionability—there are no concrete code examples, commands, or copy-paste-ready snippets in the main skill file itself. The overview reads more like a table of contents with guidelines than an actionable skill, relying entirely on the reference file for any executable guidance.
Suggestions
Add at least one inline executable code example for each major section (e.g., a minimal NavHostFragment XML setup, a SafeArgs navigation call in Kotlin) so the skill is actionable even without reading the reference file.
Include a concrete SafeArgs plugin setup snippet (build.gradle configuration) since 'Enable SafeArgs plugin — MANDATORY' is vague without showing the actual dependency and plugin application.
Add a brief validation step, such as 'Build the project after enabling SafeArgs to verify generated Directions classes are created' to improve 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 provides actionable guidance or constraints. | 3 / 3 |
Actionability | The skill contains no concrete code, commands, or executable examples. It describes what to do ('Use one Host Activity with NavHostFragment', 'Enable SafeArgs plugin') but delegates all actual implementation details to a reference file without providing any inline code snippets. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (set up architecture → manage graphs → navigate with SafeArgs) and anti-patterns are called out, but there are no validation checkpoints or feedback loops for verifying correct setup, and the steps lack specificity. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled, one-level-deep references to the implementation details file. Content is appropriately split between the overview and the reference document. | 3 / 3 |
Total | 9 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.