android-new-module

Guide for creating new Android gradle modules in the android-components project.

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/android-new-module/SKILL.md

Quality

Content

75%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 body is a well-structured, actionable procedural guide with concrete commands, real example-file references, and a verification section. It is efficient and clearly sequenced, with only minor gaps in feedback-loop explicitness and a few reference-based steps.

Dimension	Reasoning	Score
Conciseness	Efficient and well-organized with executable commands and key-element lists; only minor explanatory sentences (e.g. 'This configures Robolectric to use Android SDK 35') could be trimmed.	4 / 5
Actionability	Provides concrete, executable commands (mkdir, mach gradle, mach lint) and real file paths, but build.gradle and Kotlin source steps reference external examples rather than giving copy-paste code, leaving minor gaps.	4 / 5
Workflow Clarity	A clearly sequenced 9-step process with a dedicated Verification section (buildDebug, testDebug, lint) as checkpoints, but lacks an explicit validate->fix->retry feedback loop for the score-5 anchor.	4 / 5
Progressive Disclosure	Well-structured with clear sections and clearly signaled one-level references to repo example files; no nested references. Slightly long for a single file, with build.gradle/source details that could live in reference files.	4 / 5
	Total	16 / 20 Passed

Description

53%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 concise and names a specific, distinctive niche, but it omits any explicit 'when to use' trigger guidance and lists only one action. It reads as a clear 'what' with the 'when' missing.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when creating a new Android gradle module in android-components or when the user asks to add a new component category.'

Expand the action list beyond 'creating' to cover the sub-tasks (e.g. scaffolding directories, configuring build.gradle, registering in .buildconfig.yml) for fuller capability coverage.

Include natural synonyms/variants such as 'new module', 'gradle component', and 'android-components' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the specific domain ('Android gradle modules in the android-components project') and one concrete action ('creating'), matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes relevant natural terms ('Android', 'gradle modules', 'android-components') a developer would say, but lacks common variations or synonyms like 'new module' phrasings.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Android gradle modules in a specific project) with minimal overlap risk, though trigger phrases are sparse compared to the score-5 anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: mozilla/enterprise-firefox
Path: .agents/skills/android-new-module/SKILL.md
Commit: cd7d47c

Reviewed: 4 days 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.