android-testing
Write unit tests, Compose UI tests, and Hilt-integrated tests for Android. Use when writing test files or testing ViewModels, Composables, or Repositories with MockK and coroutine test utilities.
87
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (Android testing), lists specific concrete actions and targets, and includes an explicit 'Use when' clause with natural trigger terms. The description is concise yet comprehensive, covering the technology stack (MockK, Hilt, Compose, coroutines) and the types of components it targets (ViewModels, Composables, Repositories).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Write unit tests', 'Compose UI tests', 'Hilt-integrated tests' for Android, and mentions specific targets like ViewModels, Composables, Repositories with specific tools (MockK, coroutine test utilities). | 3 / 3 |
Completeness | Clearly answers both 'what' (write unit tests, Compose UI tests, Hilt-integrated tests for Android) and 'when' (explicit 'Use when writing test files or testing ViewModels, Composables, or Repositories with MockK and coroutine test utilities'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'unit tests', 'UI tests', 'Android', 'ViewModels', 'Composables', 'Repositories', 'MockK', 'coroutine', 'Hilt', 'test files'. These cover the terms a developer would naturally use when requesting Android testing help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Android-specific testing with particular frameworks (Hilt, MockK, Compose) and patterns (ViewModels, Repositories). Unlikely to conflict with general testing skills or non-Android skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-structured skill that efficiently communicates Android testing conventions and anti-patterns. Its main weakness is the lack of concrete, executable code examples — a ViewModel test snippet and a Compose UI test snippet would significantly improve actionability. The workflow for actually writing tests could also be more explicit.
Suggestions
Add a concrete, executable code example for a ViewModel unit test using MockK, runTest, and MainDispatcherRule
Add a concrete code example for a Compose UI integration test using createAndroidComposeRule with HiltAndroidRule and @TestInstallIn
Consider adding a brief step-by-step workflow for writing a test (e.g., 1. Create test class with rules, 2. Set up mocks, 3. Call SUT, 4. Assert/verify)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what unit tests are or how MockK works. Every line provides specific, actionable guidance that Claude wouldn't already know about this project's conventions. | 3 / 3 |
Actionability | Provides specific tool/library names and patterns (runTest, MainDispatcherRule, createAndroidComposeRule, @TestInstallIn) but lacks executable code examples. A concrete code snippet showing a ViewModel test with MockK and runTest would make this fully actionable. | 2 / 3 |
Workflow Clarity | The skill distinguishes between unit tests and UI integration tests with clear scoping, but there's no sequenced workflow for writing a test (e.g., setup -> arrange mocks -> act -> assert -> verify). For a testing skill, a step-by-step test creation workflow with validation would strengthen this. | 2 / 3 |
Progressive Disclosure | Clean overview structure with well-organized sections (Unit Tests, UI Integration Tests, Anti-Patterns) and a single-level reference to implementation.md for detailed test rules. Appropriate content split for a skill of this scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- Reviewed
Table of Contents
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.