benchmark
/benchmark
Use when 要產出、查核或依據一個量測出來的效能數字:報 speedup/regression、挑 library 或設定、凍結 benchmark harness、對單一指標做 hillclimb。NOT for 找出變慢的原因(/diagnose)、估工時或交期(/estimate-hours)、CI runner 規格與排隊(/ci-runners、/delivery-capacity)。
- Author
- YuDefine ↗
- Repository
- nuxt-supabase-starter ↗
- Licence
- MIT
- Last repository change
- 14.11.2026
Assessment and security
- Files in this package
- 9
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/summarize-runs.mjs
What it does and when to use it
Use when 要產出、查核或依據一個量測出來的效能數字:報 speedup/regression、挑 library 或設定、凍結 benchmark harness、對單一指標做 hillclimb。NOT for 找出變慢的原因(/diagnose)、估工時或交期(/estimate-hours)、CI runner 規格與排隊(/ci-runners、/delivery-capacity)。
Original author description
Use when 要產出、查核或依據一個量測出來的效能數字:報 speedup/regression、挑 library 或設定、凍結 benchmark harness、對單一指標做 hillclimb。NOT for 找出變慢的原因(/diagnose)、估工時或交期(/estimate-hours)、CI runner 規格與排隊(/ci-runners、/delivery-capacity)。
How it works
- Phase 1 -- 先寫主張再量
- Phase 2 -- 逐側調到 production 設定並量
- Phase 3 -- 出報告
- Phase 4 -- 持續逼近單一指標(hillclimb,可選)
- 相鄰 skill
SKILL.md preview
--- name: benchmark description: "Use when 要產出、查核或依據一個量測出來的效能數字:報 speedup/regression、挑 library 或設定、凍結 benchmark harness、對單一指標做 hillclimb。NOT for 找出變慢的原因(/diagnose)、估工時或交期(/estimate-hours)、CI runner 規格與排隊(/ci-runners、/delivery-capacity)。" --- # benchmark 數字出口之前,先查它量到的是不是你以為的那件事;要逼近目標時,一次只改一件、量完才決定留不留。改編自 pstack 的 `benchmark-checklist`、`principle-explain-the-number` 與 hillclimb/perf-issue playbook,授權見 `references/UPSTREAM.md`。 # SOP ## Phase 1 -- 先寫主張再量 1. THINK 先寫下要出口的那句主張(含數字、單位、資料規模,例如「60k 筆匯出 p50 快 30%」)、什麼結果會改變決定、noise floor;run-to-run 的擴散比預期效果大就先停,不繼續量。 2. READ 讀取量測腳本或指令,記下它計時什麼、數什麼、忽略什麼;跑 `uptime` 與 `nproc` 看機器忙不忙,忙又停不掉就在 Phase 2 交錯兩側並在報告寫明。 3. THINK 使用者明說「只要抓個大概」且只量一次時,只做七問的第 4、7 問並寫明單次;任何選項之間的比較(挑 library、runtime、設定)一律不算大概,走完整 Phase 2。 ## Phase 2 -- 逐側調到 production 設定並量 1. READ 讀取 `rules/量測七問.md`,逐問用跑出來的證據回答;limiter 要靠不報告的 profile 跑、第 2 問要把每一側調到 production 設定再量。 2. DELEGATE 兩側各量至少 5 次並交錯(A、B、A、B…),把兩組數字依序交給 `node <本 skill 根目錄>/scripts/summarize-runs.mjs --a <數字,逗號分隔> --b <數字,逗號分隔>`(指標越大越好時加 `--higher-is-better`),讀 stdout 的 `route=` 分流: 評估:first-match;以上皆非 → R* | id | `route` | 動作 | | --- | --- | --- | | R1 | `need-more-runs` | 補跑到每側 ≥ 5 次再判,**NEVER** 用不足次數的數字下結論 | | R2 | `no-measurable-difference` | 結論寫「沒有可量測差異」,附 script 印的 median 與 range | | R3 | `faster` 或 `slower` | 該方向成立;仍要通過七問其餘各問才能寫進報告 | | R* | 其他值、欄位缺、exit 2 | STOP,回報 script 原始輸出,**NEVER** 憑印象判方向 | 3. THINK 差距很接近且 script 判不出時,用 rank-sum 檢定或 harness 自帶的統計判斷;這一步是 agent 判斷,script 刻意不做。 ## Phase 3 -- 出報告 1. THINK 先選 verdict:faster/slower/no measurable difference/inconclusive;宣稱有差異卻說不出 limiter、有一側沒調到 production 設定、或第 4/7 問查不了時,一律寫 inconclusive 並寫明缺口。 2. WRITE 先讀取 `templates/benchmark-report.md` 與 `templates/benchmark-report.example.md`,再依骨架複製結構、參考範例改寫數字、單位、跑數、range 與 limiter,完成結論先行的量測報告;PR 描述只放一個主數字,細節放連結檔。 ## Phase 4 -- 持續逼近單一指標(hillclimb,可選) 1. THINK 只在「持續逼近單一指標的目標」時走本 Phase;一次性修復不走,回 Phase 1–3。 2. READ 讀取 `rules/hillclimb迴圈與停止條件.md`,先凍結 harness 並證明它分得出差異,再定指標、方向與含次數下限的停止條件。 3. WRITE 先讀取 `templates/decision-log.txt` 與 `templates/decision-log.example.txt`,再依骨架複製欄位、參考範例改寫,在 repo 之外開這個 hillclimb 的決策紀錄,每個嘗試一列,保留與回退都記。 4. DELEGATE 每輪一個假設、一次改動,凍結 harness 量前後,依 Phase 2 第 2 步取 `route=` 判指標有沒有越過 noise,並依 rule 的決策表決定保留或回退;結束時回報指標與目標、baseline 到最終的百分比、保留與回退次數、每個保留的修正一行、決策紀錄路徑、下一個最想試的點子。 ## 相鄰 skill | 場景 | 用 | | --- | --- | | 找出變慢或壞掉的原因 | `diagnose`(變慢的原因歸它;數字能不能信歸本 skill) | | 工作量、交期 | `estimate-hours` | | CI runner 規格、排隊、容量 | `ci-runners`、`delivery-capacity` |
Files in this package (9)
- SKILL.md 4 KB
- references/UPSTREAM.md 2 KB
- rules/hillclimb迴圈與停止條件.md 6 KB
- rules/量測七問.md 6 KB
- scripts/summarize-runs.mjs 5 KB
- templates/benchmark-report.example.md 1 KB
- templates/benchmark-report.md 1 KB
- templates/decision-log.example.txt 1 KB
- templates/decision-log.txt 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · YuDefine/nuxt-supabase-starter | 100 | MIT |
| workerstack/repo | 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 |
Database snapshot: 13.11.2026 · package version e7836bb12363 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100benchmark-checklist
Check whether a measured performance claim supports a comparison or decision. Use when running benchmarks, reporting a measured speedup or regression, or choosing between implementations from timing results. Do NOT use for interpreting published benchmarks without running them… - 100steady-flame
Zuko's steady flame for vetting a performance number. A flame that flickers is not a measurement. Use for benchmark-checklist, /benchmark-checklist, before you report or act on a speedup, a regression, a latency, a throughput, a hillclimb harness, or a library or config choice… - 100benchmark-checklist
Seven evidence questions every performance number must pass before you report it or act on it. Use on /benchmark-checklist, whenever you produce a before/after timing, claim a speedup or regression, freeze a benchmark harness, or pick a library or setting for speed. - 100benchmark-checklist
Vet a performance measurement (limiter, tuning, limits, errors, repeatability, relevance, whether the work ran) before reporting a speedup or regression. Use when you run a benchmark or report a number you measured. - 100benchmark-checklist
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured. - 100benchmark-checklist
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.