Best fit
- Use when the user asks to make something faster, try many variants, run recursive optimization, benchmark latency/throughput/cost, or choose the best implementation by repeated measured tests.
affaan-m/ECC
Use when the user asks to make something faster, try many variants, run recursive optimization, benchmark latency/throughput/cost, or choose the best implementation by repeated measured tests.
npx skills add https://github.com/affaan-m/ECC --skill "skills/benchmark-optimization-loop"Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Use this skill to convert "make it 20x faster" or "try 50 recursive optimizations" into a bounded measured loop that can actually improve a system.
npx skills add https://github.com/affaan-m/ECC --skill "skills/benchmark-optimization-loop"The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.
316 source words · 5 usable sections
Best fit
Source workflow
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
Do not optimize until these exist:
1. Measure the baseline. 2. Identify bottlenecks from evidence. 3. Generate variants that test one hypothesis each. 4. Run variants with the same input shape. 5. Reject variants that fail correctness, safety, or reproducibility. 6. Promote the fastest safe variant. 7. Codify the…
Track variants like this:
For recursive or hyperparameter work:
Source checklist
The source section “Required Baseline” has been checked.
The source section “Loop” has been checked.
The source section “Variant Table” has been checked.
The source section “Recursive Search” has been checked.
FAQ
Use this skill to convert "make it 20x faster" or "try 50 recursive optimizations" into a bounded measured loop that can actually improve a system.
The source record exposes this install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/benchmark-optimization-loop". Inspect the command and pinned source before running it.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Use this skill to convert "make it 20x faster" or "try 50 recursive optimizations" into a bounded measured loop that can actually improve a system.
Do not optimize until these exist:
If the user asks for an unrealistic target, keep the ambition but make the loop bounded and measurable.
Track variants like this:
Variant | Hypothesis | Command | Time | Correct? | Notes
baseline | current path | npm run job | 120s | yes | stable
batch-500 | fewer round trips | npm run job -- --batch 500 | 42s | yes | winner
parallel-8 | more workers | npm run job -- --workers 8 | 31s | no | rate limited
For recursive or hyperparameter work:
Use phrases like "best measured safe variant" instead of "global optimum" unless the search space was actually exhaustive.
A variant cannot become the new default until: