使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/gnibu/bento --skill bento-hillclimb開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Hillclimb
The failure mode: change three things at once, the number moves, you don't know which tweak did it — or whether it was noise. Next week it drops and you can't retrace. One variable at a time, logged, keep-or-revert.
Repo layer first. Read the repo's AGENTS.md/CLAUDE.md and, if it exists, the overlay .agents/bento/bento-hillclimb.md at the repo root; follow it under the overlay rules.
Steps (paste as todos)
- Freeze the harness first. Fix the dataset, the metric, and how it's measured
before touching the thing you're tuning. If the ruler moves, no result means anything.
- Record the baseline. Run the frozen harness once. Write the number down.
- Change ONE variable. One knob per experiment. Never stack untested changes.
- Measure against baseline. Same harness, same input set.
- Keep or revert — and log it either way. Keep only a real gain (significant, not
noise; re-run if the sample is small). Log the attempt, the delta, and the decision. A reverted attempt is still knowledge — write it down so you don't retry it.
- New baseline on a keeper, then back to step 3.
- Don't stop on a lucky first hit. Run enough iterations that one good roll can't
fool you. State the stop condition up front (target metric, or N no-improvement rounds).
Guardrails
- Regression check on every keeper: a gain that breaks something else is not a gain.
- If two knobs seem coupled, that's a finding — still change one, note the interaction.
- The log is the deliverable as much as the final number. No log = you learned nothing
transferable.
