verify-eap-compatibility

Ensure the plugin remains compatible with the latest IntelliJ Platform releases and EAP (Early Access Program) builds.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/verify-eap-compatibility/SKILL.md

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, fully actionable verification workflow with concrete commands, a clear sequence, and an implicit validate-fix loop. The only minor redundancy is the 'Objective' section restating the description.

Dimension	Reasoning	Score
Conciseness	The body is lean and instruction-only with no concept-explaining padding; it assumes Claude's competence and every line earns its place, though the 'Objective' section lightly restates the description.	3 / 3
Actionability	It gives concrete executable Gradle commands (testClasses, verifyPlugin, test) and names exact files (gradle.properties, plugin.xml) with the specific XML attribute to inspect, making guidance copy-paste ready.	3 / 3
Workflow Clarity	A clear 5-step sequence is present with an explicit verification step (#2) and a fix-and-resolve feedback step (#4) that closes the loop on EAP incompatibilities.	3 / 3
Progressive Disclosure	This is a short single-purpose skill under 50 lines with well-organized sections and no need for external references, satisfying the simple-skill allowance for a top score.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 clear and domain-specific but stops at a single action with no explicit trigger clause. Adding a 'Use when...' sentence and naming concrete actions (e.g., update target version, run verification, adjust until-build bounds) would raise it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user upgrades the IntelliJ Platform, targets an EAP build, or hits binary-compatibility errors after an IDE update.'

Enumerate concrete actions (update gradle.properties target, run verifyPlugin/test, adjust until-build bounds) rather than the single 'ensure compatible' action.

Include natural user-sayable variations like 'IntelliJ update', 'new IDE version', or 'upgrade plugin' alongside 'EAP'.

Dimension	Reasoning	Score
Specificity	It names the domain and one core action ("Ensure the plugin remains compatible"), but does not list multiple specific concrete actions like the level-3 anchor requires.	2 / 3
Completeness	It clearly states what the skill does but provides no explicit "Use when..." trigger guidance, so the 'when' is only implied and completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	It includes relevant terms ("IntelliJ Platform", "EAP", "Early Access Program", "compatibility") but misses common natural variations such as "IntelliJ update" or "upgrade the plugin".	2 / 3
Distinctiveness Conflict Risk	The IntelliJ Platform / EAP compatibility niche is distinct and specific, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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/verify-eap-compatibility/SKILL.md
Commit: 21aaf0b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.