android-navigation
Implement navigation with Jetpack Compose Navigation and App Links on Android. Use when implementing navigation flows, deep links, or backstack handling in Android. (triggers: **/*Screen.kt, **/*Activity.kt, **/NavGraph.kt, NavController, NavHost, composable, navArgument, deepLinks)
71
63%
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-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 strong skill description that clearly identifies its niche (Jetpack Compose Navigation on Android), provides explicit 'Use when' guidance, and includes excellent file-pattern and code-level trigger terms. The main weakness is that the capability description could be more specific about the concrete actions it performs beyond the general 'implement navigation flows, deep links, or backstack handling'.
Suggestions
Expand the capability list with more specific actions, e.g., 'Define navigation routes, pass arguments between screens, configure deep links and App Links, manage backstack behavior, set up nested navigation graphs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jetpack Compose Navigation, App Links, Android) and some actions (navigation flows, deep links, backstack handling), but doesn't list multiple concrete actions like 'define routes, pass arguments, handle deep links, manage backstack'. It's more of a domain statement than a list of specific capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement navigation with Jetpack Compose Navigation and App Links on Android) and 'when' (when implementing navigation flows, deep links, or backstack handling in Android), with an explicit 'Use when' clause and file/code triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including file patterns (*Screen.kt, *Activity.kt, NavGraph.kt) and code-level keywords (NavController, NavHost, composable, navArgument, deepLinks). These are terms a developer would naturally use or have in their codebase when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Android Jetpack Compose Navigation specifically. The combination of Android-specific file patterns and Compose Navigation API terms makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise but severely lacks actionability—it reads as a checklist of principles rather than executable guidance. There are no code examples for route definitions, NavHost setup, deep link configuration, or argument validation, which are the core tasks this skill should teach. The workflow is absent, making it difficult for Claude to follow a clear implementation path.
Suggestions
Add executable code examples: a sealed class route definition, a NavHost setup with composable destinations, and a deep link configuration in both Kotlin and AndroidManifest.xml.
Include a step-by-step workflow for implementing navigation: 1) Define routes, 2) Set up NavHost, 3) Configure deep links in Manifest, 4) Validate by testing navigation and deep link resolution.
Add a concrete example of argument validation (e.g., checking a navArgument ID before loading content) to make the validation guideline actionable.
Expand the references/navigation-patterns.md link with a brief description of what it contains so Claude knows when to consult it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations of what Jetpack Compose Navigation is or how Android works. Every line provides specific, actionable guidance. | 3 / 3 |
Actionability | The skill provides only abstract guidelines and anti-patterns with no executable code examples. There are no concrete code snippets showing sealed class route definitions, NavHost setup, deep link configuration, or argument validation—just vague directives like 'use sealed classes for routes.' | 1 / 3 |
Workflow Clarity | There is no sequenced workflow for implementing navigation. The skill lists guidelines and anti-patterns but doesn't describe a step-by-step process for setting up navigation, configuring deep links, or validating the setup. No validation checkpoints are provided. | 1 / 3 |
Progressive Disclosure | The skill references a separate file (references/navigation-patterns.md) which is good, but the main content is too thin to serve as a useful overview. The reference is one-level deep and clearly signaled, but the lack of substantive quick-start content weakens the structure. | 2 / 3 |
Total | 7 / 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.