Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →famclaw/honeybadger-dev
How to add a scanner, lockfile parser, or rule to HoneyBadger, plus the test-fixture and self-check requirements.
Passed 21 of 23 test cases with the skill, and 3 of 23 without it.
and 24 more in the full report
19 fixed3 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are building a new scanner named 'container' to analyze OCI container images in HoneyBadger. What exact Go package directory should be created for this module?
| Checked | Without skill | With skill |
|---|---|---|
| Requires placing the package under internal/scanner/container/ | Missed | Passed |
The instructions your model reads when the skill loads.
internal/scanner/<name>/.internal/engine/engine.go (scanner list + verdict weighting).internal/testfixture/ — fixtures build secrets at runtime (never hardcoded) so GitHub push protection doesn't reject the push.internal/scanner/cve/deps.go.rules/ (embedded via rules/embed.go).internal/scanner/supplychain.internal/testfixture/ with secrets built at runtime.make build · make test · make self-check (scans itself) · go test -tags integration ./.... Open the PR against main.
test cases passed, vs 3 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.