Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingxling/cpp
Language-specific super-code guidelines for cpp.
Passed 22 of 22 test cases with the skill, and 20 of 22 without it.
and 1 more in the full report
2 fixed20 passed either way0 still failing0 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.
Here is a C++ class implementation that handles background processing, resource cleanup in destructors, and exception catching. I suspect it has hidden performance overheads and exception safety bugs. Please review and rewrite the class using modern C++ best practices, providing the updated code block and explaining what was fixed.
| Checked | Without skill | With skill |
|---|---|---|
| Uses std::scoped_lock for thread locking. | Missed | Passed |
| Declares destructors with noexcept. | Missed | Passed |
The instructions your model reads when the skill loads.
// ❌ Raw new/delete
Widget* w = new Widget();
// ... 15 lines later ...
delete w;
// ✅
auto w = std::make_unique<Widget>();
// ❌ Shared ownership when unique suffices
auto w = std::make_shared<Widget>();
transfer(w); // only one owner
// ✅ — unique_ptr; move when transferring
auto w = std::make_unique<Widget>();
transfer(std::move(w));
// ❌ new[] for dynamic arrays
test cases passed, vs 20 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.