android-jetpack-compose-expert

Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable Kotlin examples and a clear step sequence, but inline version pins hurt conciseness and the absence of validation checkpoints and external references leaves workflow clarity and progressive disclosure at mid-level.

Suggestions

Move pinned versions to a separate references file or a clearly marked 'current versions' section so they don't date the inline guidance.

Add explicit validation/checkpoint steps (e.g. build, run, verify recomposition in Layout Inspector) within the Step-by-Step Guide.

Split the dependency catalog and navigation examples into reference files linked from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code-centric content, but embeds time-sensitive version numbers (composeBom = "2024.02.01", activityCompose = "1.8.2") inline rather than in a deprecated/old-patterns section, which penalizes conciseness per the rubric.	2 / 3
Actionability	Provides fully executable, copy-paste-ready Kotlin including libs.versions.toml entries, a StateFlow ViewModel, Composable screens, and type-safe navigation — concrete rather than abstract.	3 / 3
Workflow Clarity	A numbered Step-by-Step Guide sequences setup, state, and screen creation, but there are no explicit validation checkpoints or feedback loops; the Troubleshooting section gives recovery hints rather than inline checkpoints.	2 / 3
Progressive Disclosure	Content is well-organized into clear sections but everything is inline in a single ~150-line SKILL.md with no bundle references; referenceable material (e.g. full dependency catalog, navigation patterns) could be split out.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 is specific and distinctive with strong natural trigger terms, but it omits an explicit "Use when..." clause so the use-case trigger is only implied. Adding a trigger clause would raise completeness.

Suggestions

Append a 'Use when ...' clause naming concrete triggers, e.g. 'Use when building or migrating Android UIs with Jetpack Compose, or when handling Compose state, navigation, or performance.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — "building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3" — rather than vague abstractions.	3 / 3
Completeness	It clearly states what the skill does but lacks an explicit "Use when..." trigger clause, so the "when" is only implied; per guidelines a missing trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms a developer would say are well covered: "Jetpack Compose", "Android UIs", "state management", "navigation", "Material Design 3".	3 / 3
Distinctiveness Conflict Risk	"Android UIs with Jetpack Compose" and "Material Design 3" define a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: boisenoise/skills-collections
Commit: f36337d

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