Index of every page on this site: llms.txt
All skills
Run it yourself

Micro-benchmark and iteratively improve hot paths in any codebase: baseline first, mandatory improvement suggestions (bottleneck + 3 creative ideas + recommended next step), bounded attempts, user lock-in checkpoints, then human WHY comments after lock-in. Use when the user asks to benchmark, profile, optimize performance, compare implementations, or measure µs/op before shipping perf changes. Applies to Bun/Node, React, Next.js, browser code, and extensions.

Use this Skill: https://skilld.dev/gh/illyism/dev-skills/benchmarking

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

outcomes-template.md

≈318 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Benchmark outcomes log

Keep these in your own repo (e.g. docs/perf-outcomes/). One file per locked-in perf change. Numbers are machine-specific; patterns and rules are what we keep.

When to append

After Phase D (lock-in), not after investigation-only runs.

Filename

YYYY-MM-DD-<project-or-domain>-<short-slug>.md

Example: 2026-01-15-checkout-form-validation.md

Template (copy per entry)

# <title>

- **Date:** YYYY-MM-DD
- **Project:** repo or product name
- **User-visible action:** e.g. Enter / Copy in picker
- **Suites:** `bun tools/benchmark/<suite>.mjs` (+ live trace if used)
- **Runtime:** Bun x.x · happy-dom / Chrome trace

## Locked in

| Change | Module | Ship gate |
|---|---|---|
| … | `src/…` | pass / fail + why |

## Round 0 → shipped (µs/op or ms)

| Label | Before | After | × vs ref |
|---|---|---|---|

## Learnings → perf rules

- Rule N: … (portable; no golden µs)

## Live trace (optional)

Link or summary from [perf-live-traces.md](perf-live-traces.md).

## Next ideas (not shipped)

- …

Perf rules index

Derived rules live in perf-rules.md. After each lock-in, add or tighten a rule if the learning generalizes — treat it like lint policy for hot paths.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill provides a legitimate and structured micro-benchmarking workflow with helper scripts for timing functions and running benchmark suites. No malicious patterns or security risks were detected.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at f8a2249. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 weeks ago.

Activeupdated 2 weeks ago
Other metadata
metadata
{
  "version": "1.0.0",
  "author": "illyism",
  "source": "https://il.ly/skills/benchmarking"
}

README badge

README badge for illyism/dev-skills/benchmarking