android-compose
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects.
87
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 concrete capabilities, and includes an explicit 'Use when...' clause with natural trigger terms. It uses proper third-person voice and covers both what the skill does and when to use it, with terminology that is highly distinctive to the Jetpack Compose ecosystem.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing Composable functions, optimizing recomposition, hoisting state, working with LazyColumn and side effects. These are distinct, concrete capabilities within the Jetpack Compose domain. | 3 / 3 |
Completeness | Clearly answers both 'what' (build high-performance declarative UI with Jetpack Compose) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios like writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Jetpack Compose', 'Composable functions', 'recomposition', 'state hoisting', 'LazyColumn', 'side effects'. These are the exact terms Android developers use when seeking help with Compose. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in Jetpack Compose / Android declarative UI. Terms like 'Composable functions', 'recomposition', 'LazyColumn' are unique to this framework and unlikely to conflict with other 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 efficiently communicates Jetpack Compose best practices without over-explaining. Its main weakness is the lack of any inline executable code examples — all concrete implementation is deferred to a reference file, which reduces immediate actionability. The verification checklist is a strength but could benefit from explicit error-recovery guidance.
Suggestions
Add at least one inline executable code snippet (e.g., a minimal state-hoisting pattern or LazyColumn with key) so the skill is immediately actionable without needing to consult the reference file.
Expand the verification checklist with a feedback loop: specify what to do if a check fails (e.g., 'If ViewModel is passed below Screen-level, refactor by extracting state to the Screen composable and passing data/callbacks down').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is actionable and assumes Claude already knows Compose fundamentals. No unnecessary explanations of what Jetpack Compose is or how Android UI works. Bullet points are tight and directive. | 3 / 3 |
Actionability | Guidance is specific and directive (e.g., 'Annotate params with @Stable or @Immutable', 'Use key in LazyColumn items'), but lacks executable code examples. The skill delegates all concrete code to references/implementation.md rather than providing at least one copy-paste-ready snippet inline. | 2 / 3 |
Workflow Clarity | The numbered sections provide a logical sequence (state hoisting → recomposition optimization → side effects), and the verification checklist is a good checkpoint. However, there's no explicit workflow for building or refactoring a Compose screen step-by-step, and the checklist lacks a feedback loop (e.g., what to do if verification fails). | 2 / 3 |
Progressive Disclosure | The skill is 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, and navigation is clear. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- 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.