Resolve Verification Issues Agent Skill

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

524 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

2013

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/flutter/flutter-intellij --skill resolve-verification-issues

The instruction itself

9 sections, as written by the author

Skill: Resolve Plugin Verification Issues

You are tasked with eliminating plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.).

Objective

Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.).

Workflow Instructions

1. Baseline

Run ./gradlew testClasses to ensure project compiles.
Run ./gradlew test and ./gradlew verifyPlugin to establish a clean baseline.

2. Analyze Report

Identify distinct issues to resolve (e.g., "Override-only API usage in ClassX").

3. Implement Fix

Resolve the specific issue in the current branch.
Ensure the fix is minimal and targeted.

4. Verify Fix

Run ./gradlew testClasses to ensure no new compilation errors.
Run ./gradlew verifyPlugin again to confirm the specific warning is gone and quantify the improvement.
Run ./gradlew test to ensure no regressions.

5. Validation & Manual Testing

Explain how to verify the fix manually by running ./gradlew runIde.
Provide specific navigation steps for the user to reach the changed code within the plugin (e.g. "Open Settings > Languages & Frameworks > Flutter...").
Verify that the changes do not introduce runtime errors or regressions.

6. Report & Review

Summarize the remaining verifyPlugin issues (e.g., "Total remaining issues: X compatibility warnings, Y internal API usages").
Confirm that ./gradlew runIde validation passed.
Test Location: Explicitly state *where* in the IDE the user should go to test the changed functionality (e.g., "Go to Preferences > Languages & Frameworks > Flutter").
Action: Ask the user to review the fix closely.
Do not commit or push.
Provide a suggested Git commit message including specific counts (e.g., "Fix Internal API usage in ClassX: 5 experimental APIs used -> 4 experimental APIs used").

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take flutter/resolve-verification-issues from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.