CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is token-efficient and uses progressive disclosure well, offloading code templates to a real reference file. It is weakened by the absence of any executable example in the body and a dangling 'Priority: P0' header.

Suggestions

Remove or populate the empty '## Priority: P0' header so it does not read as a dangling section.

Add one small executable Kotlin snippet (e.g. a runTest + MainDispatcherRule skeleton) directly in the body so guidance is copy-paste ready without opening the reference.

Add a brief validation/verification note (e.g. run tests, confirm no real network/thread-sleep) as an explicit checkpoint after the implementation steps.

DimensionReasoningScore

Conciseness

Lean bullet-point body that assumes Claude's competence; no padding with basic explanations of what testing or coroutines are.

3 / 3

Actionability

Names concrete APIs (runTest, MainDispatcherRule, createAndroidComposeRule, @TestInstallIn) but the body itself has no executable code blocks; full copy-paste examples are delegated to the reference file.

2 / 3

Workflow Clarity

Sections are organized (Unit Tests, UI Integration Tests, Anti-Patterns) but there is no sequenced workflow or validation checkpoint, and the orphaned 'Priority: P0' header has no content beneath it.

2 / 3

Progressive Disclosure

Concise overview body with a single one-level-deep, clearly signaled reference to references/implementation.md, which exists and holds the detailed code templates.

3 / 3

Total

10

/

12

Passed

Description

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.

The description is concise, specific, third-person, and answers both what the skill does and when to use it with concrete trigger terms. It is a strong, well-targeted description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Write unit tests, Compose UI tests, and Hilt-integrated tests for Android') naming distinct test categories rather than vague language.

3 / 3

Completeness

Clearly states what it does and includes an explicit 'Use when writing test files or testing ViewModels, Composables, or Repositories...' trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms users would say ('unit tests', 'Compose UI tests', 'ViewModels', 'Composables', 'Repositories', 'MockK', 'coroutine test utilities') with good variation.

3 / 3

Distinctiveness Conflict Risk

Narrow Android-testing niche with distinctive triggers (Hilt, MockK, Compose, coroutine test utilities) unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.