Implement navigation with Jetpack Compose Navigation and App Links on Android. Use when implementing navigation flows, deep links, or backstack handling.
55
63%
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-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 technology niche (Jetpack Compose Navigation, App Links, Android) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the capability description could be more specific about the concrete actions it performs beyond the general categories of navigation flows, deep links, and backstack handling.
Suggestions
Expand the 'what' portion with more concrete actions, e.g., 'Set up NavHost and route definitions, configure route arguments, handle nested navigation graphs, implement App Links for deep linking, and manage backstack behavior.'
| 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 'set up NavHost', 'configure route arguments', 'handle nested navigation graphs'. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement navigation with Jetpack Compose Navigation and App Links on Android) and 'when' (Use when implementing navigation flows, deep links, or backstack handling) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Jetpack Compose Navigation', 'App Links', 'navigation flows', 'deep links', 'backstack handling', 'Android'. These are terms developers naturally use when seeking help with this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining Jetpack Compose Navigation + App Links + Android. Unlikely to conflict with other skills due to the specific technology stack mentioned. Clear triggers distinguish it from general Android or general navigation 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 admirably concise and avoids explaining concepts Claude already knows, but it critically lacks actionability — there are no code examples for route definitions, NavHost setup, or Manifest configuration. The workflow for implementing navigation is not sequenced, and the referenced navigation-patterns.md file is missing from the bundle, leaving the skill incomplete.
Suggestions
Add executable code examples: a sealed class route definition, a minimal NavHost setup with composable destinations, and a Manifest intent-filter XML snippet for deep links.
Provide a sequenced workflow: 1) Define routes as sealed classes, 2) Set up NavHost, 3) Configure Manifest intent-filters, 4) Verify deep links with `adb shell am start -a android.intent.action.VIEW -d <url>`, 5) Validate arguments before rendering.
Include the referenced navigation-patterns.md in the bundle, or inline the most critical patterns if the file doesn't exist.
Add a concrete deep link validation/testing step (e.g., adb command to test deep link resolution) to serve as a feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Jetpack Compose Navigation is or how Android navigation works conceptually. Every bullet point adds specific, non-obvious guidance (sealed classes for routes, autoVerify=true, validation before rendering). | 3 / 3 |
Actionability | There are no concrete code examples, no executable snippets showing sealed class route definitions, no NavHost setup code, no Manifest XML for intent-filters. The guidance is entirely descriptive ('use sealed classes', 'configure intent-filter') without showing how. | 1 / 3 |
Workflow Clarity | Navigation implementation is a multi-step process (define routes, set up NavHost, configure Manifest, handle deep links, validate arguments) but no sequenced workflow is provided. There are no validation checkpoints or feedback loops for verifying deep link configuration works correctly. | 1 / 3 |
Progressive Disclosure | The skill references a separate file (references/navigation-patterns.md) which is good structure, but no bundle files are provided so the reference is unverifiable. The main content is appropriately brief for an overview, but the lack of the referenced file means the skill is incomplete as-is. | 2 / 3 |
Total | 7 / 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 | |
556618c
Table of Contents
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.