Flutter Plugin for IntelliJ is an IntelliJ plugin that adds support for developing Flutter applications, which can run on iOS, Android, and the web. It is used by Flutter developers working in IntelliJ IDEA or Android Studio.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add flutter/flutter-intellij --skill resolve-verification-issuesgit clone --depth 1 https://github.com/flutter/flutter-intellijWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/flutter/flutter-intellij/resolve-verification-issues)<a href="https://agentmods.dev/skills/flutter/flutter-intellij/resolve-verification-issues"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/resolve-verification-issues/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/flutter/flutter-intellij/resolve-verification-issues"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/resolve-verification-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00468 |
| Opus 5.5 | $0.00013 | $0.00187 |
| Sonnet 5.5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
resolve-verification-issues scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
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").
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 43 lines · 33 tokens per session scan A 08df054da2c5
resolve-verification-issues is a skill published in the GitHub repository flutter/flutter-intellij (2,019 stars, last pushed today), licensed BSD-3-Clause. It adds 33 tokens to every session and 468 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
nullaway
Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.
tika-eval-encoding-regression
Condensed tika-eval pattern for charset-detector regression hunts ("A picks encoding X, B picks Y") using one build and two configs — encoding-pair flip queries, OOV/languageness/FFFD signals, per-file detector attribution.
wxjava-troubleshooter
A troubleshooting guide for WxJava, a Java library used to connect applications to WeChat services. It organizes problems involving setup, access tokens, signatures, payment certificates, callbacks, data conversion, network requests, and multiple accounts.
dev-fix
Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
cyber-triage
Evidence-led blue incident triage with authorization, runtime gates, and optional isolated lab retest handoff.