CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verify-eap-compatibility

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

Quality

68%

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/verify-eap-compatibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 compact, actionable workflow with concrete gradle commands and specific configuration targets, well-organized for a simple skill with no bundle files. Its main weaknesses are redundant restatement of the objective and missing workflow checkpoints — no instruction to restore the temporary gradle.properties change or to re-run verification after applying fixes.

Suggestions

Remove the duplicated objective: the "You are tasked with..." intro and "## Objective" section both restate the frontmatter description verbatim — keep only one.

Add a feedback loop to step 4 (e.g., "After fixing, re-run `./gradlew verifyPlugin` and `./gradlew test` until both pass") so resolution is verified rather than assumed.

Add an explicit step to revert the temporary `gradle.properties` EAP override once verification completes, since step 1 changes it only "temporarily" with no restore instruction.

DimensionReasoningScore

Conciseness

The workflow steps are lean and command-driven, but the objective is stated three times ("You are tasked with...", the "## Objective" section, and the frontmatter description), which is unnecessary padding that could be trimmed.

3 / 5

Actionability

Concrete executable commands (`./gradlew testClasses`, `./gradlew verifyPlugin`, `./gradlew test`) and exact file/attribute targets (`gradle.properties`, `plugin.xml`, `since-build`/`until-build`) are given, with minor gaps such as the specific gradle property name and an example EAP version string.

4 / 5

Workflow Clarity

A clear five-step numbered sequence with verification commands at each stage, but there are gaps: no feedback loop instructing re-running verification after fixes, and no step to revert the "temporarily" changed gradle.properties.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, has no bundle files, and no content that warrants external references; the section structure (numbered workflow steps under "Workflow Instructions") is well-organized, which merits a 5 under the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

48%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 domain-specific and distinct but under-specified: it states a goal rather than concrete capabilities and entirely lacks a "when to use" trigger clause. Adding an explicit usage trigger and naming the actual actions (verify, update bounds, fix incompatibilities) would move it into good-example territory.

Suggestions

Add an explicit trigger clause, e.g. "Use when a new IntelliJ Platform release or EAP build ships, when the user mentions EAP, or when verification against a new platform version fails."

Replace the goal statement with concrete actions: "Verify plugin compilation and binary compatibility against IntelliJ Platform EAP builds, update since-build/until-build bounds, and resolve incompatibilities."

Include natural trigger variations users would say, such as "IntelliJ IDEA", "plugin upgrade", or specific version numbers.

DimensionReasoningScore

Specificity

The description names the domain ("IntelliJ Platform releases and EAP (Early Access Program) builds") but the only action is the generic goal "Ensure the plugin remains compatible" — no concrete actions like updating version properties, running verification, or checking build bounds are stated.

2 / 5

Completeness

It clearly answers "what" (ensure plugin compatibility with platform releases/EAP builds) but has no "Use when..." clause or any explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "IntelliJ Platform", "EAP", and "Early Access Program" are present, but common variations users would naturally say ("IntelliJ IDEA", "plugin upgrade", "new version", "2024.x build") are missing.

3 / 5

Distinctiveness Conflict Risk

The EAP/platform-compatibility niche is fairly distinct with specific technical terms, with only minor overlap risk against generic plugin-maintenance or build skills.

4 / 5

Total

12

/

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/verify-eap-compatibility/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.