Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fzyzcjy/frb-cargokit-dev
Develop or update CargoKit for flutter_rust_bridge.
Passed 22 of 22 test cases with the skill, and 13 of 22 without it.
and 10 more in the full report
9 fixed13 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I updated CargoKit submodules in flutter_rust_bridge and ran precommit integration. Is precommit integration sufficient before staging, or is there an additional lint step required before submitting a PR? What command runs the standard PR lint fix?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends running './frb_internal lint --fix' after regenerating integrate output. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when the actual fix belongs in the external fzyzcjy/Cargokit repository and FRB needs a follow-up PR that points its CargoKit submodules at the updated CargoKit branch or commit.
The usual shape is two PRs:
Do not implement CargoKit behavior only in copied FRB example output. The source of truth is the CargoKit repository referenced by the template submodules.
FRB embeds CargoKit as git submodules in two template locations:
frb_codegen/assets/integration_template/app/rust_builder/cargokitfrb_codegen/assets/integration_template/plugin/cargokitBoth submodules should normally point at the same CargoKit branch or commit for the same logical update. Downstream generated copies may appear under:
frb_example/**/cargokit/**frb_example/**/rust_builder/cargokit/**Read frb-cargokit first if you need to classify an existing diff before deciding where the change belongs.
Work in fzyzcjy/Cargokit for the actual CargoKit implementation.
If you are editing through an FRB submodule checkout, remember that commits belong to the nested CargoKit repository, not the outer FRB repository. Push the nested repository branch before updating the outer FRB submodule pointer.
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.