Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →flutter/flutter-pr-checks-finder
Find failing checks on a Flutter PR and locate the corresponding LUCI log URLs.
Passed 14 of 19 test cases with the skill, and 11 of 19 without it.
and 1 more in the full report
4 fixed12 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact step name string should be placed in the LUCI raw log URL path for a flutter_drone check with shard 'analyze' and no subshard?
| Checked | Without skill | With skill |
|---|---|---|
| The response includes run_test.dart_for_analyze_shard_and_subshard_None as the formatted step name | Missed | Passed |
The instructions your model reads when the skill loads.
gh (GitHub CLI) must be installed and authenticated. If not in your PATH, check common locations like /opt/homebrew/bin/gh on macOS or C:\Program Files\GitHub CLI\gh.exe on Windows.curl or similar tool to fetch raw logs from LUCI.You can use the gh CLI if it's installed and authenticated, or use direct HTTP requests to the GitHub API as a fallback.
gh CLI (Preferred)Run the following command to list checks:
gh pr checks <PR_NUMBER>
If gh is not available, you can use read_url_content or a similar method to interact with the public GitHub API:
https://api.github.com/repos/flutter/flutter/pulls/<PR_NUMBER>
Extract the head.sha field.https://api.github.com/repos/flutter/flutter/commits/<PR_SHA>/check-runs
Parse the JSON response. CRITICAL: You must handle pagination to avoid missing failures! Check the total_count field. If it is greater than the number of items in the check_runs array (typically capped at 100 or what you set with per_page), make additional HTTP requests by appending ?per_page=100&page=<N> to the URL for each subsequent page until all check runs are fetched. Identify all checks that have failed (i.e., where conclusion is failure).Identify all checks that have failed.
For each failing check:
flutter-dashboard link typically appears as "View more details on flutter-dashboard" at the bottom of the check view on GitHub.https://ci.chromium.org/ui/p/flutter/builders/try/<Builder Name>/<Build Number>/overview?format=raw to the log URL or by following the pattern: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/<Build ID>/+/u/<Step Name>/stdout?format=rawtest cases passed, vs 11 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.