brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
evaluation-runsRun lm-evaluation-harness evaluations through the lm-eval CLI, YAML configs, and Python APIs with safe flags for outputs, caching, chat templates, seeds, limits, unsafe-code confirmation, and debugging.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a future agent needs to execute, debug, or programmatically assemble an lm-eval evaluation run. It covers lm-eval run, config-backed runs, and Python calls to simple_evaluate() / EvaluatorConfig.
python scripts/check_lm_eval_cli.py --json
python scripts/build_eval_command.py \
--model hf --model-arg pretrained=gpt2 --tasks hellaswag,arc_easy \
--limit 5 --output-path results/gpt2-smoke --log-samples \
--cache-requests true --use-cache cache/gpt2_eval
lm-eval ls tasks to find registered task names.lm-eval validate --tasks hellaswag,arc_easy before longer runs.lm-eval run --config eval.yaml for the actual evaluation.simple_evaluate(), EvaluatorConfig, TaskManager, seeds, cache flags, and result dictionary handling.samples vs limit, log_samples output requirements, chat-template pitfalls, cache refresh/delete, unsafe code confirmation, and optional backend errors.scripts/build_eval_command.py builds safe lm-eval run command lines and optional YAML config files without importing model backends or downloading weights.scripts/check_lm_eval_cli.py checks importability and CLI help surfaces for lm-eval, lm_eval, run, ls, and validate.--model_args details, device/backend caveats, and registry selection, route to ../model-backends/.../task-authoring/.../result-logging/.../decontamination-maintenance/.