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 (what the skill does) and entirely omits trigger guidance (when to use it). Adding specific capabilities and a 'Use when...' clause would significantly improve its effectiveness for skill selection.

Suggestions

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

List concrete actions the skill performs, e.g., 'Creates Android activities and fragments using MVVM pattern, sets up ViewBinding for type-safe view access, writes Espresso instrumented tests for UI validation.'

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

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 UI 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 any 'when should Claude use it' guidance. 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 '.java files'.	2 / 3
Distinctiveness Conflict Risk	The combination of Android + Java + MVVM + ViewBinding + Espresso is fairly specific and narrows the niche, but it could still overlap with a general Android development skill or a Java development skill. The lack of explicit trigger guidance increases conflict risk.	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 reads as a comprehensive Android Java reference/tutorial rather than a focused skill for Claude. It is highly verbose, explaining patterns and concepts Claude already knows well (MVVM, Repository pattern, singletons, ViewBinding), and lacks any workflow guidance or progressive disclosure structure. Its main strength is that all code examples are complete and executable.

Suggestions

Reduce content by 70-80% — remove standard patterns Claude already knows (MVVM, Repository, Singleton, basic Gradle setup) and focus only on project-specific conventions, non-obvious decisions, or custom tooling.

Add a clear workflow section with sequenced steps for common tasks (e.g., 'Adding a new feature screen: 1. Create model → 2. Create repository interface → 3. Implement ViewModel → 4. Run tests → 5. Verify lint passes').

Split reference material into separate files (e.g., GRADLE.md, CI.md, TESTING.md) and keep SKILL.md as a concise overview with links to each.

Replace the anti-patterns bullet list with a brief 'Key constraints' section listing only project-specific rules that differ from standard Android best practices.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Much of this is boilerplate that Claude already knows — standard MVVM patterns, Gradle configuration, Retrofit setup, singleton patterns, and basic Android anti-patterns are all well-known to Claude. The entire file reads like an Android tutorial rather than a concise skill reference adding novel information.	1 / 3
Actionability	The code examples are fully executable and copy-paste ready — complete ViewModel, Repository, Activity, Fragment, test classes, Gradle config, CI pipeline, and lint configuration. Every pattern includes concrete, working Java code rather than pseudocode.	3 / 3
Workflow Clarity	There is no clear workflow or sequenced process for building an Android app. The content is organized as a reference catalog of patterns and configurations but lacks any step-by-step guidance, validation checkpoints, or feedback loops for common development tasks like setting up a project, adding a feature, or running tests.	1 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files and no layered structure. Everything from Gradle config to CI pipelines to anti-patterns is inlined in a single massive document. Content like the full Gradle config, CI YAML, and lint XML could easily be split into separate referenced files.	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: 65efb33

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.