Content
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill fails at its stated purpose: teaching Claude to write Android unit tests for reducers, use cases, repositories, and lifecycle-safe state holders. It contains no executable test code, no concrete patterns, and no specific guidance—just generic quality-engineering platitudes and gradle commands to run pre-existing tests. The workflow section reads like a reusable template that was never customized for this skill's domain.
Suggestions
Add concrete, executable test code examples for each target (reducer test with JUnit, repository test with mocked data source, use case test with coroutines/Turbine) showing imports, setup, assertions, and expected output.
Replace the generic 5-step workflow with an Android-unit-test-specific workflow: identify the class under test → set up test dependencies (MockK/fake) → write test cases covering happy path, error, and edge cases → run and verify → check coverage.
Remove or heavily condense the generic Guardrails and Anti-Patterns sections, replacing them with Android-testing-specific pitfalls (e.g., testing implementation details of ViewModel instead of state emissions, not using TestDispatcher for coroutines).
Add inline code snippets showing patterns like testing a MVI reducer's state transitions, mocking a repository with MockK, or using Turbine to test Flow emissions from a ViewModel.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes generic filler sections (Guardrails, Anti-Patterns) that read like boilerplate rather than Android-unit-test-specific guidance. Phrases like 'Treat performance and security work as engineering tasks with evidence, not folklore' waste tokens on platitudes Claude already knows. | 2 / 3 |
Actionability | Despite claiming to teach how to write unit tests for reducers, use cases, repositories, and state holders, the skill provides zero executable test code, no test structure examples, no assertion patterns, and no concrete guidance on mocking or test setup. The examples section only shows gradle commands to run existing tests, not how to write them. | 1 / 3 |
Workflow Clarity | The workflow is entirely abstract and generic ('Scope the risk surface', 'Pick the narrowest verification strategy') with no Android-testing-specific steps. There are no validation checkpoints, no feedback loops for test failures, and no concrete sequence for writing a unit test for a reducer or repository. | 1 / 3 |
Progressive Disclosure | The skill mentions handoff skills (android-testing-ui, android-ui-states-validation) and includes official references, which is good structure. However, the main content itself is a wall of generic text with no references to detailed companion files for specific patterns like reducer testing or repository mocking. | 2 / 3 |
Total | 6 / 12 Passed |