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.
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 discrete tasks (e.g., defining nav graphs, passing arguments between fragments, handling deep links). Overall it performs well for skill selection purposes.
Suggestions
Expand the 'what' portion with more specific actions, e.g., 'define navigation graphs, configure fragment destinations, pass type-safe 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 needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: XML-based Jetpack Navigation with SafeArgs in legacy Android projects. The mention of 'legacy' and 'XML-based' further distinguishes it from Compose Navigation or other Android navigation approaches, making conflicts unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that effectively serves as an overview document with appropriate progressive disclosure to a reference file. Its main weakness is the lack of any inline executable code or concrete examples—the reader must follow the reference link for all implementation details—and the absence of validation steps for verifying correct navigation setup.
Suggestions
Add at least one inline code snippet (e.g., a minimal NavHostFragment XML setup or a SafeArgs navigation call) so the skill is actionable without requiring the reference file.
Include a brief validation step, such as verifying navigation graph compilation or confirming SafeArgs classes are generated after build, to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Navigation Component or SafeArgs are. Every line provides actionable guidance or constraints without padding. | 3 / 3 |
Actionability | The skill provides clear directives (use NavHostFragment, use SafeArgs, avoid raw bundle keys) but lacks any inline executable code or concrete examples—all concrete implementation is deferred to the reference file. The anti-patterns are specific but the main instructions are directive rather than executable. | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced (set up architecture → manage graphs → navigate with SafeArgs), but there are no validation checkpoints or feedback loops for verifying correct setup, which matters for XML graph configuration that can silently fail. | 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 | 10 / 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
4c72e76
- 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.