android-new-module

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

1.43x

Quality

47%

Does it follow best practices?

Impact

83%

1.43x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

62%

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

This is a solid procedural skill with a well-structured 9-step workflow and good verification steps. Its main weaknesses are reliance on external file references without bundle support (making several steps less immediately actionable) and some unnecessary explanations of concepts Claude already knows (dependency types, category descriptions). The workflow clarity is strong with explicit build/test/lint verification.

Suggestions

Inline the key portions of build.gradle template rather than just referencing the example file, since no bundle files are provided to support the reference.

Remove or significantly trim the 'Dependency Types' section under Common Patterns — Claude already knows the difference between api, implementation, and testImplementation.

Consider trimming the Component Categories section to just the list without descriptions, or move it to a separate reference file.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary explanations (e.g., explaining what each component category does, explaining what Robolectric properties do, explaining dependency types that Claude already knows). The category descriptions and dependency type explanations could be trimmed.	2 / 3
Actionability	The skill provides concrete directory structures, file templates, and commands, but several critical steps rely on 'reference the example at...' rather than providing the actual content (build.gradle, main Kotlin source, test file, README). Without bundle files to back those references, Claude would need to read those files first, making the guidance incomplete as written.	2 / 3
Workflow Clarity	The 9-step workflow is clearly sequenced with logical ordering (determine type → create dirs → build file → manifest → source → tests → config → readme → register). It includes explicit verification steps at the end (build, test, lint) and notes about CI failures if steps are missed (taskcluster/config.yml). The instruction to create a plan before executing is a good checkpoint.	3 / 3
Progressive Disclosure	The skill references example files in the repo (e.g., feature/example/build.gradle, ExampleFeature.kt) which is good progressive disclosure in principle, but no bundle files are provided to back these references. The content is also somewhat monolithic — common patterns, verification, and notes sections could potentially be separate files, though the overall length is manageable.	2 / 3
	Total	9 / 12 Passed

Description

32%

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 brief and identifies the domain (Android gradle modules in android-components) but lacks explicit trigger guidance ('Use when...'), concrete action details, and natural keyword variations. It reads more like a title than a functional description that would help Claude select this skill from a large pool.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to add a new module, create a gradle subproject, or scaffold a component in the android-components repository.'

List specific concrete actions the skill covers, such as 'Creates build.gradle files, configures module dependencies, updates settings.gradle, and sets up the module directory structure.'

Include natural trigger term variations users might say, such as 'new module', 'add component', 'module setup', 'gradle subproject', or 'scaffold module'.

Dimension	Reasoning	Score
Specificity	It names the domain (Android gradle modules) and a general action (creating), but doesn't list specific concrete steps or multiple actions involved in module creation.	2 / 3
Completeness	It describes what (creating new Android gradle modules) but has no explicit 'Use when...' clause or trigger guidance, and per the rubric, a missing 'Use when' clause caps completeness at 2. The 'what' is also fairly thin, making this closer to a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Android', 'gradle modules', and 'android-components project', but misses common variations users might say such as 'new module', 'add module', 'module setup', or 'project structure'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'android-components project' provides some specificity, but 'creating new Android gradle modules' could overlap with general Android development or Gradle build skills.	2 / 3
	Total	7 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mozilla/enterprise-firefox
Commit: 7c07e6f

Reviewed: about 1 month 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.