CtrlK
BlogDocsLog inGet started
Tessl Logo

android-navigation-type-safe

Implement type-safe Jetpack Navigation Compose routes using Kotlin serialization. Use only when defining typed Compose destinations and arguments; defer XML navigation, deep links, animations, and generic auth or bottom-navigation work.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-organized, concise, and actionable with a verified single-level reference; it reads as an effective standards skill. The main improvement is removing minor redundancy between the Implementation Guidelines, Anti-Patterns, and Required route example sections.

Suggestions

Dedupe the 'No String Routes' guidance so it appears once (either Implementation Guidelines or Anti-Patterns) rather than restated across sections.

Fold the 'Required route example' into the Type-Safe Navigation section or the reference file so the canonical pattern lives in one place.

Add a one-line inline NavHost wiring snippet (or point explicitly to the NavHost Setup section of implementation.md) so the main pattern is executable from SKILL.md alone.

DimensionReasoningScore

Conciseness

The body is lean with no padding explaining Compose or navigation basics, but 'No String Routes' is restated across Implementation Guidelines and Anti-Patterns and the 'Required route example' overlaps prior sections, so minor trimming is possible below a 5.

4 / 5

Actionability

Provides concrete executable rules (use @Serializable objects/classes, .toRoute<T>(), hoist to callbacks, library 2.8.0+) plus a concrete ProductDetail example, but lacks a full inline copy-paste NavHost setup (delegated to references), leaving minor gaps versus anchor 5.

4 / 5

Workflow Clarity

This is a standards skill with no destructive or batch operations, so the simple-skill exception applies; the 'Required route example' gives an unambiguous pattern, but no explicit multi-step sequence or checkpoints keeps it at 4 rather than 5.

4 / 5

Progressive Disclosure

The body is a concise overview with a single, clearly signaled one-level-deep reference to references/implementation.md (verified to exist), matching the anchor for a well-organized, easy-to-navigate sub-50-line skill.

5 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it names a precise domain, gives concrete actions, and explicitly bounds when to use the skill with both positive and negative triggers. Minor room to sharpen the action list, but completeness and distinctiveness are excellent.

DimensionReasoningScore

Specificity

Names the domain (type-safe Jetpack Navigation Compose routes, Kotlin serialization) and several concrete actions (define typed destinations/arguments, defer XML nav/deep links/animations/auth/bottom-nav); slightly boundary-oriented rather than a pure action list, so below 5.

4 / 5

Completeness

Clearly states what ('Implement type-safe Jetpack Navigation Compose routes using Kotlin serialization') and an explicit 'Use only when defining typed Compose destinations and arguments' trigger, matching the anchor for explicit what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

Includes natural developer terms like 'Jetpack Navigation Compose', 'Kotlin serialization', 'typed Compose destinations and arguments', and 'deep links'; good coverage with a few natural synonyms missing, fitting anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (type-safe Navigation Compose) reinforced by explicit deferral of XML navigation, deep links, animations, auth, and bottom-nav, giving a distinct trigger set with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.