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.mdFeature module scaffold with buildconfig registration
Plan has 9 steps
50%
100%
Correct directory paths
100%
100%
Test directory paths
0%
100%
build.gradle plugins
100%
100%
build.gradle namespace
25%
100%
build.gradle dependencies
100%
100%
Manifest MPL comment
100%
100%
Minimal manifest
0%
100%
MPL headers on source files
100%
100%
Alphabetical buildconfig entry
100%
100%
buildconfig entry format
100%
100%
mach update-buildconfig command
0%
100%
taskcluster config update
28%
100%
PascalCase class name
100%
100%
Lib module test patterns and README conventions
StandardTestDispatcher usage
0%
0%
Dispatcher injection in tests
0%
0%
runTest with dispatcher
0%
0%
advanceUntilIdle usage
0%
0%
Callback tracking over mocks
87%
100%
Backtick test names
100%
100%
Robolectric sdk=35
0%
100%
README breadcrumb title
0%
75%
README usage section
100%
100%
README MPL footer
100%
100%
@VisibleForTesting annotation
100%
100%
mach gradle in commands
0%
100%
Concept module api dependency type and naming conventions
api dependency type
100%
100%
No implementation for exports
100%
100%
Package name no hyphens
100%
100%
Namespace no hyphens
100%
100%
PascalCase class names
100%
100%
LifecycleAwareFeature implemented
50%
70%
Dependency injection pattern
0%
0%
MPL header on Kotlin files
100%
100%
MPL header on AndroidManifest
100%
100%
Minimal manifest
100%
100%
publish true in buildconfig
0%
100%
Module name kebab-case
100%
100%
cd457f4
Table of Contents
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.