xml-to-compose-migration

Convert Android XML layouts to Jetpack Compose. Use when asked to migrate Views to Compose, convert XML to Composables, or modernize UI from View system to Compose.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

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

A highly actionable, well-structured migration reference built on complete executable code and comprehensive mapping tables. Its weaknesses are mild: some inline reference material could be offloaded to bundle files, and the workflow's verification lacks explicit error-recovery feedback loops.

Suggestions

Move the container/widget/attribute mapping tables into a references/ file (e.g., references/mapping-table.md) and keep SKILL.md as an overview that points to it, improving progressive disclosure.

Add an explicit validation feedback loop before 'Old XML files deleted' (e.g., build and run the Compose UI, confirm parity, only then delete the XML) to strengthen workflow_clarity for this destructive step.

Dimension	Reasoning	Score
Conciseness	Dense, mostly reference material (mapping tables and complete code) that assumes Compose/Android competence and avoids explaining basics; a few of the longer worked examples and table notes could be trimmed, but nothing is padded.	4 / 5
Actionability	Copy-paste-ready Kotlin examples cover the common migration cases (weighted LinearLayout, RecyclerView→LazyColumn, two-way bound EditText, ConstraintLayout, ComposeView/AndroidView interop, LiveData→collectAsState), backed by exhaustive, concrete XML→Compose mapping tables.	5 / 5
Workflow Clarity	A clear five-step sequence (Analyze → Plan → Convert → Migrate State → Test & Verify) plus a closing checklist provides verification, but the workflow lacks explicit validate-then-proceed feedback loops despite involving a destructive step ('Old XML files deleted').	4 / 5
Progressive Disclosure	Well-organized into clear sections with a one-level-deep external References list; however, no bundle files exist and the large mapping tables/pattern library are fully inlined in SKILL.md rather than split into reference files.	4 / 5
	Total	17 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, third-person description that clearly states its single capability and provides explicit, natural trigger phrasings. The main limitation is that it describes essentially one action rather than a comprehensive set of distinct capabilities.

Suggestions

Add one or two genuinely distinct capabilities (e.g., 'migrate state and data binding, set up ComposeView interop for incremental adoption') to lift specificity beyond the single 'Convert' action.

Consider including a file/extension cue (e.g., '.xml layouts') to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Android XML layouts to Jetpack Compose') with one concrete core action ('Convert'), but the remaining phrases ('migrate Views to Compose', 'convert XML to Composables', 'modernize UI') are rewordings of that single capability rather than multiple distinct actions.	3 / 5
Completeness	Explicitly answers both 'what' ('Convert Android XML layouts to Jetpack Compose') and 'when' ('Use when asked to migrate Views to Compose, convert XML to Composables, or modernize UI from View system to Compose') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural developer phrasings ('migrate Views to Compose', 'convert XML to Composables', 'modernize UI', 'View system', 'Compose') with useful synonyms, though it lacks file-extension triggers and a few natural variations.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Android View-to-Compose migration) with distinct, specific triggers that are unlikely to fire for unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: new-silvermoon/awesome-android-agent-skills
Path: .github/skills/migration/xml-to-compose-migration/SKILL.md
Commit: 82900ea

Reviewed: 1 day 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.