CtrlK
BlogDocsLog inGet started
Tessl Logo

migrate-intellij-util

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

61

Quality

71%

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

86%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-structured, highly actionable instruction-only skill with concrete commands and migration mappings, plus explicit verification steps. Minor conciseness redundancy and an implicit (rather than explicit) fix-retry loop are the only gaps.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation, but the intro line and the 'Objective' section redundantly restate the frontmatter description and the 'Go read [URL]' framing could be tightened.

4 / 5

Actionability

Provides concrete gradle commands, a specific class-migration mapping table, an explicit 50-line constraint, and a concrete report format with a commit-message example — fully actionable instruction-only guidance.

5 / 5

Workflow Clarity

A clear 6-step sequence with baseline and post-migration verification checkpoints (testClasses/test/verifyPlugin), but the fix-and-retry feedback loop is only implicit and no explicit checklist is provided.

4 / 5

Progressive Disclosure

Under 50 lines with no need for bundle files, organized into clear sections (Objective, Candidates, numbered Workflow); the simple-skill exception applies and one external javadoc link is clearly signaled.

5 / 5

Total

18

/

20

Passed

Description

57%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 clearly conveys a specific, distinctive niche but omits any explicit 'when to use' trigger guidance and relies on technical rather than natural-language keywords. It is actionable and distinct but not comprehensive on trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when developing IntelliJ plugins and you want to replace standard Java/Kotlin collections or utilities with com.intellij.util equivalents.'

Include natural-language trigger phrases users would say (e.g., 'migrate to IntelliJ util classes', 'use SmartList/ContainerUtil') alongside the technical terms.

Consider listing 2-3 concrete migration actions (e.g., 'replace collections with ContainerUtil, swap string checks for StringUtil') to lift specificity above a single action.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ('migrating standard Java/Kotlin classes to IntelliJ's specialized com.intellij.util implementations') plus three benefit goals, but lists only a single action rather than several specific ones.

3 / 5

Completeness

Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Contains strong technical keywords ('com.intellij.util', 'Java/Kotlin', 'IntelliJ') but lacks natural user-facing trigger phrasing and common synonyms a user would actually say.

3 / 5

Distinctiveness Conflict Risk

Targets a very specific niche (IntelliJ com.intellij.util migration) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

14

/

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.

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.