Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingxling/go
Language-specific super-code guidelines for go.
Passed 23 of 24 test cases with the skill, and 22 of 24 without it.
1 fixed22 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We have a slice of user structs and need to extract user IDs into a '[]string' slice. I noticed a code review suggestion to initialize 'var ids []string' and append items inside a loop over 10,000 items. How should this slice be initialized for maximum efficiency before appending? Show the refactored Go function.
| Checked | Without skill | With skill |
|---|---|---|
| The slice is initialized using make with a length of 0 and a capacity equal to the input slice length. | Missed | Passed |
The instructions your model reads when the skill loads.
// ❌ Ignoring errors
result, _ := os.Open(path)
// ✅ — always handle; only use _ when error is provably irrelevant
result, err := os.Open(path)
if err != nil {
return fmt.Errorf("open %s: %w", path, err)
}
// ❌ Redundant error variable
err := doA()
if err != nil { return err }
err = doB()
if err != nil { return err }
// ✅ — each :=/: is fine; this is idiomatic Go. Don't try to "fix" it.
// What you CAN simplify: collapsing to one-liners where the if body is a single return
if err := doA(); err != nil { return err }
if err := doB(); err != nil { return err }
test cases passed, vs 22 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.