android-new-module
Guide for creating new Android gradle modules in the android-components project.
65
51%
Does it follow best practices?
Impact
83%
1.43xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/android-new-module/SKILL.mdQuality
Discovery
40%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 identifies a clear niche (creating Android gradle modules in the android-components project) which makes it distinctive, but it lacks explicit trigger guidance ('Use when...') and doesn't enumerate specific actions or steps involved. It would benefit from more concrete capability listing and an explicit 'when to use' clause.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to add a new module, create a new component, or set up a new gradle subproject in android-components.'
List specific concrete actions the skill covers, such as 'Creates build.gradle files, configures module dependencies, sets up manifest entries, and registers the module in settings.gradle.'
Include natural trigger term variations like 'new module', 'add component', 'Gradle setup', 'subproject', 'module template'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Android gradle modules, android-components project) and one action (creating), but doesn't list specific concrete steps or multiple actions involved in module creation. | 2 / 3 |
Completeness | Describes what it does (guide for creating Android gradle modules) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also fairly thin, bringing it to 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Android', 'gradle modules', and 'android-components project' that users might mention, but misses common variations like 'new module', 'add module', 'Gradle', 'component', or 'project setup'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Android gradle modules' and 'android-components project' is quite specific and unlikely to conflict with other skills; it targets a clear niche within a specific project. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
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 clear 9-step workflow and good verification steps. Its main weakness is that several critical steps (build.gradle, source files, README) defer to 'reference the example at...' rather than providing complete, copy-paste-ready templates, which reduces actionability. The content could be tightened by removing explanations of concepts Claude already knows (dependency types, what categories mean) while adding the actual file templates inline.
Suggestions
Provide a complete, executable build.gradle template inline rather than saying 'reference the example at...' — this is the most critical file for module creation and the current guidance is too abstract.
Remove or significantly trim the 'Component Categories' descriptions and 'Dependency Types' subsection, as Claude already understands these concepts — just list the category names and move on.
Include a minimal but complete example Kotlin source file and test file inline rather than referencing external examples, since the bundle has no supporting files to back up those references.
| 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 | Provides concrete directory structures, commands, and file templates, but several critical steps rely on 'reference the example at...' rather than providing the actual content (build.gradle, main Kotlin source, test file, README). The build.gradle step gives guidance but no complete executable example. This leaves gaps where Claude must infer or look up the actual patterns. | 2 / 3 |
Workflow Clarity | The 9-step workflow is clearly sequenced with explicit verification steps at the end (build, test, lint). The instruction to create a plan before executing is good. The registration step includes the follow-up mach command and warns about CI failure without the treeherder update. The verification section provides concrete commands for validation. | 3 / 3 |
Progressive Disclosure | The skill references example files in the repository (e.g., feature/example/build.gradle, ExampleFeature.kt) which is good for progressive disclosure, but since no bundle files are provided, these references are unverifiable. The content is somewhat monolithic — the Common Patterns and Notes sections could potentially be separate references. However, for a skill of this length, inline content is reasonable. | 2 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- mozilla/enterprise-firefox
- Commit
cd457f4
- 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.