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.
82
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/xml-to-compose-migration/SKILL.mdQuality
Discovery
89%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 well-crafted skill description with strong trigger terms and clear 'what/when' structure. The main weakness is that the capabilities could be more specific about what aspects of conversion are handled (e.g., handling ConstraintLayout, custom views, data binding). Overall, it effectively distinguishes itself and would be reliably selected for Android UI migration tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Android XML layouts, Jetpack Compose) and the core action (convert/migrate), but doesn't list multiple specific concrete actions like handling specific layout types, attributes, or edge cases. | 2 / 3 |
Completeness | Clearly 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrate Views to Compose', 'convert XML to Composables', 'modernize UI', 'View system to Compose', 'Android XML layouts', 'Jetpack Compose' - these are all phrases developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting a specific Android development task. The combination of 'XML layouts', 'Jetpack Compose', 'Views', and 'Composables' creates distinct triggers unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 solid, actionable skill with excellent code examples and comprehensive mapping tables that provide real value for XML-to-Compose migrations. The main weaknesses are the monolithic structure (all reference tables inline rather than in separate files) and the lack of explicit validation steps in the workflow for catching migration errors early.
Suggestions
Add explicit validation checkpoints to the workflow, such as 'Run @Preview to verify visual output before proceeding' or 'Build and check for compilation errors after each component migration'
Extract the mapping tables (Container Layouts, Common Widgets, Attribute Mapping) to a separate REFERENCE.md file, keeping only the workflow and 2-3 key patterns in SKILL.md
Add a feedback loop for error recovery, e.g., 'If Compose preview shows layout issues: check Modifier order, verify Arrangement/Alignment params, compare with XML constraints'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good reference tables, but includes some unnecessary explanation in the workflow section that Claude would already understand (e.g., explaining what to identify in XML layouts). The mapping tables are appropriately dense. | 2 / 3 |
Actionability | Provides fully executable code examples for all common patterns, complete with before/after XML-to-Compose comparisons. The mapping tables give specific, copy-paste ready equivalents, and the interop examples are complete and runnable. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced, but lacks explicit validation checkpoints. Step 5 mentions 'Test and Verify' but doesn't provide concrete validation commands or feedback loops for catching migration errors before proceeding. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~300 lines) with all reference tables inline. The mapping tables could be extracted to separate reference files, with SKILL.md providing just the workflow and key patterns. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
3f68e39
- 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.