android-navigation-type-safe
Implement type-safe Jetpack Navigation Compose routes on Android. Use when implementing type-safe navigation graphs in Jetpack Compose for Android. (triggers: **/*NavHost.kt, **/*Graph.kt, NavHost, navController, @Serializable)
85
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 with excellent trigger terms, clear 'when' guidance, and a distinct niche. Its main weakness is that the 'what' portion is somewhat thin — it mentions implementing type-safe routes but doesn't enumerate specific sub-tasks like handling navigation arguments, nested graphs, or deep links.
Suggestions
Expand the capability list with more concrete actions, e.g., 'Define navigation routes with type-safe arguments, create nested navigation graphs, handle deep links, and manage back stack behavior.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jetpack Navigation Compose on Android) and one action ('implement type-safe routes'), but doesn't list multiple concrete actions like defining routes, handling arguments, creating nested graphs, or deep links. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement type-safe Jetpack Navigation Compose routes on Android) and 'when' (explicit 'Use when' clause plus file pattern and keyword triggers). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms that users and file patterns would match: 'NavHost', 'navController', '@Serializable', file globs like '**/*NavHost.kt' and '**/*Graph.kt', plus domain terms like 'type-safe navigation', 'Jetpack Compose', 'Android'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting type-safe Jetpack Navigation Compose on Android with distinct file patterns and keywords like NavHost, navController, and @Serializable — unlikely to conflict with other skills. | 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 concise, well-structured skill that efficiently communicates Android navigation conventions without over-explaining. Its main weakness is the lack of concrete, executable code examples — a type-safe route definition snippet and a NavHost wiring example would significantly improve actionability. The workflow could also benefit from a brief sequenced process for implementing navigation.
Suggestions
Add a concrete code example showing a @Serializable route definition and its usage in a NavHost composable block (e.g., composable<MyRoute> { ... })
Include a brief step-by-step workflow: 1. Define @Serializable route objects, 2. Build NavHost with typed composable blocks, 3. Hoist navigation callbacks from screens
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. Every line adds value, no unnecessary explanations of what Jetpack Compose or Navigation is. Assumes Claude knows Android development and only provides the specific conventions to follow. | 3 / 3 |
Actionability | Provides specific guidance (use @Serializable, use .toRoute<T>(), Navigation Compose 2.8.0+) but lacks executable code examples. A concrete code snippet showing a type-safe route definition and NavHost setup would make this fully actionable. | 2 / 3 |
Workflow Clarity | The structure and anti-patterns sections provide clear guidance on what to do and what to avoid, but there's no sequenced workflow for implementing navigation. For a skill about implementing navigation graphs, a step-by-step process (define routes → build NavHost → wire callbacks) would improve clarity. | 2 / 3 |
Progressive Disclosure | Clean overview with a single well-signaled reference to implementation details. The SKILL.md stays concise as an overview and delegates detailed route definitions to a separate reference file, exactly one level deep. | 3 / 3 |
Total | 10 / 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.