android-jetpack-compose-expert

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

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/android-jetpack-compose-expert/SKILL.md

Quality

Content

64%Scale 1-3

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

This is a solid, actionable skill with high-quality executable Kotlin code examples covering key Compose patterns. Its main weaknesses are moderate verbosity (boilerplate sections, explanatory framing), lack of validation checkpoints in the workflow, and a monolithic structure that could benefit from splitting detailed topics into separate reference files. The code quality and pattern choices are excellent for production use.

Suggestions

Remove the boilerplate 'When to Use This Skill' and 'Limitations' sections, or condense them significantly—they add little value for Claude.

Add validation checkpoints to the workflow, e.g., 'Build and verify no compilation errors after adding dependencies' and 'Use Layout Inspector to confirm recomposition counts after implementing state management'.

Consider splitting detailed topics (navigation, performance/stability annotations, state management patterns) into separate referenced files to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary framing ('A comprehensive guide for building production-quality Android applications...'), the 'When to Use This Skill' section is somewhat redundant, and the Limitations section is boilerplate. The code examples themselves are well-targeted, but the surrounding prose could be tightened. The version catalog setup is borderline—Claude likely knows how to set up Compose dependencies.	2 / 3
Actionability	The skill provides fully executable, copy-paste-ready Kotlin code for state management (ViewModel + StateFlow), screen composables with state hoisting, and type-safe navigation. The examples are concrete, complete, and follow real-world patterns with Hilt injection and lifecycle-aware state collection.	3 / 3
Workflow Clarity	The steps are numbered and sequenced (setup → state management → screen composable → navigation), but there are no validation checkpoints. For a skill involving project setup and architecture, there's no mention of verifying the build compiles, running the app to confirm state flows correctly, or checking recomposition behavior. The troubleshooting section partially compensates but doesn't constitute explicit validation steps in the workflow.	2 / 3
Progressive Disclosure	The content is reasonably well-structured with clear sections, but it's monolithic—all content is inline with no references to external files. The performance optimization, navigation, and state management topics could each warrant their own reference files. Given no bundle files exist, there's no progressive disclosure structure to leverage.	2 / 3
	Total	9 / 12 Passed

Description

32%Scale 1-3

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 identifies its domain (Jetpack Compose for Android) and lists relevant topic areas, but it reads more like a course syllabus than an actionable skill description. It lacks concrete actions, explicit trigger conditions, and the 'Use when...' clause that would help Claude reliably select this skill from a large pool.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Jetpack Compose, building Android UIs, composable functions, or Material Design 3 components.'

Replace 'Expert guidance' with specific concrete actions, e.g., 'Creates composable UI components, implements navigation graphs, manages state with ViewModel and remember, optimizes recomposition performance.'

Include additional natural trigger terms users might say, such as 'Compose UI', 'composable', 'LazyColumn', 'recomposition', 'Kotlin UI', or 'Android UI toolkit'.

Dimension	Reasoning	Score
Specificity	Names the domain (Android UIs with Jetpack Compose) and lists topic areas (state management, navigation, performance, Material Design 3), but these are categories rather than concrete actions. It says 'Expert guidance' rather than listing specific actions like 'create composables, implement navigation graphs, optimize recomposition'.	2 / 3
Completeness	Describes what it covers at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also somewhat vague ('Expert guidance'), this falls to 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Android', 'Jetpack Compose', 'Material Design 3', 'state management', and 'navigation' that users might naturally mention. However, it misses common variations like 'Compose UI', 'composable functions', 'recomposition', 'LazyColumn', 'ViewModel', or file extensions like '.kt'.	2 / 3
Distinctiveness Conflict Risk	Specifying 'Jetpack Compose' and 'Material Design 3' provides some distinctiveness from generic Android or UI skills. However, terms like 'state management', 'navigation', and 'performance' are broad enough to overlap with other Android or general UI development skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: popey/claude-code-skills
Path: skills/android-jetpack-compose-expert/SKILL.md
Commit: a5a6601

Reviewed: 5 days 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.