Add Flutter Docusaurus Locale
matthiasn/lotti
Add, complete, or audit a locale across a Flutter application's ARB catalogs and a localized Docusaurus manual, including generated localization code, locale selectors, native platform declarations…
Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.) identified by ./gradlew verifyPlugin.
Install Resolve Verification Issues
$ npx skills add flutter/flutter-intellij --skill resolve-verification-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install flutter/flutter-intellij resolve-verification-issues --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/flutter/flutter-intellij.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/resolve-verification-issues .claude/skills/resolve-verification-issues && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "resolve-verification-issues" agent skill from https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/resolve-verification-issues into .claude/skills/resolve-verification-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-verification-issues", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/resolve-verification-issuesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add flutter/flutter-intellij --skill resolve-verification-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install flutter/flutter-intellij resolve-verification-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter-intellij.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/resolve-verification-issues .agents/skills/resolve-verification-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "resolve-verification-issues" agent skill from https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/resolve-verification-issues into .agents/skills/resolve-verification-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-verification-issues", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flutter/flutter-intellij --skill resolve-verification-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install flutter/flutter-intellij resolve-verification-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter-intellij.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/resolve-verification-issues .cursor/skills/resolve-verification-issues && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "resolve-verification-issues" agent skill from https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/resolve-verification-issues into .cursor/skills/resolve-verification-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-verification-issues", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/flutter/flutter-intellij.git --path .agents/skills/resolve-verification-issues--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add flutter/flutter-intellij --skill resolve-verification-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install flutter/flutter-intellij resolve-verification-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter-intellij.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/resolve-verification-issues .gemini/skills/resolve-verification-issues && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "resolve-verification-issues" agent skill from https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/resolve-verification-issues into .gemini/skills/resolve-verification-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-verification-issues", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install flutter/flutter-intellij resolve-verification-issuesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add flutter/flutter-intellij --skill resolve-verification-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/flutter/flutter-intellij.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/resolve-verification-issues .github/skills/resolve-verification-issues && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "resolve-verification-issues" agent skill from https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/resolve-verification-issues into .github/skills/resolve-verification-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-verification-issues", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flutter/flutter-intellij --skill resolve-verification-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install flutter/flutter-intellij resolve-verification-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter-intellij.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/resolve-verification-issues .opencode/skills/resolve-verification-issues && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "resolve-verification-issues" agent skill from https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/resolve-verification-issues into .opencode/skills/resolve-verification-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-verification-issues", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
resolve-verification-issues- GitHub stars
- 2k
- Token cost
- ~525 tokens
- SKILL.md length
- 258 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.) identified by ./gradlew verifyPlugin.
- Works in 6 steps: Baseline → Analyze Report → Implement Fix → …
- Tasks that involve Cross-platform mobile apps
- SKILL.md covers Objective and Workflow Instructions
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Resolve Verification Issues is an agent skill from flutter/flutter-intellij. Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.) identified by ./gradlew verifyPlugin.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Mobile, covering Cross-platform mobile apps. It works with Flutter. The repository describes itself as: Flutter Plugin for IntelliJ. The licence is BSD-3-Clause.
When your agent uses it
- Tasks that involve Cross-platform mobile apps
Example prompts
- “/resolve-verification-issues”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit de31ba6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Resolve Verification Issues loads about 525 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 258 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from flutter/flutter-intellij at commit de31ba6, republished under its BSD-3-Clause licence (© flutter). 258 words, ~525 tokens.
Download SKILL.mdSave it as
.claude/skills/resolve-verification-issues/SKILL.md (or your agent's skills folder).- name
- resolve-verification-issues
- description
- Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.) identified by ./gradlew verifyPlugin.
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 testClassesto ensure project compiles. - Run
./gradlew testand./gradlew verifyPluginto 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 testClassesto ensure no new compilation errors. - Run
./gradlew verifyPluginagain to confirm the specific warning is gone and quantify the improvement. - Run
./gradlew testto 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
verifyPluginissues (e.g., "Total remaining issues: X compatibility warnings, Y internal API usages"). - Confirm that
./gradlew runIdevalidation 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").
© flutter, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/resolve-verification-issues of flutter/flutter-intellij.
Open the folder on GitHubat commit de31ba6
Compare with similar skills
Resolve Verification Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Resolve Verification Issues this skillflutter/flutter-intellij | 2k | — | ~525 | Automated safety check: Pass | BSD-3-Clause | |
| Add Flutter Docusaurus Localematthiasn/lotti | 1.2k | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| Tm Launcher DesignFar-Se/tabame | 372 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Mobile App UI Designceorkm/mobile-app-ui-design | 400 | — | ~2k | Automated safety check: Pass | None | |
| Marionette Flutter Drive Appleancodepl/marionette_mcp | 473 | — | ~11k | Automated safety check: Pass | Apache-2.0 | |
| Flutter ScreenshotJustLookAtNow/pt_mate | 503 | — | ~511 | Automated safety check: Pass | MIT |
Similar skills
Tm Launcher Design
Far-Se/tabame
Create or revise Tabame's Flutter launcher designs: frames, search bars, result rows, palettes, typography, and action dialogs.
Mobile App UI Design
ceorkm/mobile-app-ui-design
Design high-quality mobile app UI/UX screens, flows, and components.
Marionette Flutter Drive App
leancodepl/marionette_mcp
Set up and drive a running Flutter app (debug or profile) with Marionette — an AI agent's hands and eyes for the app.
Flutter Screenshot
JustLookAtNow/pt_mate
Capture and show two Flutter UI screenshots for this project: one landscape/large-screen preview and one portrait/mobile preview, without using Flutter Web.
Flutter Init
bear2u/my-skills
A skill your agent uses when user wants to create a new Flutter project (Todo/Habit/Note/Expense/Custom domain) with Clean Architecture, Riverpod 3.0, Drift, and modern Flutter stack
More from flutter/flutter-intellij
All 14 skills in this repoRelease Plugin
flutter/flutter-intellij
Prepare and execute a new release for the flutter-intellij plugin, including updating dependencies, compatibility bounds, changelogs, and verification.
Add Missing Unit Test
flutter/flutter-intellij
Add a new unit test for a class that currently lacks one or add a new test case to an existing test file, verifying improvement with Kover.
Audit Accessibility
flutter/flutter-intellij
Ensure the plugin's custom UI components are accessible to users with screen readers and other assistive technologies.
Audit Dependencies
flutter/flutter-intellij
Optimize plugin size and security by removing unused dependencies and updating outdated libraries.
Audit UI Thread Safety
flutter/flutter-intellij
Prevent UI freezes and ensure a responsive user experience by validating threading rules and migrating blocking calls off the Event Dispatch Thread (EDT).
Cleanup Code Inspections
flutter/flutter-intellij
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
Related
Works with
Categories
Questions about Resolve Verification Issues
What does Resolve Verification Issues do?
Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.) identified by ./gradlew verifyPlugin. Resolve Verification Issues is an agent skill from flutter/flutter-intellij./gradlew verifyPlugin.
When should I use Resolve Verification Issues?
Resolve Verification Issues fits situations like: tasks that involve Cross-platform mobile apps.
How do I install Resolve Verification Issues in Claude Code?
Run `npx skills add flutter/flutter-intellij --skill resolve-verification-issues -a claude-code`. Or copy the skill folder (.agents/skills/resolve-verification-issues in flutter/flutter-intellij) into .claude/skills/resolve-verification-issues in your project. Claude Code loads it when a task matches its description.
How do I install Resolve Verification Issues in Codex?
Run `npx skills add flutter/flutter-intellij --skill resolve-verification-issues -a codex`. Or copy the skill folder (.agents/skills/resolve-verification-issues in flutter/flutter-intellij) into .agents/skills/resolve-verification-issues in your project. Codex loads it when a task matches its description.
Can I use Resolve Verification Issues in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flutter/flutter-intellij --skill resolve-verification-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resolve-verification-issues, .gemini/skills/resolve-verification-issues, .github/skills/resolve-verification-issues and .opencode/skills/resolve-verification-issues in your project.
What does Resolve Verification Issues need to run?
SKILL.md names no scripts, command-line tools or credentials: Resolve Verification Issues is instructions for the agent only.
Does Resolve Verification Issues access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Resolve Verification Issues safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Resolve Verification Issues use?
Resolve Verification Issues is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Resolve Verification Issues use?
About 525 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Resolve Verification Issues?
Skills that share tags, products or a category with Resolve Verification Issues: Add Flutter Docusaurus Locale (matthiasn/lotti, 1.2k stars), Tm Launcher Design (Far-Se/tabame, 372 stars), Mobile App UI Design (ceorkm/mobile-app-ui-design, 400 stars) and Marionette Flutter Drive App (leancodepl/marionette_mcp, 473 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Resolve Verification Issues?
flutter (a GitHub organization) maintains it in flutter/flutter-intellij, which has 2,017 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 8, 2026.
Source: flutter/flutter-intellij on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.