Install any skill in seconds. Free to start, no credit card required.
Get Started Free →get-bb/repo-conventions
Conventions for working in this repository — commit style, branch naming, and testing expectations.
Passed 23 of 23 test cases with the skill, and 7 of 23 without it.
and 14 more in the full report
16 fixed7 passed either way0 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.
Can you explain the standard project rules for naming feature branches and writing commit logs in this codebase, as well as how to search our bundled documentation?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using 'bb docs search' to search local documentation. | Missed | Passed |
| Specifies feature branches must start with the 'bb/' prefix. | Missed | Passed |
| Requires commit logs to follow conventional commit standards. | Missed | Passed |
The instructions your model reads when the skill loads.
Search the bundled docs before guessing:
bb docs search "conventional commits"
feat(scope): summary).bb/<topic>.test cases passed, vs 7 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.