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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

The body is a lean, well-organized overview with a correctly signaled single-level reference, but its standalone guidance is incomplete — executable config and the mechanism for failing the build live only in the reference, and the CI-gate workflow lacks explicit validation/feedback steps.

Suggestions

Add a minimal executable snippet to the body (e.g. the Detekt Gradle plugin block or a one-line `./gradlew detekt ktlintCheck` command) so the overview is actionable without opening the reference.

Make the CI-gate workflow explicit: spell out the validation checkpoint (run checks → if violations, fix at source and re-run → only merge when green) rather than leaving the feedback loop implicit.

Tighten vague directives like 'Fail build on high complexity' with the concrete mechanism (e.g. `maxIssues: 0` in detekt.yml) so Claude knows exactly how to enforce the gate.

Dimension	Reasoning	Score
Conciseness	Lean bullet-point directives with no over-explanation of what Detekt/Ktlint/Android Lint are; every token earns its place and assumes Claude's competence, fitting the 'lean and efficient' anchor.	3 / 3
Actionability	Provides some concrete tokens (abortOnError = true, jlleitschuh, LongMethod/LargeClass) but no executable config in the body, and 'Fail build on high complexity' lacks the mechanism — key setup detail is deferred to the reference, matching the 'some concrete guidance but incomplete' anchor rather than fully copy-paste-ready.	2 / 3
Workflow Clarity	Presents a pre-commit → PR-pipeline sequence with an implicit fail-the-build gate, but lacks explicit validation checkpoints or a fix-and-retry feedback loop, matching the 'steps listed but validation gaps' anchor rather than the explicit-checkpoint score-3 anchor.	2 / 3
Progressive Disclosure	A clean overview split into Static Analysis, CI Gates, Anti-Patterns, and a single one-level-deep reference ([Configuration](references/implementation.md), verified to exist) holding the detailed config — well-signaled and easy to navigate.	3 / 3
	Total	10 / 12 Passed

Description

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.

A concise, well-constructed description that names specific tools and actions, supplies natural trigger terms, and gives an explicit 'Use when' clause for both what and when. It occupies a clear niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Names concrete tools (Detekt, Ktlint, Android Lint) and multiple specific actions — configure analysis, add lint rules, set up a CI gate — matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2 anchor.	3 / 3
Completeness	Explicitly states what it does ('Configure static analysis with Detekt, Ktlint, and Android Lint for CI/CD quality gates') and when to use it via an explicit 'Use when...' clause, satisfying both halves of the top anchor.	3 / 3
Trigger Term Quality	Includes natural terms a user would actually say — 'lint rules', 'code quality checks', 'Detekt', 'Ktlint', 'Android Lint', 'CI gate' — giving good coverage rather than just some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	Targets an Android-specific static-analysis niche with named tools and distinct triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Commit: 611f52a

Reviewed: 4 days 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.