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.

perf-live-traces.md

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

Performance: local benchmark vs live trace

Use both, in this order. Local µs/op decides whether to ship; live ms confirms feel on real pages.

How to record and read Chrome traces: devtools.md

When to use which

Surface Tool Report as
Export pipeline, mapper, zip, IDB bun run benchmark / tools/benchmark/*.mjs µs/op vs Round 0
Picker hover, outline paint, first inject Chrome Performance on target tab ms frames
Full user action E2E (copy → clipboard → toast) Chrome Performance + optional console marks ms to feedback
Extension cold start, popup open Manual Chrome only ms wall time

Do not fake extension storage latency in CI. Mock delay in a dedicated suite is fine for I/O shape.

Live trace checklist

  1. Record one representative action (hover only, copy only, or both — label which).
  2. Note URL, element size, format (JSX/Tailwind/CSS).
  3. Identify longest task; name the function stack if visible.
  4. Compare to local bench — if bench says fast but trace says slow, the gap is I/O, main-thread yield, or site-specific CSS.

Trace log

Append one row per investigation. Link the outcome entry when a change ships (see outcomes-template.md).

Date URL / fixture Action Dominant ms Conclusion Outcome file
YYYY-MM-DD e.g. /dashboard e.g. open report before → after what shipped, or why not link

After a live trace

  1. If the slow part is pure computation (transform, export, serialize) → run or extend the matching local benchmark fixture.
  2. If the slow part is paint or input handling → stay in the live trace; happy-dom has no substitute for paint.
  3. Append row above; if locked in, copy learnings to perf-rules.md and an outcome entry (template).

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