CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 concise, well-structured standards document with strong progressive disclosure and lean token efficiency. Its main gap is the absence of an explicit workflow sequence with validation checkpoints, since it functions as a reference/standards skill rather than a procedural one.

Suggestions

Add a short numbered workflow for the most common multi-step task (e.g., setting up ViewBinding then wiring a RecyclerView adapter) with an explicit validation/verify checkpoint such as building or running tests.

Inline one minimal copy-paste code snippet (e.g., the ListAdapter + DiffUtil.ItemCallback skeleton) in the body so the core pattern is actionable without opening the reference.

Clarify the verification expectation after RecyclerView changes (e.g., 'Confirm DiffUtil updates render without notifyDataSetChanged()') to give the standards a concrete feedback loop.

DimensionReasoningScore

Conciseness

Lean directive lines like 'Synthetics: kotlin-android-extensions Dead. Remove it.' and 'NEVER call notifyDataSetChanged()' assume Claude's competence with no padding or concept explanation.

5 / 5

Actionability

Concrete, executable directives ('Always inherit ListAdapter', 'Remove all import kotlinx.android.synthetic.*') are present, but copy-paste code examples are deferred to the reference rather than inline.

4 / 5

Workflow Clarity

Content is organized into labeled sections (ViewBinding, RecyclerView, Layouts, Anti-Patterns) but presents standards rather than a sequenced multi-step workflow, with no validation checkpoints.

3 / 5

Progressive Disclosure

The body is a concise overview with a single well-signaled one-level-deep reference ([ViewBinding & Adapter](references/implementation.md)) that exists as a real file, keeping detail appropriately separated.

5 / 5

Total

17

/

20

Passed

Description

87%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 strong, concise description that clearly states capabilities and explicit trigger conditions with useful boundary guidance. Minor room to broaden trigger synonyms and enumerate more distinct actions.

DimensionReasoningScore

Specificity

Names concrete targets ('ViewBinding, RecyclerView, and XML layouts') and the action 'Implement...correctly', plus sub-areas ('item animations and layout managers'), but the action verb is largely a single 'implement/change' rather than multiple distinct concrete actions.

4 / 5

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...'), with concrete trigger phrases and explicit boundary guidance.

5 / 5

Trigger Term Quality

Includes natural Android terms users would say ('ViewBinding', 'RecyclerView', 'XML layouts', 'item animations', 'layout managers') with good coverage, but misses common synonyms/extensions like '.xml' or 'adapter'.

4 / 5

Distinctiveness Conflict Risk

Clear Android XML-views niche with distinct triggers, and the boundary clause ('defer standalone animation or layout-manager questions unrelated to RecyclerView') minimizes conflict with adjacent skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.