android-compose-foundations

Build Android UI with Jetpack Compose foundations, layouts, modifiers, theming, and stable component structure.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/android-compose-foundations/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 technology domain (Jetpack Compose for Android) and lists several relevant topic areas, but it reads more like a category listing than a concrete skill description. It critically lacks a 'Use when...' clause, making it harder for Claude to know when to select this skill, and the listed capabilities are more abstract categories than specific actions.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about building Android UI with Jetpack Compose, creating composable functions, applying Material themes, or structuring Compose layouts.'

Replace abstract category names with concrete actions, e.g., 'Creates composable functions, applies Material Design theming, structures layout hierarchies with Row/Column/Box, and configures modifiers for sizing, padding, and click handling.'

Include additional natural trigger terms users might say, such as 'Compose UI', 'composables', '@Composable', 'Material Design', 'Kotlin UI', or 'Android screen layout'.

Dimension	Reasoning	Score
Specificity	Names the domain (Android UI with Jetpack Compose) and lists some areas (foundations, layouts, modifiers, theming, stable component structure), but these are more like categories than concrete actions. It doesn't list specific actions like 'create composable functions, apply Material themes, build navigation drawers'.	2 / 3
Completeness	Describes what the skill does (build Android UI with Jetpack Compose) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also only moderately clear, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Android UI', 'Jetpack Compose', 'layouts', 'modifiers', 'theming' which users might mention. However, it misses common variations like 'Compose UI', 'Material Design', 'composables', '@Composable', 'Kotlin UI', or 'Android app interface'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Jetpack Compose' specifically narrows the domain and distinguishes it from general Android development or other UI frameworks. However, it could still overlap with broader Android development skills or Kotlin skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

35%

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

This skill reads more like a high-level process document than an actionable technical guide. Its biggest weakness is the complete absence of Compose code examples—no layout snippets, modifier chains, theming setup, or component structure patterns—which is critical for a skill about building Android UI with Jetpack Compose. The workflow and guardrails provide reasonable structure but remain too abstract to be directly useful.

Suggestions

Add concrete, executable Compose code examples showing common patterns: a basic composable with modifiers, a layout using Column/Row/Box, and a themed component using MaterialTheme tokens.

Replace the abstract workflow steps with specific, actionable instructions—e.g., 'Use `@Preview` with `widthDp = 320` to test narrow layouts' instead of 'Exercise edge cases such as long text, font scaling, RTL.'

Include at least one complete, copy-paste-ready composable function that demonstrates the stable component structure mentioned in the skill description.

Add specific validation commands or checks in the workflow, such as lint rules for accessibility semantics or specific test assertions to verify layout behavior.

Dimension	Reasoning	Score
Conciseness	The content is reasonably concise but includes some filler language and vague guidance that doesn't add value beyond what Claude already knows (e.g., 'Select the lowest-friction UI pattern that satisfies responsiveness, accessibility, and performance needs' is generic advice). The anti-patterns and guardrails sections contain reasonable but somewhat obvious guidance for an AI that already understands Compose.	2 / 3
Actionability	The skill lacks any concrete, executable code examples. There are no Compose code snippets, no specific modifier patterns, no layout examples, and no theming code. The 'examples' section only provides gradle commands to run existing projects rather than showing how to actually build Compose UI. The workflow steps are abstract descriptions rather than concrete instructions.	1 / 3
Workflow Clarity	The workflow has numbered steps and the done checklist provides some validation criteria, but the steps are abstract and lack specific validation checkpoints. Step 5 mentions validation but doesn't specify what constitutes passing. The failure recovery example references a script but doesn't explain what to do when failures occur.	2 / 3
Progressive Disclosure	The skill mentions handoff skills and includes official references, which is good structure. However, the main content is somewhat monolithic with sections that could benefit from linking to detailed guides (e.g., a separate file for modifier patterns, layout examples, or theming setup). The references are external URLs only with no internal documentation links for deeper content.	2 / 3
	Total	7 / 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
metadata_field	'metadata' should map string keys to string values	Warning

	Total	10 / 11 Passed

Repository: krutikJain/android-agent-skills
Commit: c5bf673

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