CtrlK
BlogDocsLog inGet started
Tessl Logo

remove-platform-version

Remove support for an older IntelliJ Platform / Android Studio version from the project and clean up obsolete code, baselines, and CI configurations.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 content is concise, highly actionable, and well-structured with concrete commands, specific paths, and explicit validation checkpoints framing a clear multi-step workflow. No bundle files exist, which is appropriate for this self-contained skill.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — it assumes Claude's knowledge of gradle/Intelliit basics and devotes every line to actionable instruction with no padding or redundant explanation.

5 / 5

Actionability

Provides concrete executable commands ('./gradlew testClasses', 'git rm -r tool/baseline/<version>'), specific file paths ('gradle.properties', 'tool/github.sh'), and precise grep targets covering the common cases.

5 / 5

Workflow Clarity

Eight clearly sequenced steps with an explicit baseline checkpoint at the start and a dedicated validation step at the end (testClasses, test, verifyPlugin), giving proper feedback loops for this destructive batch operation.

5 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with no external bundle files, organized into clearly headed sections — meeting the rubric's exception that simple, self-contained skills can score 5 on well-organized structure alone.

5 / 5

Total

20

/

20

Passed

Description

75%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 is specific and clearly distinct, naming concrete cleanup actions for a niche task. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the invocation context only implied.

Suggestions

Add an explicit trigger clause such as 'Use when dropping support for an older IntelliJ Platform or Android Studio version (e.g., moving the lower bound from 2025.1 to 2025.2).'

Include a few more natural synonyms (e.g., 'platform compatibility range', 'sinceBuild') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (removing an older IntelliJ Platform / Android Studio version) and lists multiple concrete actions — 'remove support', 'clean up obsolete code, baselines, and CI configurations' — giving comprehensive coverage.

5 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause; the 'when' is only weakly implied, so per the rubric guidance completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('IntelliJ Platform', 'Android Studio', 'CI configurations', 'baselines') but lacks synonyms or file-extension variants, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (removing a specific platform version from an IntelliJ plugin project) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.