android-jetpack-compose-expert

Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.

1.06x

Quality

68%

Does it follow best practices?

Impact

81%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/android-jetpack-compose-expert/SKILL.md

The canonical home for this skill is android-jetpack-compose-expert in sickn33/agentic-awesome-skills

Quality

Content

75%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 body is well-structured with mostly copy-paste-ready Kotlin code, a clear numbered workflow, and a troubleshooting feedback loop. It loses points for a few undefined helper composables and minor over-explanation in the intro.

Suggestions

Define or briefly stub the referenced helper composables (ErrorView, UserProfile, HomeScreen, ProfileScreen) so examples are fully copy-pasteable.

Trim the Overview marketing language ('comprehensive guide', 'production-quality') to leaner factual framing.

Consider a short 'Prerequisites' note for Hilt setup since hiltViewModel() is used without showing the DI configuration.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with brief framing, and only minor marketing fluff ('A comprehensive guide for building production-quality Android applications...') could be trimmed, fitting 'efficient; minor instances of over-explanation' rather than the fully-lean anchor 5.	4 / 5
Actionability	Concrete, executable Kotlin is provided for dependencies, ViewModel/StateFlow, screen composables, and type-safe navigation, but helper composables (ErrorView, UserProfile, HomeScreen, ProfileScreen) and Hilt setup are referenced without being defined, leaving minor gaps that fit 'mostly executable; minor gaps' instead of 5.	4 / 5
Workflow Clarity	The numbered Step-by-Step Guide gives a clear setup → state → screen sequence and the Troubleshooting section provides an error-recovery loop; no destructive/batch validation cap applies, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist, but the single-file content is well-organized into Overview, When to Use, Step-by-Step, Examples, Best Practices, and Troubleshooting sections; this self-contained structure fits 'good structure; minor organization gaps' rather than 5, which requires explicit one-level-deep references.	4 / 5
	Total	16 / 20 Passed

Description

61%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 clearly identifies its Compose niche with good trigger keywords, but lacks an explicit 'Use when...' trigger clause and frames its scope as covered topics rather than concrete actions.

Suggestions

Add an explicit 'Use when...' clause listing concrete trigger scenarios (e.g., 'Use when building or migrating Android UIs to Jetpack Compose, managing UI state, or setting up type-safe navigation').

Reframe the topic list as concrete actions (e.g., 'Build, migrate, and optimize Jetpack Compose UIs') to lift specificity above a topics-coverage phrasing.

Include natural synonyms such as 'Compose UI' or 'Compose navigation' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('building modern Android UIs with Jetpack Compose') and lists covered areas (state management, navigation, performance, Material Design 3), but these are topics under 'covering' rather than concrete actions, so it sits at the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the multi-action anchor 4.	3 / 5
Completeness	A clear 'what' is stated but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3 and matches the 'clear what, when missing' anchor.	3 / 5
Trigger Term Quality	Natural user-facing terms like 'Jetpack Compose', 'Android UIs', 'navigation', and 'Material Design 3' are present, matching 'good keyword coverage; a few natural terms missing'; synonyms such as 'Compose UI' are absent, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	The Jetpack Compose niche is specific and distinct, but the skill spans many general Android topics so it has minor overlap risk with closely related Android development skills, fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/android-jetpack-compose-expert/SKILL.md
Commit: 900c504

Reviewed: 2 hours ago

Table of Contents

Discovery Implementation Validation

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.