CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/remove-platform-version/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A tight, actionable, well-sequenced workflow that covers the full removal process (compatibility bounds, CI, baselines, dead code, issues, changelog, verification) with concrete commands and file paths. The main gaps are the absence of an explicit failure-recovery loop after the final verification step and a couple of search steps that could be given as exact commands.

DimensionReasoningScore

Conciseness

The body is directive and free of concept explanations Claude already knows, with concrete file paths and commands. Minor over-explanation remains: the 'You are tasked with...' intro and '## Objective' section restate what the numbered workflow already specifies, keeping it just below the lean 5 anchor.

4 / 5

Actionability

Mostly executable guidance: exact commands ('./gradlew testClasses', 'git rm -r tool/baseline/<version>', './gradlew verifyPlugin') and precise file paths (gradle.properties, tool/github.sh, .gemini/styleguide.md). A few steps (grep for version strings, GitHub issue search) are described rather than given as copy-paste commands, so it falls short of fully copy-paste-ready 5.

4 / 5

Workflow Clarity

A clear, logically ordered 8-step sequence with a baseline compile check up front (step 1) and an explicit final validation step (step 8: testClasses, test, verifyPlugin). Because this is destructive/batch work (code deletion, baseline removal) it lacks an explicit error-recovery feedback loop, so it sits at the 'most checkpoints present; minor validation gaps' anchor rather than 5.

4 / 5

Progressive Disclosure

This is a single-file skill: no references/, scripts/, or assets/ bundle exists, the body is under 50 lines, and it has well-organized section headers with no external references needed — per the rubric guideline this earns a 5 on organization alone.

5 / 5

Total

17

/

20

Passed

Description

70%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.

A specific, well-scoped description with concrete actions and strong distinctiveness, undermined by the complete absence of trigger guidance. Adding a 'Use when...' clause (e.g., when dropping support for an IDE version) would materially improve it.

Suggestions

Add an explicit trigger clause such as 'Use when dropping support for an older IntelliJ Platform or Android Studio version, or when raising the minimum supported build (sinceBuild).' to fix the missing 'when'.

Include common user phrasings and synonyms in the trigger (e.g., "drop support", "deprecate", "raise the minimum version", "sinceBuild") to improve trigger term coverage.

Optionally mention updating the compatibility range and changelog in the 'what' portion to make the capability list fully comprehensive.

DimensionReasoningScore

Specificity

The description names the domain ("IntelliJ Platform / Android Studio version") and several concrete actions ("Remove support", "clean up obsolete code, baselines, and CI configurations"), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because it omits actions the skill actually covers (changelog updates, compatibility-range bump, issue checks).

4 / 5

Completeness

It has a clear 'what' (remove support for an older platform version and clean up code, baselines, and CI configs) but no 'when' — there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "remove support", "IntelliJ Platform", "Android Studio", "version", "CI configurations" are phrases users would plausibly say. A few natural variants are missing ("drop support", "deprecate", "sinceBuild", "compatibility range"), keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The description targets a clear niche (IntelliJ/Android Studio plugin platform-version removal) with distinct triggers, so it is unlikely to fire for unrelated skills — matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

16

/

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/remove-platform-version/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.