Implement ViewBinding, RecyclerView, and XML layouts correctly on Android. Use when working with XML layouts, ViewBinding, or RecyclerView adapters in legacy Android projects.
88
87%
Does it follow best practices?
Impact
Pending
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 capability description could be more specific about the concrete actions performed beyond just 'implement correctly'.
Suggestions
Expand the 'what' clause 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
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise standards skill that efficiently communicates Android XML view best practices without unnecessary explanation. Its main weakness is the lack of inline executable code examples—key patterns like ListAdapter with DiffUtil or ViewBinding setup are deferred entirely to the reference file. The organization and progressive disclosure are excellent for a skill of this scope.
Suggestions
Add a brief inline code snippet showing the ListAdapter + DiffUtil.ItemCallback pattern, since this is the most critical and error-prone guidance in the skill.
Include a minimal ViewBinding usage example (e.g., inflating in a Fragment) so the skill is actionable without requiring the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. Every line conveys actionable information without explaining concepts Claude already knows. No padding or unnecessary context about what ViewBinding or RecyclerView are. | 3 / 3 |
Actionability | Provides clear directives (use ListAdapter, provide DiffUtil.ItemCallback, never call notifyDataSetChanged) but lacks executable code examples. The actual implementation details are deferred to a reference file, so the skill itself reads more as a checklist than copy-paste-ready guidance. | 2 / 3 |
Workflow Clarity | This is a simple, single-purpose standards skill rather than a multi-step workflow. The guidance is unambiguous: use ViewBinding, use ListAdapter with DiffUtil, avoid specific anti-patterns. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Clean overview with well-organized sections (Implementation Guidelines, Anti-Patterns, References) and a single clearly-signaled one-level-deep reference to implementation.md for detailed code examples. | 3 / 3 |
Total | 11 / 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 | |
4c72e76
Table of Contents
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.