benchmark
/benchmark
Dobiera wymiary benchmarku pod decyzję, uruchamia bun repo bench i podaje każdą liczbę z tym, co ją ogranicza.
- Autor
- workerstack ↗
- Repozytorium
- repo ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Dobiera wymiary benchmarku pod decyzję, uruchamia bun repo bench i podaje każdą liczbę z tym, co ją ogranicza.
Oryginalny opis (EN)
Benchmark anything: pick the dimensions that serve a decision, weight them, run bun repo bench and report each number with what limits it. Use for /benchmark, benchmark X vs Y, or which of these is faster, smaller or cheaper.
Jak działa
- Steps
- Report
Podgląd SKILL.md
---
name: benchmark
description: "Benchmark anything: pick the dimensions that serve a decision, weight them, run bun repo bench and report each number with what limits it. Use for /benchmark, benchmark X vs Y, or which of these is faster, smaller or cheaper."
---
# Benchmark
Compare candidates on what the decision needs, run them with `bun repo bench`, and report each number with its limit.
Slash `/benchmark` only. Not a session flag. Works for any subject: code, CLIs, compressors, prompts and models, build tools, data formats, services.
## Steps
1. Pin the subject, the candidates and the decision the numbers serve. Pin each candidate's settings too (level, flags, version, config) and state them in the question: they often decide the result. Ask only if one is missing.
2. Propose dimensions from `catalog.md` (beside this file). Each gets a metric, better (lower or higher), a weight and a one-line why. List the skipped ones with why. Dimensions that are not numbers go under judged.
3. Ask once: pick and weight these, or say "go". Ask again only if a candidate cannot run.
4. Write `.repo/bench/<name>.bench.ts` with `defineBench` from `@workerstack/repo/bench`. Put one harness per candidate under `.repo/bench/<name>/`. Each does identical work on identical input and prints `bench: {"name": n}` as its last stdout line. A shared helper in the same folder is encouraged so the work is identical. `run` commands start in the repo root. Each harness asserts its output is correct (a round trip, an expected hash) and exits non-zero when it is not, so a broken candidate fails instead of scoring. Use `setup` for builds. Spec fields: `node_modules/@workerstack/repo/references/exports.md` `## Bench`.
5. Run `bun repo bench <name>`. On a `!` line, rerun once with more runs and say whether the ranks held. Exit 1 or exit 4 is a bug in the spec or a harness: fix it, do not report it as a result.
6. When `os` lists other runners, run `bun repo bench <name> --remote`. On a refusal, quote the line and the step it names.
7. Read `/principle-explain-the-number`. For each candidate check it did the work: output, size, exit. Then check that each metric's absolute gap matters to the decision: the score is best/value, so a 0.1 ms gap can swing points. Say so in Limits or suggest a lower weight. Then report.
## Report
- The table exactly as printed, header line included.
- The winner by the user's weights, with scores.
- Limits, one line each: every `!`; every `~`; OSes the decision's users run that were not measured (no `os` means measured on this runner only); dimensions dropped or judged; an input that does not represent the real workload; and the limiter of each number, or that it is unmeasured.
Example:
```text
<table>
Winner by your weights: zstd 82, gzip 74, brotli 59.
Limits: gzip wall CV 14% (!): rerun at 20 runs gave 12%, so ranks hold but its wall is ±12%.
rss sits at this runner's 44 MB floor (~): it cannot separate them.
Measured on ubuntu-latest only. Not measured: decompress time (you dropped it).
```
Pliki w paczce (2)
- SKILL.md 3 KB
- catalog.md 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · workerstack/repo | 100 | MIT |
| YuDefine/nuxt-supabase-starter | 100 | MIT |
| hoangsonww/Claude-Code-Agent-Monitor | 100 | MIT |
| RainingDaemons/agents | 100 | MIT |
| wwylon/devkit | 100 | MIT |
| serejaris/personal-corp-os | 100 | MIT |
| pekral/cursor-rules | 100 | MIT |
| peabrane/peapods | 100 | MIT |
| nguyenyou/scalex | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 867da5761515 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90bench-profile
Projektuje benchmark wydajności API: scenariusze testowe, metryki i narzędzia, w tym testy obciążeniowe i pomiar przepustowości. - 95bench-fast
Uruchamia benchmark z minimalną liczbą iteracji, aby wygenerować w BenchmarkDotNet jeden duży plik z kodem asemblera na benchmark. - 100sanity-bench
Uruchamia i odczytuje wyniki hermetycznego zestawu testów wydajności Studio w perf/bench, lokalnie i przez workflow GitHub Actions, wraz z porównaniami commitów i werdyktami. - 90add-benchmark
Dodaje nowe zadanie SWE z poprawki błędu na GitHubie do potoku bench-swe na podstawie linku do issue lub PR. - 100authoring-benchmarks
Projektuje, uruchamia i interpretuje przeglądarkowe benchmarki wydajności komponentów Elements w plikach .test.bench.ts, w tym metryki Vitest bench takie jak przepustowość, p99 i RME. - 100dstudio-bench
Mierzy wydajność Device przed i po zmianie: wybiera benchmark, uczciwie porównuje wyniki i opisuje liczby w pull requeście.