migrate-intellij-util

Optimize memory usage, consistency, and performance by migrating standard Java/Kotlin classes to IntelliJ's specialized com.intellij.util implementations.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/migrate-intellij-util/SKILL.md

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 concise, well-structured workflow with explicit validation checkpoints and a clear candidate list. The main gap is actionability: migration steps give direction rather than copy-paste-ready code examples for each candidate replacement.

Suggestions

Add concrete before/after code snippets for at least the top migration candidates (e.g., `new ArrayList<>()` -> `new SmartList<>()`, `new HashMap<>()` -> `ContainerUtil.newHashMap()`).

Show the exact import lines to use (e.g., `import com.intellij.util.SmartList;`) so changes are copy-paste ready.

Optionally note the single external javadoc link as a reference source rather than an inline instruction so Claude knows it is optional reading.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: a short candidate list and a numbered workflow with concrete gradle commands, with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Provides concrete gradle commands and migration candidates, but the 'Migrate' step is direction ('Replace standard API with the equivalent') without copy-paste-ready code examples for each candidate.	2 / 3
Workflow Clarity	A clear six-step sequence with explicit baseline and verification checkpoints and a feedback-oriented verify step (test classes, run tests, manual test steps), which matches the score-3 anchor.	3 / 3
Progressive Disclosure	A simple skill under 50 lines with no need for external references; the well-organized sections (Objective, Candidates, Workflow) satisfy the simple-skills allowance for a score of 3.	3 / 3
	Total	11 / 12 Passed

Description

55%

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 clearly states a specific, distinctive capability but omits explicit trigger guidance for when Claude should use it. Adding a 'Use when...' clause and a few natural user-facing keywords would lift completeness and trigger quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when migrating standard Java/Kotlin collections/utilities to com.intellij.util equivalents in an IntelliJ plugin codebase.'

Add natural trigger terms users might say, such as 'IntelliJ plugin optimization', 'memory usage', or 'SmartList/ContainerUtil migration'.

List a few concrete migration actions in the description (e.g., 'replace ArrayList with SmartList, HashMap with ContainerUtil maps') to reach specificity 3.

Dimension	Reasoning	Score
Specificity	Names the domain (memory/consistency/performance) and a concrete action (migrating standard classes to com.intellij.util), but does not list multiple specific actions like the score-3 anchor does.	2 / 3
Completeness	Clearly states what the skill does, but lacks an explicit 'Use when...' clause telling Claude when to invoke it, which the rubric caps at 2.	2 / 3
Trigger Term Quality	Includes relevant technical terms ('com.intellij.util', 'Java/Kotlin classes') but lacks natural user phrasing variations and trigger keywords a user would actually say.	2 / 3
Distinctiveness Conflict Risk	The com.intellij.util migration niche is distinct and specific; it is unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 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: flutter/flutter-intellij
Path: .agents/skills/migrate-intellij-util/SKILL.md
Commit: 21aaf0b

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