android-xml-views
Implement ViewBinding, RecyclerView, and XML layouts correctly on Android. Use when working with XML layouts, ViewBinding, or RecyclerView adapters in legacy Android projects.
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 solid skill description that clearly identifies its niche in legacy Android XML-based development. It has explicit 'Use when' guidance and good trigger terms. The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond just 'implement correctly'.
Suggestions
Expand the capability list with more specific actions, e.g., 'Create RecyclerView adapters with ViewHolder patterns, set up ViewBinding in activities and fragments, design XML layouts with ConstraintLayout'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Android) and some specific technologies (ViewBinding, RecyclerView, XML layouts), but the action is limited to 'implement...correctly' rather than listing multiple concrete actions like 'create adapters, bind views, inflate layouts, handle view holders'. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement ViewBinding, RecyclerView, and XML layouts correctly on Android) and 'when' (explicit 'Use when working with XML layouts, ViewBinding, or RecyclerView adapters in legacy Android projects'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'ViewBinding', 'RecyclerView', 'XML layouts', 'adapters', 'legacy Android projects'. These are terms developers naturally use when seeking help with these specific Android patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a clear niche: legacy Android XML-based UI development with specific technologies (ViewBinding, RecyclerView). The 'legacy' qualifier and specific technology names distinguish it well from Jetpack Compose or other Android skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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 standards skill that efficiently communicates Android XML view best practices without over-explaining. Its main weakness is the lack of concrete code examples for ViewBinding setup and ListAdapter/DiffUtil implementation, which would make it significantly more actionable. The referenced implementation.md file is not present in the bundle, leaving a gap in progressive disclosure.
Suggestions
Add a brief, executable code snippet showing correct ViewBinding usage in an Activity or Fragment (e.g., inflating binding in onCreate).
Add a minimal ListAdapter + DiffUtil.ItemCallback code example to make the RecyclerView guidance copy-paste ready.
Include the referenced `references/implementation.md` file in the bundle to support the progressive disclosure structure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. Every line delivers actionable guidance without explaining concepts Claude already knows (e.g., doesn't explain what ViewBinding or RecyclerView are). No padding or unnecessary context. | 3 / 3 |
Actionability | Provides clear directives (use ListAdapter, use DiffUtil.ItemCallback, avoid notifyDataSetChanged) but lacks any concrete code examples. For a skill about implementing ViewBinding and RecyclerView adapters, executable code snippets showing correct patterns would significantly improve actionability. | 2 / 3 |
Workflow Clarity | This is a standards/guidelines skill rather than a multi-step workflow skill. The single-purpose directives are unambiguous and clearly organized by topic (ViewBinding, RecyclerView, Layouts, Anti-Patterns). No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | References implementation.md for ViewBinding & Adapter details, which is good structure. However, the bundle has no files, so the reference path cannot be verified. The reference is one-level deep and clearly signaled, but with only one reference link and no bundle to back it up, it's hard to give full marks. | 2 / 3 |
Total | 10 / 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.