CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

resolve-verification-issues

Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.) identified by ./gradlew verifyPlugin.

Quality

80%

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/resolve-verification-issues/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 a tight, well-sequenced workflow with concrete gradle commands and explicit validation at every stage, ending in clear reporting and review instructions. Its only real weaknesses are the redundant repetition of the objective and the under-specified fix step itself. It is a strong instruction-only skill body.

DimensionReasoningScore

Conciseness

The body is almost entirely lean directives and commands with no concept explanations, but the goal statement is repeated nearly verbatim three times ("You are tasked with eliminating plugin verification warnings and errors...", "## Objective / Eliminate plugin verification warnings and errors...", matching the frontmatter) — minor instances that could be trimmed.

4 / 5

Actionability

Concrete copy-paste commands appear at every step ("./gradlew testClasses", "./gradlew verifyPlugin", "./gradlew runIde") along with specific example phrasings for the report and commit message, but the core fix step is vague ("Resolve the specific issue in the current branch") with no common fix patterns for internal/override-only API usage.

4 / 5

Workflow Clarity

A clear six-step sequence (baseline, analyze, implement, verify, manual validation, report) with explicit validation checkpoints — re-running verifyPlugin to confirm the warning is gone, testClasses for compilation, and test for regressions — forms a complete feedback loop, matching the anchor 5 example's validate-and-confirm pattern.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and needs no external references; its content is organized into well-labeled numbered workflow sections, which per the simple-skill guideline merits a 5.

5 / 5

Total

18

/

20

Passed

Description

66%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 concrete and well-scoped, correctly naming the tool and the specific issue types users encounter in IntelliJ plugin development. Its main weakness is the absence of any explicit "Use when..." trigger clause, which both caps completeness and limits trigger coverage. Adding a trigger sentence would likely lift it from good to strong.

Suggestions

Add an explicit trigger clause, e.g. "Use when ./gradlew verifyPlugin reports warnings or errors, or when the user mentions plugin verification, internal API usage, or override-only API usage."

Include natural synonyms such as "plugin compatibility", "deprecated API", and " IntelliJ plugin validation" so users phrasing the problem differently still trigger the skill.

Briefly name one or two fix approaches (e.g. replacing internal API calls with supported alternatives) to sharpen the 'what' beyond the single verb "Eliminate".

DimensionReasoningScore

Specificity

Names the domain, the exact tool ("identified by ./gradlew verifyPlugin"), and concrete issue categories ("Internal API usage, Override-only API usage"), but offers only a single action verb ("Eliminate") with no fix strategies — specific with minor gaps, matching the anchor 4 example's level of detail.

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance; the "when" is only weakly implied by "identified by ./gradlew verifyPlugin", which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"plugin verification warnings", "Internal API usage", and "verifyPlugin" are the exact phrases a user hitting this problem would say, but common synonyms like "plugin compatibility" or "deprecated API" are absent — good coverage, a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche keyed to a specific gradle task ("./gradlew verifyPlugin") makes it mostly distinct with only minor overlap risk against generic gradle/build-fix skills; it lacks the explicit distinct triggers of the anchor 5 example.

4 / 5

Total

15

/

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/resolve-verification-issues/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.