android-tooling
Configure Static Analysis (Detekt, Ktlint) and CI/CD Checks for Android. Use when adding or tuning Detekt/Ktlint rules, setting Android Lint as a CI gate, suppressing lint warnings with @Suppress, or configuring code quality checks on pull requests. (triggers: build.gradle.kts, detekt.yml, .detekt/config.yml, detekt, ktlint, lint, @Suppress, abortOnError, jlleitschuh)
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/android/android-tooling/SKILL.mdQuality
Discovery
100%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 is an excellent skill description that clearly defines its scope around Android static analysis configuration. It provides specific actions, explicit 'Use when' guidance with multiple scenarios, and a comprehensive list of trigger terms including file names, tool names, and configuration keywords. The description is concise yet thorough, making it easy for Claude to select this skill precisely when needed.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring Detekt/Ktlint rules, setting Android Lint as a CI gate, suppressing lint warnings with @Suppress, and configuring code quality checks on pull requests. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure static analysis and CI/CD checks for Android) and 'when' (explicit 'Use when...' clause with multiple specific trigger scenarios), plus an additional parenthetical triggers list. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including tool names (detekt, ktlint, lint), file names (build.gradle.kts, detekt.yml, .detekt/config.yml), annotations (@Suppress), configuration keywords (abortOnError), and even a plugin author reference (jlleitschuh). These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Android static analysis tools (Detekt, Ktlint) and CI/CD integration. The specific tool names, file paths, and annotations make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, with good progressive disclosure to a reference file. However, it critically lacks actionability — there are no concrete code examples, configuration snippets, or executable commands for any of the tools mentioned (Detekt, Ktlint, Android Lint, CI pipelines). The workflow is also too vague to guide Claude through actual implementation.
Suggestions
Add concrete, executable configuration snippets: a minimal build.gradle.kts block showing Detekt/Ktlint plugin setup, a sample detekt.yml with key rules, and the lintOptions block with abortOnError = true.
Provide a clear step-by-step workflow for adding static analysis to a project (e.g., 1. Add plugin → 2. Configure rules → 3. Verify with `./gradlew detekt` → 4. Fix violations → 5. Add to CI).
Include a concrete example of when @Suppress is acceptable vs. not, and show the exact syntax for suppressing a specific Detekt rule if truly needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line conveys actionable information without explaining concepts Claude already knows. No padding or unnecessary context. | 3 / 3 |
Actionability | The content is almost entirely abstract direction with no concrete code, commands, or configuration examples. There are no executable snippets for build.gradle.kts configuration, detekt.yml setup, or CI pipeline configuration — just vague descriptions like 'Enforce code complexity rules' and 'Run full checks'. | 1 / 3 |
Workflow Clarity | There is no clear sequenced workflow for setting up static analysis or CI gates. The content lists categories (pre-commit, pipeline) but provides no steps, no validation checkpoints, and no feedback loops for when checks fail. | 1 / 3 |
Progressive Disclosure | The skill is a concise overview that appropriately delegates detailed configuration to a single reference file (references/implementation.md) with a clear one-level-deep link. The structure is well-organized with logical sections. | 3 / 3 |
Total | 8 / 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
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.