android-testing

Write Android unit, Compose UI, and Hilt-integrated tests. Use when designing test behavior with MockK or coroutine test utilities; defer database/WorkManager-specific recipes to the owning feature skill.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-3

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

A well-organized, token-efficient standards skill that offloads executable code to a genuine one-level reference. Its weakness is that the body itself contains no copy-paste examples and no explicit validation checkpoint, leaving actionability and workflow clarity at the mid anchor.

Suggestions

Add one minimal inline snippet per test type (e.g., a runTest + MainDispatcherRule skeleton) so the body is copy-paste ready without opening the reference, lifting actionability.

Add a short verification checkpoint such as "Run ./gradlew test and confirm no real network calls or Thread.sleep leak" to give the workflow an explicit feedback loop.

Rename the reference link from "Test Rules" to match its actual content (implementation patterns for both unit and Compose UI tests) so the signaling is accurate.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-point guidance with no conceptual padding (no explaining what a test or coroutine is); every line names a specific tool or rule, matching the lean score-3 anchor.	3 / 3
Actionability	It names concrete APIs (runTest, MainDispatcherRule, MockK, createAndroidComposeRule, @TestInstallIn, IdlingResource) but includes no executable code blocks in the body, deferring actual usage to the reference — "some concrete guidance but incomplete" per the score-2 anchor.	2 / 3
Workflow Clarity	Guidance is organized by test type but there is no sequenced multi-step workflow and no validation/verification checkpoint (e.g., how to confirm tests run hermetically), so it sits at the score-2 anchor with sequence/categorization present but checkpoints missing.	2 / 3
Progressive Disclosure	The body is an overview that points to a single real one-level-deep reference (references/implementation.md, verified to exist) via a dedicated References section, matching the well-signaled one-level-deep score-3 anchor.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise, third-person description that clearly states capabilities, includes an explicit Use-when trigger, and actively scopes its boundary against sibling skills. It hits the top anchor on every dimension with no padding or over-claims.

Dimension	Reasoning	Score
Specificity	"Write Android unit, Compose UI, and Hilt-integrated tests" lists multiple specific concrete actions across distinct test categories, matching the score-3 anchor rather than the single-action score-2 anchor.	3 / 3
Completeness	It states both what ("Write Android unit, Compose UI, and Hilt-integrated tests") and an explicit when ("Use when designing test behavior with MockK or coroutine test utilities"), so it is not capped at 2.	3 / 3
Trigger Term Quality	Natural developer-facing terms ("Android unit", "Compose UI", "Hilt", "MockK", "coroutine") give good coverage of what a user would actually say, satisfying the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The explicit deferral ("defer database/WorkManager-specific recipes to the owning feature skill") carves a clear niche and reduces overlap, matching the distinct-trigger score-3 anchor.	3 / 3
	Total	12 / 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
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
Path: skills/android/android-testing/SKILL.md
Commit: 9f695e8

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.