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?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/android-jetpack-compose-expert/SKILL.md

Quality

Discovery

32%

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 a clear technology domain (Jetpack Compose) and lists relevant topic areas, but it reads more like a course syllabus than an actionable skill description. It lacks concrete actions, a 'Use when...' clause, and sufficient trigger term coverage to reliably distinguish it in a large skill library.

Suggestions

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

Replace 'Expert guidance' with specific concrete actions, e.g., 'Build composable UI components, implement Compose navigation, manage UI state with remember/ViewModel, optimize recomposition performance, and apply Material Design 3 theming.'

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

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 the skill 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', which users might naturally mention. However, it misses common variations like 'Compose UI', 'composable', 'recomposition', 'LazyColumn', 'ViewModel', or 'Kotlin UI'.	2 / 3
Distinctiveness Conflict Risk	Jetpack Compose is a fairly specific technology, which helps distinguish it from generic Android or UI skills. However, the broad terms like 'navigation' and 'state management' could overlap with other Android or general UI framework skills.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

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 excellent code examples that are immediately usable. Its main weaknesses are moderate verbosity (boilerplate explanations, version-specific dependency blocks) and lack of validation checkpoints in the workflow. The content would benefit from trimming unnecessary framing, adding build/preview verification steps, and splitting detailed topics into referenced files.

Suggestions

Remove the 'When to Use This Skill' section and the generic 'Limitations' boilerplate — these are obvious and waste tokens.

Add validation checkpoints after key steps, e.g., 'Build and verify the project compiles' after setup, 'Use Layout Inspector to confirm recomposition counts' after creating composables.

Move the version catalog TOML block and detailed navigation example into separate referenced files (e.g., SETUP.md, NAVIGATION.md) to keep the main skill lean.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary framing ('comprehensive guide', 'When to Use This Skill' section with obvious items) and the version catalog setup is verbose boilerplate Claude doesn't need. However, the code examples themselves are reasonably tight and the best practices section is efficient with its do/don't format.	2 / 3
Actionability	The skill provides fully executable, copy-paste-ready Kotlin code for state management, screen composables, and type-safe navigation. The ViewModel pattern, UI state definition, and NavHost setup are all concrete and complete enough to use directly.	3 / 3
Workflow Clarity	Steps are listed (Setup → State Management → Screen Composable → Navigation) but there are no validation checkpoints. For a multi-step process involving project setup and architecture, there's no guidance on verifying each step works before proceeding (e.g., build verification, preview testing). The troubleshooting section partially compensates but lacks explicit feedback loops.	2 / 3
Progressive Disclosure	The content is a monolithic single file with no references to supporting documents. At ~120 lines with multiple distinct topics (setup, state management, navigation, performance, troubleshooting), some content like the version catalog or detailed navigation examples could be split into referenced files. However, the sections are well-organized with clear headers.	2 / 3
	Total	9 / 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: sickn33/antigravity-awesome-skills
Commit: 22710e9

Reviewed: about 21 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.