resolve-verification-issues

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

Quality

63%

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

Quality

Content

70%

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 well-sequenced workflow with strong validation checkpoints and concrete verification commands, but its actual fix-implementation step is vague and the Objective section redundantly restates the description. Tightening the duplication and specifying how to resolve flagged API usages would improve it.

Suggestions

Replace the vague 'Resolve the specific issue' with concrete resolution techniques (e.g., substitute a supported API, add the appropriate @OverrideOnly/@RequiresApi annotation, or suppress with justification).

Remove the redundant '## Objective' section and opening line that restate the frontmatter description to improve conciseness.

Add an explicit feedback loop in the Verify step ('if the warning persists, re-analyze and repeat Implement/Verify') to make error recovery explicit.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands, but the '## Objective' section and opening line restate the frontmatter description, and several commands repeat across steps, so it could be tightened rather than earning a 3.	2 / 3
Actionability	It provides concrete, executable gradle commands and example outputs (commit message, navigation paths), but the core 'Implement Fix' step only says 'Resolve the specific issue' without explaining how to actually resolve an Internal/Override-only API usage, leaving a key detail missing.	2 / 3
Workflow Clarity	A clear six-step sequence is given with explicit validation checkpoints (testClasses, test, verifyPlugin re-run) and a final verification/report stage, matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	The skill is under 50 lines, single-purpose, and has no bundle files; per the simple-skills note its well-organized numbered sections are sufficient for a top progressive-disclosure score.	3 / 3
	Total	10 / 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 specific and distinctive, naming concrete issue types and the exact tool, but it omits any explicit 'when to use' trigger guidance and relies on somewhat technical jargon. Adding a 'Use when...' clause would raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause such as 'Use when the user runs ./gradlew verifyPlugin and reports Internal API or Override-only API warnings.'

Soften jargon by adding common phrasings users might say (e.g., 'plugin compatibility warnings', 'intellij plugin API errors') alongside the technical terms.

Expand beyond the single 'Eliminate' verb to name the concrete resolution actions (e.g., 'replace, suppress, or annotate flagged API usages') to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('plugin verification warnings and errors'), concrete issue categories ('Internal API usage, Override-only API usage'), and the tool ('./gradlew verifyPlugin'), but offers only a single action verb ('Eliminate') rather than multiple concrete actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	It clearly answers 'what' (eliminate verification warnings/errors) but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant domain keywords like 'plugin verification' and 'verifyPlugin' appear, but the terms are fairly technical ('Override-only API usage', './gradlew verifyPlugin') and miss common user phrasings, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The scope is a clear, narrow niche (IntelliJ plugin verification via ./gradlew verifyPlugin with specific API-usage issue types) that is 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/resolve-verification-issues/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.