android-tooling
Configure static analysis with Detekt, Ktlint, and Android Lint for CI/CD quality gates. Use when adding lint rules, configuring code quality checks, or setting up analysis as a CI gate.
81
78%
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 a strong skill description that clearly identifies the domain (static analysis for Android/Kotlin projects), names specific tools, and provides an explicit 'Use when' clause with natural trigger terms. It is concise, uses third-person voice, and is highly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring static analysis with named tools (Detekt, Ktlint, Android Lint), setting up CI/CD quality gates, adding lint rules, and configuring code quality checks. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure static analysis with Detekt, Ktlint, and Android Lint for CI/CD quality gates) and 'when' (explicit 'Use when' clause covering adding lint rules, configuring code quality checks, or setting up analysis as a CI gate). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Detekt', 'Ktlint', 'Android Lint', 'lint rules', 'code quality checks', 'CI gate', 'static analysis', 'CI/CD'. These cover the main terms a developer would use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific tool names (Detekt, Ktlint, Android Lint) and a clear niche in static analysis configuration for CI/CD. Unlikely to conflict with general coding or CI/CD skills due to the specificity of the tools and domain. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%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 actionable, executable content — no Gradle snippets, no CLI commands, no configuration file examples. It reads more like a policy document than an instructional skill that Claude can act on.
Suggestions
Add concrete Gradle configuration snippets for Detekt, Ktlint (jlleitschuh plugin), and Android Lint (e.g., the `android { lintOptions { abortOnError true } }` block).
Include specific CLI commands for running each tool (e.g., `./gradlew detekt`, `./gradlew ktlintCheck`) so Claude can execute them directly.
Add a brief example of a CI pipeline step or pre-commit hook configuration to make the CI Gates section actionable rather than descriptive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line conveys actionable configuration guidance without explaining what static analysis is or how CI/CD works. No unnecessary padding. | 3 / 3 |
Actionability | The skill describes what tools to use and general policies but provides no concrete code, Gradle configuration snippets, or executable commands. 'Use jlleitschuh plugin' and 'abortOnError = true' are mentioned but not shown in context of actual build files. | 1 / 3 |
Workflow Clarity | There is a basic two-stage workflow (pre-commit vs pipeline) and the sequence is implied, but there are no explicit validation checkpoints, no feedback loops for when checks fail, and no step-by-step process for setting up or running the analysis. | 2 / 3 |
Progressive Disclosure | The skill provides a concise overview and appropriately delegates detailed configuration to a single reference file (references/implementation.md) with a clear link. One level deep, well-signaled. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- 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.