android-compose
Build high-performance declarative UI with Jetpack Compose state hoisting and recomposition optimization. Use when writing @Composable functions, Screen files, LazyColumn, state hoisting, LaunchedEffect, or diagnosing excessive recomposition. (triggers: **/*Screen.kt, **/*Composable*.kt, **/*Content.kt, @Composable, Modifier, Column, Row, LazyColumn, setContent, recompose, remember, derivedStateOf, LaunchedEffect)
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its domain (Jetpack Compose), lists specific capabilities (state hoisting, recomposition optimization, composable functions), and provides explicit trigger guidance with both a 'Use when' clause and a comprehensive triggers list. The description is concise yet thorough, using third-person voice and domain-specific terminology that would naturally appear in developer requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: building declarative UI, state hoisting, recomposition optimization, writing @Composable functions, working with LazyColumn, diagnosing excessive recomposition. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (build high-performance declarative UI with Jetpack Compose state hoisting and recomposition optimization) and 'when' (explicit 'Use when...' clause with specific scenarios plus a comprehensive triggers list). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: @Composable, Modifier, Column, Row, LazyColumn, setContent, recompose, remember, derivedStateOf, LaunchedEffect, plus file patterns like *Screen.kt and *Composable*.kt. These are exactly the terms a Kotlin/Android developer would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — Jetpack Compose is a specific Android UI framework with unique terminology (@Composable, recomposition, LazyColumn, derivedStateOf). Very unlikely to conflict with other skills unless there were multiple Compose-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that effectively communicates Compose best practices and anti-patterns without over-explaining. Its main weakness is the lack of any inline executable code examples — all implementation details are deferred to a reference file, which reduces immediate actionability. Adding at least one concrete code snippet for the most critical pattern (state hoisting) would significantly improve it.
Suggestions
Add at least one inline executable code example showing the Screen (stateful) -> Content (stateless) pattern with state hoisting, rather than deferring all code to the reference file.
Include a brief verification step, such as how to check recomposition counts using Layout Inspector or recomposition logging, to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line provides actionable guidance without explaining what Compose is or how Android UI works. No unnecessary padding or concept explanations that Claude would already know. | 3 / 3 |
Actionability | The guidance is specific and directive (e.g., 'Annotate params with @Stable or @Immutable', 'Use key in LazyColumn items'), but lacks executable code examples. The actual implementation patterns are deferred to a reference file rather than providing at least one concrete code snippet inline. | 2 / 3 |
Workflow Clarity | The skill presents a clear structure (state hoisting → recomposition optimization → side effects → anti-patterns), but there's no explicit workflow sequence with validation checkpoints. For a UI composition skill, there's no guidance on how to verify recomposition counts or validate that optimizations are working. | 2 / 3 |
Progressive Disclosure | The skill provides a concise overview with well-signaled one-level-deep references to references/implementation.md for detailed patterns. Content is appropriately split between the overview and the reference file, with clear navigation links. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.