CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cleanup-unused-assets

Reduce plugin size by scanning resources/icons and removing unreferenced assets.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/cleanup-unused-assets/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 body is a well-sequenced, appropriately concise workflow with real validation around a destructive batch operation. The main gaps are the missing concrete command for the central reference-search step and the absence of an explicit error-recovery loop after deletion.

Suggestions

Provide a concrete reference-search command, e.g., 'rg -l "<asset-name>" src/ plugin.xml' or a loop that greps each asset filename against source and plugin.xml.

Add an explicit recovery step: if verifyPlugin or the plugin load check fails after deletion, restore the removed assets (e.g., via git checkout) before iterating.

Remove the duplication between the opening task sentence and the '## Objective' section to tighten token usage.

DimensionReasoningScore

Conciseness

The body is lean with concrete gradle commands and no explanations of concepts Claude already knows. However, the opening line 'You are tasked with reducing plugin size by removing unused icons, images, and resources' is duplicated verbatim by the '## Objective' section, a minor instance of padding that keeps it from anchor 5.

4 / 5

Actionability

Most steps are executable — specific commands ('./gradlew test', 'verifyPlugin', 'buildPlugin', 'testClasses') and paths ('resources/icons', 'plugin.xml') — but the core operation 'Check if each asset is referenced in code or plugin.xml' provides no concrete search command (e.g., a grep/ripgrep invocation). This is a minor gap consistent with anchor 4 rather than fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

A clear six-step sequence (baseline, scan, search, remove, verify, report) with validation checkpoints on both sides of the destructive deletion, so the destructive-operation cap does not apply. It stops short of anchor 5 because there is no explicit error-recovery loop, e.g., what to do if verifyPlugin fails after assets are deleted.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references (none exist in the bundle), and is well-organized into an Objective plus six numbered workflow sections. Per the simple-skills scoring note, this earns a 5 on organization alone.

5 / 5

Total

17

/

20

Passed

Description

53%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 communicates a clear, concrete purpose but reads as a bare 'what' statement. Its main weakness is the absence of any 'when to use' trigger guidance, which both caps completeness and leaves natural trigger synonyms ('unused icons', 'bloat') uncovered.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user wants to slim down a plugin, remove unused icons/assets, or reduce plugin size or bloat.'

Include natural synonyms users would actually say — 'unused icons', 'unused assets', 'bloat', 'clean up' — rather than only the technical term 'unreferenced assets'.

Optionally enumerate the asset types covered (icons, images, resources) in the description itself to strengthen specificity.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — 'scanning resources/icons' and 'removing unreferenced assets' — matching the 1-2 concrete actions anchor. It does not list several specific actions (e.g., verification or reporting steps), so it falls short of anchor 4.

3 / 5

Completeness

The 'what' is clear (scan resources/icons and remove unreferenced assets to reduce plugin size), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'plugin size', 'resources/icons', and 'unreferenced assets' are relevant keywords, but the natural phrases users would say — 'unused icons', 'unused assets', 'clean up', 'bloat' — are missing, and 'unreferenced' leans technical. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

'Reduce plugin size', 'resources/icons', and 'unreferenced assets' carve a fairly specific plugin-asset-cleanup niche with only minor overlap risk against generic cleanup skills. It lacks the explicit distinct trigger phrases of anchor 5.

4 / 5

Total

13

/

20

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

Validation for skill structure

No warnings or errors.

Repository

flutter/flutter-intellij

Path

.agents/skills/cleanup-unused-assets/SKILL.md

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.