android-java

Android Java development with MVVM, ViewBinding, and Espresso testing

Quality

31%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/android-java/SKILL.md

Quality

Discovery

32%

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 identifies a clear technology stack but reads as a topic label rather than a functional skill description. It lacks concrete actions, explicit trigger guidance ('Use when...'), and sufficient keyword coverage to reliably distinguish it from other Android or Java development skills.

Suggestions

Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about Android app development in Java, setting up MVVM architecture, ViewBinding, or writing Espresso UI tests.'

List specific concrete actions the skill performs, e.g., 'Creates Android activities and fragments using MVVM pattern, configures ViewBinding for layouts, writes Espresso instrumented tests for UI validation.'

Include common keyword variations users might say, such as 'Android app', 'ViewModel', 'LiveData', 'UI testing', 'instrumented tests', 'Android Studio'.

Dimension	Reasoning	Score
Specificity	Names the domain (Android Java development) and some specific technologies (MVVM, ViewBinding, Espresso testing), but doesn't list concrete actions like 'create activities', 'write unit tests', or 'set up data binding'. It reads more like a topic list than a description of capabilities.	2 / 3
Completeness	Only addresses 'what' at a high level (Android Java development with certain patterns) and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Android', 'Java', 'MVVM', 'ViewBinding', and 'Espresso testing' that users might mention, but misses common variations like 'Android app', 'UI testing', 'ViewModel', 'LiveData', 'instrumented tests', or file extensions like '.java'.	2 / 3
Distinctiveness Conflict Risk	The combination of Android + Java + MVVM + ViewBinding + Espresso is fairly specific and narrows the domain, but without explicit triggers it could still overlap with general Android development skills or Java development skills.	2 / 3
	Total	7 / 12 Passed

Implementation

29%

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

This skill is essentially an Android Java reference manual dumped into a single file. While the code examples are high-quality and executable, the content is far too verbose for a skill file — it explains patterns Claude already knows (MVVM, Repository, Singleton, ViewBinding) at textbook length. It lacks any workflow guidance, sequencing, or progressive disclosure structure.

Suggestions

Reduce content to project-specific conventions and decisions (e.g., 'We use MVVM with this specific callback pattern') rather than teaching standard Android patterns from scratch.

Add a workflow section with sequenced steps for common tasks like 'adding a new feature screen' with validation checkpoints (e.g., run lint, run tests before committing).

Split reference material (Gradle config, CI pipeline, lint config, full code examples) into separate bundle files and link from a concise overview in SKILL.md.

Remove explanatory comments like '// ViewModel - holds UI state, survives configuration changes' that describe concepts Claude already understands.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Explains standard Android patterns (MVVM, Repository, ViewBinding, Singleton) that Claude already knows well. The full Gradle config, CI pipeline, lint config, and boilerplate code examples are reference material Claude doesn't need spelled out in this detail. Much of this is textbook Android content.	1 / 3
Actionability	All code examples are fully executable and copy-paste ready — complete ViewModel, Repository, Activity, Fragment, test classes, Gradle config, and CI pipeline. Concrete and specific throughout.	3 / 3
Workflow Clarity	There is no workflow or sequenced process described. The skill is a collection of patterns and code snippets without any guidance on when or how to apply them in sequence. No validation checkpoints, no step-by-step process for creating features or running tests.	1 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files and no layered structure. Everything is inlined in a single massive document with no navigation strategy or separation of quick-start vs. reference material.	1 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: 7e5f7a2

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