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.
77
73%
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-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 full scope of what the skill covers.
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 UI skills, general Kotlin skills, or other navigation approaches. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, with good progressive disclosure via a reference file. However, it critically lacks actionable, executable code examples—no route definition snippet, no NavHost setup, no example of .toRoute<T>() usage. This makes it more of a style guide summary than a skill Claude can directly execute from.
Suggestions
Add at least one complete, executable code example showing a @Serializable route definition, NavHost setup, and composable navigation with type-safe arguments.
Include a concrete example of the anti-pattern vs. correct pattern (e.g., String route vs. @Serializable object) to make the guidance immediately actionable.
Add a brief step-by-step workflow for setting up type-safe navigation in a new feature module (define routes → build NavHost → wire callbacks).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line conveys a specific rule or constraint without explaining what Jetpack Compose or Kotlin serialization is. No unnecessary padding. | 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 how these look in practice. | 1 / 3 |
Workflow Clarity | The skill outlines structural guidelines (split into nested graphs, hoist navigation events) and anti-patterns, but there is no sequenced workflow for implementing navigation, no validation steps, and no feedback loop for verifying correctness. | 2 / 3 |
Progressive Disclosure | The content is a concise overview with a clear one-level-deep reference to 'references/implementation.md' for route definitions. The structure is well-organized with distinct sections. | 3 / 3 |
Total | 9 / 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.