agentleFS
PradnyeshpPradnyeshp/Claude-Skills/.claude/skills/benchmark/SKILL.md

benchmark

Skill2 starsChanged 4 months agoMITView on GitHub

Measure the runtime, throughput, or memory of a function, endpoint, or command — establish a baseline and report the numbers, using the project's benchmark tooling. Use when the user says "benchmark this", "how fast is this", "measure performance", "time this function", "set up a benchmark", or "what's the baseline".

98 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ios-clean, ios-fix and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 11 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 8 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 7 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 8 projects that use this

  • +1 more from Saqlain-811

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 84 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Measure stably: Run enough iterations for a stable result, report central tendency *and* spread (mean/median + stddev or p95, not a single …

    line 28
  2. Distinctive:

    Keep setup/teardown out of the timed region.

    line 34
  3. Very specific:

    Don't change the code being measured in this pass.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 84 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Bench tooling signals

!ls package.json pyproject.toml Cargo.toml go.mod 2>/dev/null

!ls benches bench benchmarks 2>/dev/null && echo "(existing benchmarks above — extend them)"

Instructions

Benchmark the target in $ARGUMENTS. If no target is given, ask what to measure and what "fast enough" means (the workload, input size, and the metric that matters — latency, throughput, or memory).

Method

  1. Pick the right tool for the stack, preferring one already in use:
    • JS/TS: vitest bench, tinybench, benchmark.js, or hyperfine for CLI commands.
    • Python: pytest-benchmark, timeit, or hyperfine for scripts.
    • Rust: cargo bench (criterion).
    • Go: go test -bench=. -benchmem.
    • For any whole-command timing, hyperfine is a good language-agnostic default.
  2. Write a focused benchmark that exercises the real target with representative input. Isolate the work being measured (set up data outside the timed loop), and use a realistic input size — note it explicitly. Warm up where the runtime/JIT makes cold runs misleading.
  3. Measure stably. Run enough iterations for a stable result, report central tendency and spread (mean/median + stddev or p95, not a single run), and note the environment (machine, runtime version) since absolute numbers aren't portable.
  4. Report the baseline as a small table: target, input size, metric, and the numbers. If comparing two implementations or before/after, run both under the same harness and report the delta with the relative change.

Rules

  1. Measure, don't estimate — report numbers from an actual run, with the iteration count and spread, not a single noisy sample.
  2. Keep setup/teardown out of the timed region; benchmark the work, not the fixture.
  3. State the conditions (input size, hardware, runtime version) — a number without them is meaningless and non-reproducible.
  4. Don't change the code being measured in this pass; this is measurement. Hand off to the optimize skill to act on a bottleneck the baseline reveals.
  5. Beware microbenchmark traps: dead-code elimination removing the work, unrealistic all-cache-hot inputs, and measuring the harness instead of the target. Call out anything that makes the result suspect.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.