security-cleanup-inspector

Removes app bloat, secures data, and ensures failures are visible. Use this skill to safely eliminate dead code or unused resources, secure vulnerabilities like hardcoded API keys, fix silent exceptions (empty catch blocks), convert heavy assets to WebP, and ensure logs do not contain PII.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%Weight 40%Scale 1-5

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

The content is well-structured, concise, and highly actionable with concrete Gradle commands and concrete replacements, plus a clear multi-step workflow with validation. The only minor gap is an explicit validate-fix-retry feedback loop, which keeps workflow clarity just below maximum.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no padding or explanation of basic concepts; every section (Constraints, Instructions, Examples) earns its place with actionable, direct content.	5 / 5
Actionability	It provides fully executable, specific guidance such as './gradlew ktfmtFormat', './gradlew lintDebug', 'Timber.e(e)' as a logger replacement, and concrete WebP/API-key moves, with examples covering the common cases.	5 / 5
Workflow Clarity	The SCAN/SELECT/SECURE/VERIFY/PRESENT sequence is clear with an approval checkpoint before destructive changes and a VERIFY step that builds and tests, but the validate->fix->retry feedback loop is implied rather than an explicit re-run loop, so it sits just below the top anchor.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external bundle files and is organized into clear, well-labeled sections (Goal, Constraints, Instructions, Examples), satisfying the simple-skill exception for a top score.	5 / 5
	Total	19 / 20 Passed

Description

88%Weight 40%Scale 1-5

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 is strong, explicitly covering what the skill does and when to use it with concrete, domain-specific triggers. Minor synonym coverage gaps and slight overlap risk with general cleanup skills keep it just below perfect on two dimensions.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('eliminate dead code or unused resources, secure vulnerabilities like hardcoded API keys, fix silent exceptions (empty catch blocks), convert heavy assets to WebP, and ensure logs do not contain PII'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	It explicitly states both what the skill does and when to use it via 'Use this skill to...' followed by concrete trigger conditions, matching the anchor that requires both what and when.	5 / 5
Trigger Term Quality	Natural user-facing terms like 'dead code', 'API keys', 'empty catch blocks', 'WebP', and 'PII' are present, but a few common variations or synonyms are missing, so it sits above the midpoint rather than at full coverage.	4 / 5
Distinctiveness Conflict Risk	The Android-focused security/cleanup niche with specific triggers (WebP, BuildConfig, Timber) is mostly distinct with only minor overlap risk against generic cleanup skills, fitting the 'mostly distinct' anchor rather than full niche clarity.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: nekomangaorg/Neko
Path: .agents/skills/inspector/SKILL.md
Commit: 9852a3f

Reviewed: 3 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.