Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vstorm-co/performant-code
Writing efficient code that handles large data and tight constraints
Passed 24 of 24 test cases with the skill, and 22 of 24 without it.
2 fixed22 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.
We are building a latency-critical C data parser with gcc. Currently no optimization flags are specified in the Makefile. Which standard gcc flag level should be applied to enable production compiler optimizations?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using the -O2 compiler optimization flag. | Missed | Passed |
The instructions your model reads when the skill loads.
How to write code that won't timeout on large inputs.
Before writing code, ask: how big is the data?
| Data size | Approach |
|---|---|
| < 1 MB | Load into memory, any approach works |
| 1-100 MB | Load into memory, but use efficient algorithms |
| 100 MB - 1 GB | Stream/mmap, avoid loading entirely into memory |
| > 1 GB | Streaming only, chunk-based processing |
mmap(), Python: mmap.mmap()) — map file into memory, OS handles pagingfread() in C, open(f, 'rb').read(chunk) in Pythonfgets() when you need random accesswrite() for every bytefwrite() or sys.stdout.buffer.write() for binary outputmmap() for large file access-O2 or -O3 for compiler optimizationstest cases passed, vs 22 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.