CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

71%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 delivers a tight, actionable workflow with concrete gradle verification commands, specific migration candidates, and sensible constraints (single package, max 50 lines). Its main improvements are de-duplicating the repeated objective statement and adding a small before/after migration example plus an explicit failure-recovery step.

Suggestions

State the objective once and cut the duplicated mission phrasing from the intro and Objective sections to save tokens.

Add one short before/after code example of a real migration (e.g., 'new ArrayList<>()' -> 'new SmartList<>()' with the StringUtil.isNotEmpty null/empty check) so the migration pattern is unambiguous.

Add an explicit recovery step to the Verify section, e.g., 'If tests fail, revert the migration and re-run the baseline commands before trying a smaller scope.'

DimensionReasoningScore

Conciseness

The body is mostly lean, but the mission statement 'optimize memory usage, consistency, and performance by migrating standard Java/Kotlin classes to IntelliJ's specialized com.intellij.util implementations' is repeated nearly verbatim three times (intro, Objective, and echoing the description), which could be tightened to a single statement.

3 / 5

Actionability

Concrete executable commands are given (`./gradlew testClasses`, `./gradlew test`, `./gradlew verifyPlugin`), the candidate mappings are specific (ArrayList -> SmartList, javax.swing.Timer -> Alarm, etc.), and a hard 50-line constraint is imposed; the minor gap is the absence of a before/after code example showing an actual migration.

4 / 5

Workflow Clarity

A clear 6-step sequence (Baseline, Select Target, Constraint, Migrate, Verify, Report) with real validation checkpoints: tests are run before and after the change. It falls short of a 5 only because there is no explicit error-recovery loop (what to do if `./gradlew test` fails after migration).

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no bundle files needed and well-organized sections; the single external reference (the com.intellij.util javadoc URL) is clearly signaled and one level deep, matching the simple-skill exception for a top score.

5 / 5

Total

16

/

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, fairly niche capability (migrating Java/Kotlin code to IntelliJ's com.intellij.util utilities) but reads more like a task statement than a skill description. Its main weaknesses are the missing 'when to use' guidance and the reliance on abstract goals instead of concrete, natural trigger terms.

Suggestions

Add an explicit trigger clause, e.g., 'Use when developing IntelliJ Platform plugins and standard Java/Kotlin collection, string, or path handling could be replaced with com.intellij.util equivalents.'

Enumerate the concrete migration targets as trigger keywords (SmartList, ContainerUtil, StringUtil, PathUtil, ObjectUtils, ArrayUtil) so users mentioning those classes or terms naturally match.

Replace the abstract 'optimize memory usage, consistency, and performance' opening with the concrete action first, e.g., 'Migrate standard Java/Kotlin collections, strings, and null checks to IntelliJ's com.intellij.util utilities (SmartList, ContainerUtil, StringUtil) to reduce memory overhead in IntelliJ Platform plugins.'

DimensionReasoningScore

Specificity

The description names the domain ("migrating standard Java/Kotlin classes to IntelliJ's specialized com.intellij.util implementations") and one concrete action, but the goals "optimize memory usage, consistency, and performance" are abstract and no specific utilities (e.g., SmartList, StringUtil) are enumerated, so it does not reach the 'several specific actions' anchor.

3 / 5

Completeness

The 'what' is clear (migrate standard classes to com.intellij.util implementations), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "memory usage", "performance", "Java/Kotlin", "IntelliJ", and "com.intellij.util" are relevant, but common natural variations users would say ("IntelliJ plugin", "IDEA", specific class names like StringUtil or SmartList) are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The com.intellij.util migration niche is mostly distinct with minimal overlap against other skills, though the broad 'optimize memory usage and performance' phrasing creates minor overlap risk with generic performance-optimization skills, keeping it below a 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/migrate-intellij-util/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.