android-navigation-type-safe
Implement type-safe Jetpack Navigation Compose routes using Kotlin serialization. Use when defining navigation graphs with type-safe destinations in Jetpack Compose.
59
70%
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-type-safe/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, focused description that clearly identifies a specific technical niche (type-safe Jetpack Navigation Compose with Kotlin serialization) and includes an explicit 'Use when' clause. Its main weakness is that it could list more concrete actions beyond just 'implement routes' to better convey the breadth of what the skill covers. The trigger terms are well-chosen for the target developer audience.
Suggestions
Expand the 'what' portion with additional concrete actions, e.g., 'define route arguments, handle nested navigation graphs, pass typed parameters between screens' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Jetpack Navigation Compose) and one action ('implement type-safe routes using Kotlin serialization'), but doesn't list multiple concrete actions like defining arguments, handling deep links, creating nested graphs, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement type-safe Jetpack Navigation Compose routes using Kotlin serialization) and 'when' (Use when defining navigation graphs with type-safe destinations in Jetpack Compose), with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Jetpack Navigation Compose', 'type-safe', 'Kotlin serialization', 'navigation graphs', 'type-safe destinations', 'Jetpack Compose'. These are terms developers naturally use when working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Jetpack Navigation Compose, type-safe routes, and Kotlin serialization. Unlikely to conflict with general Compose skills, general Kotlin skills, or other navigation approaches. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%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 and well-structured as a high-level overview, but critically lacks executable code examples that would make it actionable. The anti-patterns section is useful but would benefit from showing correct implementations alongside the incorrect patterns. The referenced implementation file is not available in the bundle, undermining the progressive disclosure strategy.
Suggestions
Add concrete, executable Kotlin code examples showing a complete type-safe route definition with @Serializable, NavHost setup, and navigation call (e.g., `navController.navigate(ProfileRoute(userId = 123))`)
Include a before/after code example contrasting the anti-pattern (String routes) with the correct approach (@Serializable routes) to make the guidance immediately actionable
Provide the referenced `references/implementation.md` file in the bundle, or inline the essential route definition patterns if the file doesn't exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Jetpack Compose or Kotlin serialization are, assumes Claude's competence, and every bullet point conveys a distinct, non-obvious instruction. | 3 / 3 |
Actionability | There are no concrete code examples, no executable snippets, and no copy-paste ready patterns. The guidance is entirely descriptive ('Use @Serializable objects/classes', 'Use .toRoute<T>()') without showing actual implementation code. | 1 / 3 |
Workflow Clarity | The skill outlines structural guidelines (split into nested graphs, hoist navigation events) and anti-patterns, providing a reasonable sequence of concerns. However, there is no step-by-step workflow for implementing navigation, and no validation or verification steps. | 2 / 3 |
Progressive Disclosure | There is a reference to 'references/implementation.md' which suggests progressive disclosure, but no bundle files were provided to verify the reference exists. The main content is appropriately brief for an overview, but with only one reference and no bundle to back it up, the navigation structure is incomplete. | 2 / 3 |
Total | 8 / 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
3df717f
- 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.