CtrlK
BlogDocsLog inGet started
Tessl Logo

android

Workflow guide when working with Android builds or the mobile/ directory.

60

4.00x
Quality

37%

Does it follow best practices?

Impact

100%

4.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/android/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%

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

This skill is extremely concise and provides one useful, non-obvious piece of project-specific knowledge (the `./mach gradle` wrapper). However, for a skill described as a 'workflow guide,' it is far too thin — it lacks any actual workflow steps, build targets, validation steps, or examples. It reads more like a single tip than a guide.

Suggestions

Add a multi-step workflow for common Android build tasks (e.g., building, running tests, deploying to device) with explicit commands and validation checkpoints.

Include at least one concrete, copy-paste-ready example such as `./mach gradle -p mobile/android assembleGecko` with expected output or success indicators.

Add common troubleshooting steps or verification commands (e.g., how to confirm a successful build, how to check for errors).

DimensionReasoningScore

Conciseness

Extremely lean — only two sentences, both adding non-obvious project-specific knowledge (use `./mach gradle` instead of `gradlew`, use `-p` for subdirectories). No fluff or explanation of concepts Claude already knows.

3 / 3

Actionability

Provides a concrete command substitution (`./mach gradle` instead of `gradlew`) and mentions the `-p` flag, but lacks an executable example showing actual usage (e.g., `./mach gradle -p mobile/android assembleDebug`). Key details like common tasks or typical gradle targets are missing.

2 / 3

Workflow Clarity

There is no workflow sequence, no steps, and no validation or verification guidance for Android builds. For a skill described as a 'workflow guide,' the content provides only a single substitution tip rather than any multi-step process.

1 / 3

Progressive Disclosure

The content is very short and well-organized with a clear heading, which is fine for a simple skill. However, for a topic as broad as 'Android builds or the mobile/ directory,' there are no references to additional resources, common tasks, or related files that would help with discovery.

2 / 3

Total

8

/

12

Passed

Description

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to be effective for skill selection. It lacks concrete actions, explicit trigger guidance, and sufficient detail about what the skill actually does. The only redeeming quality is the mention of 'Android builds' and 'mobile/ directory' which provide some domain specificity.

Suggestions

List specific concrete actions the skill covers, e.g., 'Guides building Android APKs, configuring Gradle files, resolving build errors, and running instrumentation tests.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Android builds, Gradle configuration, APK generation, mobile/ directory structure, or Android build errors.'

Replace the vague 'workflow guide' framing with active verbs describing what the skill does, e.g., 'Provides step-by-step instructions for compiling, testing, and debugging Android projects in the mobile/ directory.'

DimensionReasoningScore

Specificity

The description says 'workflow guide when working with Android builds' but does not list any concrete actions. It is vague about what the skill actually does — no specific capabilities like 'compile APKs', 'configure Gradle', 'run tests', etc.

1 / 3

Completeness

The 'what' is extremely weak ('workflow guide' is not a concrete description of capabilities), and there is no explicit 'when' clause or trigger guidance. The description fails to clearly answer either question.

1 / 3

Trigger Term Quality

It includes 'Android builds' and 'mobile/ directory' which are relevant keywords a user might mention, but it misses common variations like 'APK', 'Gradle', 'Android Studio', 'mobile app', '.apk', 'build.gradle', etc.

2 / 3

Distinctiveness Conflict Risk

'Android builds' and 'mobile/ directory' provide some specificity that distinguishes it from generic coding skills, but 'workflow guide' is vague enough that it could overlap with other build or mobile-related skills.

2 / 3

Total

6

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
mozilla/enterprise-firefox
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.