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.
67
82%
Does it follow best practices?
Impact
—
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. The terminology is precise and domain-specific, making it highly distinguishable from other skills.
| 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 (writing Composable functions, optimizing recomposition, hoisting state, 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. The specific 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
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 well-structured, concise skill that effectively communicates Jetpack Compose best practices as clear rules and anti-patterns. Its main weakness is the lack of executable code examples — for a UI framework skill, concrete Composable snippets would greatly improve actionability. The referenced implementation file is missing from the bundle, which weakens the progressive disclosure strategy.
Suggestions
Add at least 2-3 concrete, executable Composable code snippets showing correct state hoisting, LazyColumn with keys, and LaunchedEffect usage to improve actionability.
Include the referenced `references/implementation.md` file in the bundle, or inline the most critical examples if the file cannot be provided.
Add error recovery guidance to the verification section (e.g., what to check if `./gradlew build` fails due to composition issues).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section delivers actionable rules without explaining what Jetpack Compose is or how recomposition works conceptually. No unnecessary padding or tutorial-style exposition. | 3 / 3 |
Actionability | The guidance is specific and rule-based (e.g., 'annotate params with @Stable or @Immutable', 'use key in LazyColumn items'), but lacks executable code examples. For a UI framework skill, concrete Composable code snippets showing correct vs incorrect patterns would significantly improve actionability. | 2 / 3 |
Workflow Clarity | The verification checklist is a good addition and the sections are logically sequenced (state → recomposition → side effects → anti-patterns → verification). However, there's no explicit workflow for building or refactoring a Composable, and the verification step of `./gradlew build` lacks error recovery guidance. | 2 / 3 |
Progressive Disclosure | References to `references/implementation.md` are well-signaled and one level deep, which is good structure. However, no bundle files were provided, meaning the referenced file doesn't exist, undermining the progressive disclosure. The skill also references the same file twice without differentiating what content lives where. | 2 / 3 |
Total | 9 / 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
3df717f
- 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.