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.

69

Quality

83%

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%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, highly actionable workflow with concrete commands, specific file paths, and explicit validation checkpoints bracketing destructive operations like baseline removal.

DimensionReasoningScore

Conciseness

The body is a lean, numbered workflow of actionable bullets with only brief justifying rationale (e.g., "so baseline update scripts do not attempt to verify unsupported versions"); it assumes Claude's competence and avoids explaining concepts Claude already knows.

3 / 3

Actionability

It gives concrete, executable commands and exact targets — `./gradlew testClasses`, `git rm -r tool/baseline/<version>`, `sinceBuild=252`, `grep` over `src/` — making the guidance copy-paste ready rather than abstract.

3 / 3

Workflow Clarity

The 8-step sequence is clearly ordered with explicit validation checkpoints — a baseline `testClasses` run in step 1 and a full verify step (testClasses, test, verifyPlugin) in step 8 — matching the anchor for clear sequencing with validation.

3 / 3

Progressive Disclosure

The body is well under 50 lines, single-purpose, and cleanly organized into numbered sections with no need for external references; per the rubric's simple-skills note this earns a 3 on organization alone, and no bundle files exist to verify.

3 / 3

Total

12

/

12

Passed

Description

67%

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 distinctive about its narrow domain, but it omits explicit "when to use" trigger guidance, which caps completeness and weakens trigger-term quality.

Suggestions

Add a "Use when dropping or removing support for an IntelliJ Platform / Android Studio version (e.g., 2025.1/build 251)" clause to make the trigger explicit.

Include common natural variations such as "drop support", "deprecate", or "raise the compatibility lower bound" alongside the existing terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Remove support for an older IntelliJ Platform / Android Studio version" and "clean up obsolete code, baselines, and CI configurations" — matching the anchor for enumerating several specific actions rather than a single vague one.

3 / 3

Completeness

It clearly answers "what" the skill does but provides no "Use when..." or equivalent explicit trigger guidance for "when", which the rubric guidelines cap at 2.

2 / 3

Trigger Term Quality

It surfaces domain-relevant terms ("IntelliJ Platform / Android Studio version", "baselines", "CI configurations") but lacks common natural variations a user might say (e.g., "drop support", "deprecate platform version") and has no explicit trigger phrasing, so it is not a full 3.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and explicit — removing an IntelliJ Platform / Android Studio version — making it unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

10

/

12

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.