android-java

Android Java development with MVVM, ViewBinding, and Espresso testing

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

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

The body is highly actionable with comprehensive, copy-paste-ready Android Java templates, but it is a monolithic ~570-line reference that inlines boilerplate and time-sensitive version pins rather than progressively disclosing detail via separate files. It lacks sequenced workflows with validation checkpoints.

Suggestions

Move large boilerplate blocks (GitHub Actions YAML, lint.xml, full Gradle dependency listings) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure and conciseness.

Replace or isolate pinned dependency versions (e.g., core:1.12.0, lifecycle:2.7.0) so they do not go stale inside the main skill body, or move them to a deprecated/versions section.

Add a short sequenced workflow (e.g., scaffold feature → implement ViewModel/Repository → write unit test → run lint → run Espresso) with explicit validation checkpoints for the common development flow.

Dimension	Reasoning	Score
Conciseness	The body is mostly code rather than prose padding, but it inlines substantial boilerplate (full Gradle dependencies with pinned versions like core:1.12.0, full GitHub Actions YAML, full lint.xml); the time-sensitive version pins penalize conciseness per the rubric.	3 / 5
Actionability	Provides concrete, copy-paste-ready Java, Groovy, YAML, and XML covering the common Android cases (MVVM ViewModel, Repository, ViewBinding Activity/Fragment, JUnit/Mockito, Espresso, CI, lint).	5 / 5
Workflow Clarity	This is a reference/patterns document, not a multi-step workflow, and exceeds 50 lines so the simple-skill exception does not apply; the CI section has an ordered sequence but no validation checkpoints or feedback loops, and the main development task is not sequenced.	3 / 5
Progressive Disclosure	Section headers provide reasonable in-file navigation, but the document is monolithic at ~570 lines with no bundle files and no references to external files; content that belongs in separate reference files (CI yaml, lint config, pattern catalogs) is fully inlined.	3 / 5
	Total	14 / 20 Passed

Description

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

The description is specific and uses natural Android terms with a clear niche, but it omits an explicit 'Use when...' trigger clause within the description field, capping completeness at 3. The action verb 'development' is generic despite the named technologies.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., 'Use when editing Android Java source files, build.gradle, or MVVM/ViewBinding/Espresso code') so trigger guidance is self-contained.

Replace the generic verb 'development' with concrete actions such as 'builds', 'refactors', 'tests', or 'debugs' to sharpen specificity.

Include common synonyms and file extensions (e.g., .java, build.gradle, Gradle) to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Android Java development') plus three concrete capability areas (MVVM, ViewBinding, Espresso testing), but the action verb 'development' is generic and no distinct actions are spelled out.	3 / 5
Completeness	Provides a clear 'what' but the description field itself contains no 'Use when...' clause (trigger guidance lives in a separate when-to-use field), so completeness is capped at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms Android developers actually say ('Android', 'Java', 'MVVM', 'ViewBinding', 'Espresso') with good coverage, though synonyms/extensions like .java or Gradle are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Android Java with named architecture/test patterns), mostly distinct from Kotlin-Android or generic Java skills with only minor overlap risk.	4 / 5
	Total	14 / 20 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: abc600e

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