Install any skill in seconds. Free to start, no credit card required.
Get Started Free →google/add-source-file
How to add a new source file to the BoringSSL build.
Passed 20 of 21 test cases with the skill, and 3 of 21 without it.
and 23 more in the full report
18 fixed3 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where in the BoringSSL repository can a developer find the Go struct definitions that dictate the structure of the primary build JSON file?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies util/pregenerate/build.go as the location of the Go structs | Missed | Passed |
The instructions your model reads when the skill loads.
To add a new source file (C/C++, header, or assembly) to BoringSSL, you must update the build configuration and regenerate the build files.
Update build.json:
srcs, hdrs, internal_hdrs) under the appropriate target in build.json.build.json, refer to the Go structs in util/pregenerate/build.go.Update Pregenerated Files:
build.json, you must regenerate the build files.test cases passed, vs 3 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.