CtrlK
BlogDocsLog inGet started
Tessl Logo

trail-sense-android-tests

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

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/trail-sense-android-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is an exemplary lean, actionable skill: executable code throughout, exact paths, a function reference table, and a workflow with explicit completion checkpoints. References to deeper API detail are cleanly signaled and one level deep with no bundle bloat.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: terse code blocks, a compact function table, and minimal prose with no padding explaining Android testing or library basics, so every token earns its place.

3 / 3

Actionability

It provides copy-paste-ready Kotlin for the test class, create/edit/delete flows, toolbar/quick-action patterns, and exact file paths plus runnable shell commands, matching 'fully executable code/commands; copy-paste ready'.

3 / 3

Workflow Clarity

The three-step Workflow is explicitly sequenced, each with an explicit completion criterion ('This step is complete when...'), and step 3 includes a validation checkpoint (test passes or blocking reason is reported), matching the clear-sequence-with-checkpoints anchor.

3 / 3

Progressive Disclosure

No bundle files exist; the body is a well-organized overview whose only deep references are clearly signaled one-level pointers to target-codebase source files in a dedicated 'Source Files' section, satisfying the simple-skill allowance for well-organized content.

3 / 3

Total

12

/

12

Passed

Description

57%

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 specific to its niche and clearly distinguishable, but it states only one action and lacks an explicit 'Use when' trigger clause, leaving the 'when' only implied. Adding explicit trigger guidance and a second concrete action would raise specificity and completeness.

Suggestions

Add an explicit 'Use when' clause, e.g. 'Use when adding or updating Trail Sense UI automation tests for a tool workflow or androidTest.'

Name an additional concrete action beyond 'add' (e.g., 'Add and update Trail Sense UI automation tests...') to reach the multi-action specificity anchor.

Include common trigger variations a developer might say, such as 'instrumentation test' or 'UI test', to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Trail Sense UI automation tests') and concrete tools ('AutomationLibrary and ToolTestBase') but states a single action (add tests) rather than enumerating multiple specific actions, so it matches 'names domain and some actions, but not comprehensive' rather than the multi-action level 3.

2 / 3

Completeness

It answers 'what' (add UI automation tests using the named libraries) and gives a weak 'when' ('for tool workflows or androidTests'), but lacks an explicit 'Use when...' trigger clause, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes relevant terms a developer might say ('UI automation tests', 'tool workflows', 'androidTests') but misses common variations like 'write a UI test', 'instrumentation test', or 'espresso test', fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The naming of 'Trail Sense', 'AutomationLibrary', and 'ToolTestBase' pins it to a very specific niche with distinct triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

9

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
kylecorry31/Trail-Sense
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.