android-xml-views

Implement ViewBinding, RecyclerView, and XML layouts correctly on Android. Use when changing XML view binding or RecyclerView behavior, including its item animations and layout managers; defer standalone animation or layout-manager questions unrelated to RecyclerView.

Quality

86%

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

72%Weight 40%Scale 1-3

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

The body is concise and well-structured with proper progressive disclosure to a real reference file, but it delegates all executable code to that reference and provides no sequenced workflow or validation checkpoint for fragile binding/RecyclerView edits. Actionability and workflow clarity are the weaker dimensions.

Suggestions

Add a minimal inline executable snippet for the most common task (e.g., the ListAdapter + DiffUtil skeleton or the buildFeatures.viewBinding = true block) so the body is copy-paste ready without hopping to the reference.

Add a short sequenced workflow with a verification step for RecyclerView/ViewBinding changes (e.g., build -> run -> confirm animations/diff updates behave), so workflow_clarity has an explicit checkpoint.

Explicitly state how to verify a ViewBinding/RecyclerView change is correct (e.g., 'Build succeeds and list updates animate without notifyDataSetChanged') to provide a feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is a lean bullet list of standards with no concept explanations Claude already knows (no 'what a RecyclerView is'), matching the score-3 'lean and efficient; every token earns its place'; not 2 because there is no padded or unnecessary explanation.	3 / 3
Actionability	Concrete rules are present ('Always inherit ListAdapter', 'NEVER call notifyDataSetChanged()', 'viewBinding = true', 'remove all import kotlinx.android.synthetic.*'), but the body has no inline executable code — the copy-paste-ready Kotlin lives one hop away in references/implementation.md, matching score-2 'some concrete guidance but incomplete'; not 3 because the SKILL.md body alone is not copy-paste ready, and not 1 because the guidance is specific rather than abstract.	2 / 3
Workflow Clarity	The content is a categorical standards list rather than a sequenced workflow, with no validation/verification checkpoint for fragile XML binding or RecyclerView edits, matching score-2 'sequence present but checkpoints missing or implicit'; not 3 because no explicit feedback loop is given, and not 1 because the standards do imply an order of concerns.	2 / 3
Progressive Disclosure	SKILL.md is an overview pointing to a single real one-level-deep reference — 'References: [ViewBinding & Adapter](references/implementation.md)' — with executable code appropriately split into references/implementation.md, matching the score-3 'clear overview with well-signaled one-level-deep references'; not 2 because navigation is clean and the split is appropriate.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 is strong: concrete capabilities, explicit 'Use when' triggers with natural terminology, and a clear Android niche reinforced by deferral guidance that limits conflict risk. It cleanly satisfies what/when and distinctiveness.

Dimension	Reasoning	Score
Specificity	Quotes concrete actions on a named platform: 'Implement ViewBinding, RecyclerView, and XML layouts correctly on Android.' Lists multiple specific capabilities rather than vague language, matching the score-3 anchor; not 2 because it is comprehensive rather than naming only some actions.	3 / 3
Completeness	Explicitly answers both: what ('Implement ViewBinding, RecyclerView, and XML layouts correctly on Android') and when ('Use when changing XML view binding or RecyclerView behavior...'), satisfying the score-3 anchor with an explicit 'Use when' clause; not 2 because the trigger guidance is explicit, not merely implied.	3 / 3
Trigger Term Quality	Includes natural terms developers actually say — 'ViewBinding', 'RecyclerView', 'XML layouts', 'item animations', 'layout managers' — giving good coverage, matching the score-3 anchor; not 2 because common variations are well covered rather than partially.	3 / 3
Distinctiveness Conflict Risk	An Android-specific niche with deferral guidance ('defer standalone animation or layout-manager questions unrelated to RecyclerView') reduces overlap, matching the score-3 'clear niche with distinct triggers'; not 2 because the negative trigger boundary makes conflicts unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Repository: HoangNguyen0403/agent-skills-standard
Path: skills/android/android-xml-views/SKILL.md
Commit: 9f695e8

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