Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fzyzcjy/frb-cargokit
Explain how cargokit is sourced, copied, and analyzed inside flutter_rust_bridge.
Passed 20 of 22 test cases with the skill, and 4 of 22 without it.
and 23 more in the full report
16 fixed4 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
What flag used by the internal generation command in CI ensures that un-synchronized Cargokit copies fail the pull request check?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies `--set-exit-if-changed` as the flag that causes CI to fail when generated outputs or Cargokit copies drift. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill to avoid mixing together three different things: the external cargokit repository, the template submodule pointers in FRB, and copied cargokit files inside generated examples.
The main job is to determine which layer a change belongs to before analyzing whether the change is correct.
There are two important cargokit forms inside FRB:
External source
FRB depends on an external cargokit repository through git submodules under frb_codegen/assets/integration_template/**/cargokit.
Copied outputs
FRB commands such as integrate/generate often copy concrete cargokit files into frb_example/**/cargokit or frb_example/**/rust_builder/cargokit.
This means a large cargokit diff in examples often does not mean FRB designed a large new cargokit behavior. It may only mean a template or submodule change propagated into copied outputs.
Treat these paths as the source of truth when deciding cargokit behavior:
frb_codegen/assets/integration_template/app/rust_builder/cargokitfrb_codegen/assets/integration_template/plugin/cargokitTreat these paths as downstream copies unless the evidence shows otherwise:
frb_example/**/cargokit/**frb_example/**/rust_builder/cargokit/**Do not start by judging copied example files in isolation. First determine which source submodule pointer or template content produced them.
Use ./frb_internal sync-cargokit-copies to refresh checked-in Cargokit copies from the template submodules when those copies are not already regenerated by the integrate CI. The command mirrors the Rust integration template writer's Cargokit filtering and copied-file prelude.
Do not add flutter_via_create, flutter_via_integrate, or flutter_package to this sync map; the integrate generation CI already recreates those examples from templates. The CI Generate :: Internal job runs this as part of ./frb_internal generate-internal --set-exit-if-changed --coverage, so the normal generate-internal diff gate also catches Cargokit copy drift. If Cargokit copies drift, fix the source-of-truth template/submodule first when appropriate, run ./frb_internal sync-cargokit-copies, and commit the resulting copied-output refresh.
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.