android-java

Android Java development with MVVM, ViewBinding, and Espresso testing

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/android-java/SKILL.md

Quality

Content

65%

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

The content is highly actionable with complete, executable examples, but it is a monolithic reference catalog that leans verbose and lacks sequenced workflows with validation checkpoints.

Suggestions

Move large, self-contained blocks (Gradle config, GitHub Actions YAML, lint.xml) into reference files and link to them one level deep to improve progressive disclosure.

Tighten or remove explanatory comments and the anti-patterns list that restate Android concepts Claude already knows.

Add a short sequenced workflow (e.g. implement ViewModel -> wire ViewBinding -> write Espresso test -> run ./gradlew connectedDebugAndroidTest) with an explicit validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The ~570-line body is mostly concrete code, but explanatory comments ('holds UI state, survives configuration changes', 'Always use application context to prevent Activity leaks') and the anti-patterns list restate concepts Claude already knows and could be tightened.	2 / 3
Actionability	It provides fully executable Java, complete Gradle config, GitHub Actions YAML, and lint.xml that are copy-paste ready with specific, complete examples.	3 / 3
Workflow Clarity	The body is a pattern catalog rather than a sequenced workflow; the CI section lists steps (lint, test, build, upload) but lacks validate-then-fix feedback loops for build/test operations.	2 / 3
Progressive Disclosure	No bundle files exist, so everything is inline in one monolithic file; section headers give structure, but content that could be split (full Gradle config, CI YAML, lint config) is not separated into referenced files.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 specific and well-targeted to Android Java with strong trigger terms, but it omits an explicit 'Use when...' clause, leaving the 'when to use' guidance outside the description field.

Suggestions

Add an explicit trigger clause to the description, e.g. 'Use when working on Android Java source files, Gradle builds, or Espresso tests'.

Frame capabilities as concrete actions (e.g. 'build MVVM screens, wire ViewBinding, write Espresso tests') rather than only listing technology names.

Dimension	Reasoning	Score
Specificity	Names the domain ('Android Java development') and several technologies ('MVVM, ViewBinding, and Espresso testing'), but lists tech stacks rather than concrete actions (build, test, refactor), so it is not comprehensive.	2 / 3
Completeness	It clearly states what the skill covers but has no 'Use when...' clause in the description itself; the trigger lives only in the separate when-to-use field, so 'when' is missing from the description.	2 / 3
Trigger Term Quality	Terms like 'Android Java', 'MVVM', 'ViewBinding', and 'Espresso' are exactly the natural keywords a developer would say when they need this skill.	3 / 3
Distinctiveness Conflict Risk	The narrow 'Android Java' scope with MVVM/ViewBinding/Espresso forms a clear niche unlikely to conflict with non-Android or Kotlin-focused skills.	3 / 3
	Total	10 / 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
skill_md_line_count	SKILL.md is long (582 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/android-java/SKILL.md
Commit: bb6195f

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.