Install any skill in seconds. Free to start, no credit card required.
Get Started Free →google/filament-build-clean
Clean and build Filament targets for development, debugging, and production.
Passed 19 of 20 test cases with the skill, and 6 of 20 without it.
and 13 more in the full report
16 fixed6 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am working on local interactive testing and step-debugging on my workstation. What exact script command should I run to compile Filament for desktop with debugging symbols included?
| Checked | Without skill | With skill |
|---|---|---|
| recommends ./build.sh -ip desktop debug | Missed | Passed |
The instructions your model reads when the skill loads.
This skill defines standard procedures and command configurations for cleaning build artifacts and compiling Filament targets on desktop platforms.
To completely reset the build environment and remove all compiled artifacts, caches, and generated files across all platforms:
./build.sh -C
For active development, local debugging, and interactive testing, compile the desktop target with debug symbols and no optimizations:
./build.sh -ip desktop debug
For performance analysis, optimizations, profiling, and running local benchmarks on desktop systems, compile the release build:
./build.sh -ip desktop release
For fast iteration you may invoke ninja directly against an existing build directory:
ninja -C out/cmake-debug <target>
Beware of the second build directory. Materials are not compiled by
out/cmake-debug/tools/matc/matc. Every material rule in build.ninja invokes the split-build
copy of the host tools at out/prebuilt-tools-release/tools/matc/matc. See
build_tools_for_split_build in build.sh; note that SPLIT_BUILD_TYPE defaults to release,
test cases passed, vs 6 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.