trail-sense-android-tests

Add Trail Sense UI automation tests using AutomationLibrary and ToolTestBase for tool workflows or androidTests.

Quality

81%

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

93%Weight 40%Scale 1-5

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

The content is a strong, token-efficient skill body with executable examples, a clear sequenced workflow with checkpoints, and well-structured one-level-deep references. The only minor gap is an implicit rather than explicit validate-and-retry loop in the test-run step.

Dimension	Reasoning	Score
Conciseness	The body is lean: purposeful headers, executable code with minimal prose, and no padding explaining what UI tests or Kotlin are; every token earns its place.	5 / 5
Actionability	Provides fully executable, copy-paste-ready Kotlin examples, a Key Functions reference table, and concrete script commands with file paths covering the common create/edit/delete/toolbar/quick-action cases.	5 / 5
Workflow Clarity	A three-step Workflow with explicit completion checkpoints per step and a branch for handling the no-emulator case; minor gap is the implicit (rather than explicit) re-run-after-fix validation loop.	4 / 5
Progressive Disclosure	Well-organized sections with a one-level-deep 'Source Files' pointer deferring complete API details to repo paths, keeping the SKILL.md as a concise overview with clean navigation.	5 / 5
	Total	19 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 concrete and distinctive, clearly scoping the skill to Trail Sense UI automation tests with named libraries. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the invocation conditions only weakly implied.

Suggestions

Add an explicit trigger clause such as 'Use when adding or updating UI automation tests for Trail Sense tools' to raise completeness.

Include a couple of natural synonyms users might say (e.g. 'instrumentation tests', 'espresso tests') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names a concrete action ("Add Trail Sense UI automation tests") with specific libraries ("AutomationLibrary and ToolTestBase") and target context ("tool workflows or androidTests"), listing several specific elements with only minor coverage gaps.	4 / 5
Completeness	Provides a clear "what" but the "when" is only weakly implied by "for tool workflows or androidTests" with no explicit "Use when..." clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural keywords users would say in this niche ("UI automation tests", "Trail Sense", "androidTests") with good coverage, though a few common synonyms and an explicit trigger phrase are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (Trail Sense, named test libraries, androidTests) with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: kylecorry31/Trail-Sense
Path: .agents/skills/trail-sense-android-tests/SKILL.md
Commit: fa3f680

Reviewed: ~12 hours 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.