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

48%

Does it follow best practices?

Impact

81%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-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 technical domain (Jetpack Compose for Android) and lists relevant topic areas, but lacks concrete action verbs and explicit trigger guidance. The absence of a 'Use when...' clause significantly weakens Claude's ability to know when to select this skill over other Android or UI-related skills.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when building Android UIs, working with @Composable functions, implementing Compose navigation, or asking about recomposition and state hoisting.'

Replace category nouns with concrete actions: 'Create composable functions, implement navigation graphs, optimize recomposition, apply Material Design 3 theming.'

Include additional natural trigger terms users might say: 'Compose UI', 'Kotlin UI', 'Android app interface', 'LazyColumn', 'remember', 'mutableStateOf'.

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 like 'create composables' or 'implement navigation graphs'.	2 / 3
Completeness	Describes what the skill covers (Jetpack Compose guidance) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Jetpack Compose', 'Android', 'Material Design 3', but misses common user variations like 'Compose UI', 'Android app', 'Kotlin UI', '@Composable', or 'recomposition'.	2 / 3
Distinctiveness Conflict Risk	'Jetpack Compose' and 'Material Design 3' provide some distinctiveness from generic Android or UI skills, but 'state management' and 'navigation' are broad terms that could overlap with other mobile or frontend 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 skill provides solid, actionable Compose guidance with executable code examples covering core patterns. However, it's somewhat verbose in framing, lacks validation checkpoints for the multi-step setup process, and could benefit from splitting advanced content into separate files for better progressive disclosure.

Suggestions

Remove the 'When to Use This Skill' section - these use cases are self-evident from the content

Add validation steps after project setup (e.g., 'Build and verify Compose preview renders') and after ViewModel implementation

Split advanced topics (performance optimization, stability annotations, migration) into separate linked files like PERFORMANCE.md and MIGRATION.md

Trim introductory language like 'comprehensive guide' and 'production-quality' - let the content speak for itself

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary framing ('comprehensive guide', 'production-quality') and the 'When to Use This Skill' section explains obvious use cases Claude could infer. The code examples are appropriately sized but could be tighter.	2 / 3
Actionability	Provides fully executable, copy-paste ready code examples for dependencies, ViewModel patterns, Screen composables, and navigation. All code is complete Kotlin with proper imports implied and realistic patterns.	3 / 3
Workflow Clarity	Steps are numbered and sequenced (Setup → State Management → Screen Composable), but lacks validation checkpoints. No guidance on verifying the setup works, testing recomposition behavior, or debugging steps if something fails during implementation.	2 / 3
Progressive Disclosure	Content is reasonably structured with clear sections, but everything is inline in one file. Advanced topics like performance optimization, Material Design 3 theming, and migration strategies mentioned in the description could be split into separate reference files.	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: boisenoise/skills-collections
Commit: 5c5ae21

Reviewed: 3 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.