Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/zig-project
Modern Zig project architecture guide.
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
2 fixed18 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our Zig library, we are renaming `parse_json_fast` to `parseJson`. Should we keep `pub const parse_json_fast = parseJson;` so existing callers don't break immediately?
| Checked | Without skill | With skill |
|---|---|---|
| The response advises deleting the old function name completely without leaving alias constants. | Missed | Passed |
The instructions your model reads when the skill loads.
!T for explicit error handling, avoid anyerrorDelete unused code. Change directly. No compatibility layers.
// ❌ BAD: Deprecated function kept around
/// Deprecated: Use newFunction instead
pub fn oldFunction() void {
@compileLog("oldFunction is deprecated");
newFunction();
}
// ❌ BAD: Alias for renamed functions
pub const old_name = new_name; // "for backwards compatibility"
// ❌ BAD: Unused parameters
fn process(_: *const Config, data: []const u8) !void {
_ = data;
}
// ✅ GOOD: Just delete and update all usages
pub fn newFunction() void {
// ...
}
// ✅ GOOD: Remove unused parameters entirely
test cases passed, vs 19 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.