CtrlK
BlogDocsLog inGet started
Tessl Logo

cleanup-code-inspections

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

59

Quality

67%

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-code-inspections/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 tight, actionable 7-step workflow with explicit validation and feedback checks, well-organized for a single-file skill. The only drag is the duplicated objective statement that costs a conciseness point.

Suggestions

Remove the duplicated purpose: drop the standalone intro line or the '## Objective' section so the description appears once, keeping only the actionable workflow.

DimensionReasoningScore

Conciseness

The workflow steps are lean and command-driven, but the frontmatter description is duplicated verbatim as both the intro line and the '## Objective' section, which is unnecessary padding.

2 / 3

Actionability

Provides concrete executable commands (gradle tasks), a specific IDE menu path, a real suppression syntax example, and a commit-message template — all copy-paste ready.

3 / 3

Workflow Clarity

A clear 1–7 sequence with explicit validation checkpoints (baseline in step 1, verify in step 6 with re-run analysis to confirm the 'Yellow code' count decreased and no regressions).

3 / 3

Progressive Disclosure

Under 50 lines, single-file, no external references needed, with well-organized sections (Objective, numbered Workflow Instructions) — meeting the rubric's simple-skill allowance for a top score.

3 / 3

Total

11

/

12

Passed

Description

50%

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 states a clear purpose but stays at a middle quality level across all dimensions, with no explicit trigger guidance and only modest keyword coverage. It is distinguishable but not sharply differentiated from general refactoring skills.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g. 'Use when the user asks to fix lint/static analysis warnings, reduce code smells, or clean up inspection results.'

Broaden trigger terms to include natural variations users say: 'lint warnings', 'code smells', 'inspection results', 'IntelliJ inspections'.

Replace one abstract goal with a concrete action to lift specificity, e.g. 'Resolve IntelliJ static analysis warnings by applying quick-fixes and suppressing false positives.'

DimensionReasoningScore

Specificity

Names the domain and a concrete action ("resolving static analysis warnings") alongside two abstract goals ("Reduce technical debt and improve code quality"), but does not list multiple specific concrete actions like the 3-anchor example.

2 / 3

Completeness

Clearly states what the skill does, but lacks any "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes relevant natural terms ("technical debt", "static analysis warnings") but misses common variations a user might say ("lint", "code smell", "warnings").

2 / 3

Distinctiveness Conflict Risk

The "static analysis warnings" niche is fairly distinct, but the broad "reduce technical debt / improve code quality" framing could overlap with general refactoring skills.

2 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
flutter/flutter-intellij
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.