Flutter Pub Release
MixinNetwork/flutter-plugins
Prepare and draft a pub.dev release for a package in the flutter-plugins monorepo.
Expertise in analyzing flake github issues in the flutter/flutter repository.
$ npx skills add flutter/flutter --skill analyze-github-flake -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install flutter/flutter analyze-github-flake --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.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/analyze-github-flake .claude/skills/analyze-github-flake && 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 "analyze-github-flake" agent skill from https://github.com/flutter/flutter/tree/master/.agents/skills/analyze-github-flake into .claude/skills/analyze-github-flake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-github-flake", 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/tree/master/.agents/skills/analyze-github-flakeType 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 --skill analyze-github-flake -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install flutter/flutter analyze-github-flake --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/analyze-github-flake .agents/skills/analyze-github-flake && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyze-github-flake" agent skill from https://github.com/flutter/flutter/tree/master/.agents/skills/analyze-github-flake into .agents/skills/analyze-github-flake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-github-flake", 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 --skill analyze-github-flake -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install flutter/flutter analyze-github-flake --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/analyze-github-flake .cursor/skills/analyze-github-flake && 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 "analyze-github-flake" agent skill from https://github.com/flutter/flutter/tree/master/.agents/skills/analyze-github-flake into .cursor/skills/analyze-github-flake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-github-flake", 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.git --path .agents/skills/analyze-github-flake--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 --skill analyze-github-flake -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install flutter/flutter analyze-github-flake --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/analyze-github-flake .gemini/skills/analyze-github-flake && 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 "analyze-github-flake" agent skill from https://github.com/flutter/flutter/tree/master/.agents/skills/analyze-github-flake into .gemini/skills/analyze-github-flake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-github-flake", 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 analyze-github-flakeInstalls 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 --skill analyze-github-flake -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/analyze-github-flake .github/skills/analyze-github-flake && 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 "analyze-github-flake" agent skill from https://github.com/flutter/flutter/tree/master/.agents/skills/analyze-github-flake into .github/skills/analyze-github-flake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-github-flake", 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 --skill analyze-github-flake -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 analyze-github-flake --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/analyze-github-flake .opencode/skills/analyze-github-flake && 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 "analyze-github-flake" agent skill from https://github.com/flutter/flutter/tree/master/.agents/skills/analyze-github-flake into .opencode/skills/analyze-github-flake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-github-flake", 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.
analyze-github-flakeExpertise in analyzing flake github issues in the flutter/flutter repository.
Analyze GitHub Flake is an agent skill from flutter/flutter. Expertise in analyzing flake github issues in the flutter/flutter repository. Use when a user wants to analyze the flakiness of a specific link to a flutter github issue.
Its SKILL.md is about 1.1k 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 and Failing and flaky tests. It works with GitHub, Flutter and Dart. The repository describes itself as: Flutter makes it easy and fast to build beautiful apps for mobile and beyond. The licence is BSD-3-Clause.
2 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9911f49. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
ghcurlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
ci.chromium.orgcr-buildbucket.appspot.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Analyze GitHub Flake loads about 1.1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 414 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.
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.
The full file from flutter/flutter at commit 9911f49, republished under its BSD-3-Clause licence (© flutter). 414 words, ~1,073 tokens.
.claude/skills/analyze-github-flake/SKILL.md (or your agent's skills folder).<!--
Host assumptions:
Installed and on path:
* dart
* git
* gh
Had authentication setup:
* gh
-->
Rules You should not modify ANY files - you are only to provide an analysis of why the specific check is flaking. You should only look at the issue body, as well as comments containing links to additional builds. You should not attempt to solve the flakes or pinpoint root causes inside of flutter/, just provide a high level summary of what is going on and bucket the failures into distinct types.
Github issue urls take the form of https://github.com/flutter/flutter/issues/<issue-number>. Where issue-number is a number.
Get information about the issue by using gh issue view <issue-number> --repo flutter/flutter --json=author,body,id,labels,number,state,title,url
For example to find information about the issue https://github.com/flutter/flutter/issues/174116 you can call gh issue view 174116 --repo flutter/flutter --json=author,body,id,labels,number,state,title,url
At this point there are two possible cases. If the issue
If the previous conditions are met, the title will contain the name of the flaking check, and the body will contain urls which link to instances where the check failed or flaked, each on a new line, directly after "Flaky builds:". You should also inspect the comments and find each comment made by "login": "fluttergithubbot", and extract the urls from there as well (the format will be the same, with an example flake at the top, and the full list immediately after the "Flaky builds:" header).
To find information about the specific failure take one of the urls listed in the issue body.
That link takes the format "https://ci.chromium.org/ui/p/flutter/builders/<bucket>/<check_name>/<buildNumber>/overview",
Example https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20plugin_test/16247/overview where prod is the <bucket>, Windows%20plugin_test is the <check_name> and 16247 is the <buildNumber>.
Then use the <buildNumber> to get the test logs metadata by running the following command.
curl 'https://cr-buildbucket.appspot.com/prpc/buildbucket.v2.Builds/GetBuild' \
-H 'accept: application/json' \
-H 'accept-language: en-US,en;q=0.9,es;q=0.8' \
-H 'cache-control: no-cache' \
-H 'content-type: application/json' \
-H 'origin: https://ci.chromium.org' \
-H 'pragma: no-cache' \
-H 'priority: u=1, i' \
-H 'referer: https://ci.chromium.org/' \
-H 'sec-ch-ua: "Chromium";v="146", "Not-A.Brand";v="24", "Google Chrome";v="146"' \
-H 'sec-ch-ua-mobile: ?0' \
-H 'sec-ch-ua-platform: "macOS"' \
-H 'sec-fetch-dest: empty' \
-H 'sec-fetch-mode: cors' \
-H 'sec-fetch-site: cross-site' \
-H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36' \
-H 'x-return-encrypted-headers: all' \
--data-raw '{"builder":{"project":"flutter","bucket":"<bucket>","builder":"<check_name>"},"buildNumber":<buildNumber>,"mask":{"fields":"id,builder,builderInfo,number,canceledBy,createdBy,createTime,startTime,endTime,cancelTime,status,statusDetails,summaryMarkdown,output,steps,tags,schedulingTimeout,executionTimeout,gracePeriod,ancestorIds,retriable"}}'Ignore the characters )]}' that start the response and treat the rest like json.
Inspect the content of the logs to determine the cause of the failure.
Do this for each of the urls in the issue body. Collect the logs for each of the specific failures, and categorize them by the type of failure in to a high level summary.
© 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
Just SKILL.md in .agents/skills/analyze-github-flake of flutter/flutter.
Open the folder on GitHubat commit 9911f49
Analyze GitHub Flake 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 |
|---|---|---|---|---|---|---|
| Analyze GitHub Flake this skillflutter/flutter | 179k | — | ~1.1k | Automated safety check: Pass | BSD-3-Clause | |
| Flutter Pub ReleaseMixinNetwork/flutter-plugins | 512 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Green GateVeryGoodOpenSource/vgv-ai-flutter-plugin | 170 | — | ~4.7k | Automated safety check: Notes | MIT | |
| Mock Call Count Retry Fallbackdivinevideo/divine-mobile | 266 | — | ~1.2k | Automated safety check: Pass | MPL-2.0 | |
| Mockito Stale Mock Silent Trycatch Failuredivinevideo/divine-mobile | 266 | — | ~1.4k | Automated safety check: Pass | MPL-2.0 | |
| MCP Debuggerdebugmcp/mcp-debugger | 173 | — | ~4.1k | Automated safety check: Pass | MIT |
MixinNetwork/flutter-plugins
Prepare and draft a pub.dev release for a package in the flutter-plugins monorepo.
VeryGoodOpenSource/vgv-ai-flutter-plugin
Drives a Dart or Flutter package fully green through a verify-fix-rerun loop across four gates: analyze, format, test, coverage.
divinevideo/divine-mobile
Fix test failures when adding retry/fallback logic causes mock call count mismatches.
divinevideo/divine-mobile
Fix misleading Flutter/Dart test failures where expected data is empty ([]) or default values instead of the mocked response, caused by stale Mockito generated mocks or missing stubs being silently…
debugmcp/mcp-debugger
A skill your agent uses when investigating a bug, failing test, or unexpected runtime behavior and the mcp-debugger MCP server is available — drives real step-through debuggers (breakpoints, stack…
MADTeacher/mad-agents-skills
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins.
flutter/flutter
Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44).
flutter/flutter
How to land a formal cherry-pick of a merged PR for the flutter/flutter repo stable or beta channel.
flutter/flutter
Upgrade browser versions (Chrome or Firefox) in the Flutter Web Engine and/or Framework tests.
flutter/flutter
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.
flutter/flutter
Do not trigger automatically; only run when a user runs /bump-dart.
flutter/flutter
Run DeviceLab tests for Flutter PRs using LUCI's led CLI tool.
Categories
Expertise in analyzing flake github issues in the flutter/flutter repository. Analyze GitHub Flake is an agent skill from flutter/flutter. Expertise in analyzing flake github issues in the flutter/flutter repository.
Analyze GitHub Flake fits situations like: A user wants to analyze the flakiness of a specific link to a flutter github issue; tasks that involve Cross-platform mobile apps; tasks that involve Failing and flaky tests.
Run `npx skills add flutter/flutter --skill analyze-github-flake -a claude-code`. Or copy the skill folder (.agents/skills/analyze-github-flake in flutter/flutter) into .claude/skills/analyze-github-flake in your project. Claude Code loads it when a task matches its description.
Run `npx skills add flutter/flutter --skill analyze-github-flake -a codex`. Or copy the skill folder (.agents/skills/analyze-github-flake in flutter/flutter) into .agents/skills/analyze-github-flake in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flutter/flutter --skill analyze-github-flake -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-github-flake, .gemini/skills/analyze-github-flake, .github/skills/analyze-github-flake and .opencode/skills/analyze-github-flake in your project.
Going by SKILL.md and its folder, Analyze GitHub Flake needs the command-line tools its instructions call (gh and curl).
SKILL.md names 2 domains. In commands or code: ci.chromium.org and cr-buildbucket.appspot.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
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.
Analyze GitHub Flake 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.
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Analyze GitHub Flake: Flutter Pub Release (MixinNetwork/flutter-plugins, 512 stars), Green Gate (VeryGoodOpenSource/vgv-ai-flutter-plugin, 170 stars), Mock Call Count Retry Fallback (divinevideo/divine-mobile, 266 stars) and Mockito Stale Mock Silent Trycatch Failure (divinevideo/divine-mobile, 266 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
flutter (a GitHub organization) maintains it in flutter/flutter, which has 179,269 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 10, 2026.
Source: flutter/flutter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.