CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trail-sense-android-tests

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

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary code-skill body: every section carries non-obvious, repo-specific guidance with executable examples, and the workflow's per-step completion criteria plus pass-or-report loop make the process safe to follow. The only knock is minor duplication between the skeleton and the filled-in CRUD patterns.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific knowledge (selector strategy, Andromeda IDs, seeding guards, canvas tapping) with no filler or explanation of concepts Claude already knows. Minor trimmable redundancy — the 'Test Structure' template stubs the CRUD helpers that 'Common Patterns' then fully defines — keeps it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Fully executable throughout: a complete test-class skeleton, copy-paste-ready create/edit/delete/toolbar/quick-action/back-navigation patterns, an exact file location, and concrete run commands with a timeout example. The common cases are covered with real code, and the few placeholders (<toolname>, <TOOL_ID>) are inherent to a template.

5 / 5

Workflow Clarity

The 3-step workflow is clearly sequenced and each step carries an explicit completion checkpoint ('This step is complete when...'), including a validation-oriented final step that ends only when 'the requested test passes or the blocking reason is reported' — an explicit feedback loop rather than a merely implied one.

5 / 5

Progressive Disclosure

The SKILL.md works as a well-organized overview: strategy, patterns, a compact function table, and running instructions inline, while complete API details and example tests are pushed one level deep via clearly signaled pointers ('Source Files' → AutomationLibrary.kt, TestUtils.kt, existing Tool*Test.kt). No bundle files exist, and nothing that belongs elsewhere is inlined.

5 / 5

Total

19

/

20

Passed

Description

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

A compact, distinctive description that names the exact domain and tooling, but it lacks an explicit 'Use when' trigger clause and sticks to a single action verb, leaving both completeness and specificity at the mid tier. Trigger-term coverage is good though missing a few natural synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding or updating UI/instrumented tests for a Trail Sense tool.'

Enumerate the main capabilities rather than a single verb, e.g. 'Create, update, and debug Trail Sense tool UI tests... covering CRUD flows, quick actions, toolbar menus, and deterministic seeded data.'

Include natural synonyms users might say, such as 'instrumented tests', 'Espresso-style UI tests', or 'androidTest', to broaden trigger matching.

DimensionReasoningScore

Specificity

Names the domain ('Trail Sense UI automation tests') with concrete named libraries ('AutomationLibrary', 'ToolTestBase'), but offers only one action verb ('Add ... tests') — closest to 'names domain and 1-2 concrete actions, but not comprehensive'. Not a 4 since no list of several distinct actions is present; not a 2 since the actions referenced are specific rather than generic.

3 / 5

Completeness

The 'what' is clear (add UI automation tests using two named base classes), but the trailing 'for tool workflows or androidTests' reads as scope clarification rather than an explicit 'Use when...' trigger clause — 'when' is only weakly implied, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keywords — 'UI automation tests', 'androidTests', 'tool workflows', 'Trail Sense' are phrases a user would plausibly say. A few natural variations are missing ('instrumented tests', 'UI tests', 'write tests for a tool'), keeping it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The description is pinned to a single app ('Trail Sense') and its own test infrastructure ('AutomationLibrary', 'ToolTestBase', 'androidTests'), giving it a clear niche with distinct triggers and minimal conflict risk against generic Android or testing skills.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

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.