arbor
FeaturedAutonomously improve a real artifact (code, training recipe, agent harness, data pipeline, prompt) against an objective and an evaluator, using Hypothesis Tree Refinement (HTR) from the Arbor paper. Use this whenever someone wants to iteratively optimize something over many experiments without overfitting — e.g. "get my model's eval score up", "improve this agent/harness", "tune this pipeline", "beat the baseline on this benchmark", "run a search over approaches and keep the best", "do an MLE-bench / Kaggle-style optimization", or any long-horizon "make this artifact better and don't just memorize the dev set" task. Trigger it even when the user doesn't say "Arbor" or "hypothesis tree" but describes repeated experiment-and-evaluate loops, branching exploration of competing ideas, or worries about a dev/test gap. Runs Claude itself as the coordinator with subagent executors in isolated git worktrees; for the standalone `arbor` CLI tool see references/arbor-upstream.md.
Install
Quality Score: 99/100
Skill Content
Details
- Author
- K-Dense-AI
- Repository
- K-Dense-AI/scientific-agent-skills
- Created
- 10 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
skill-auto-improve
Use when you want to automatically improve an artifact (a skill, prompt, command/workflow, or eval dataset) against a measurable metric — the orchestrator proposes one change at a time, scores it, and keeps it only if the metric improves, reverting otherwise. Vendor-agnostic (Anthropic / OpenAI / Gemini / local gateways).
thalarch-autoresearch
Runs bounded evidence-driven experiment loops for measurable optimization, repeated hypothesis testing, agent/prompt tuning, benchmark improvement, difficult debugging with a stable evaluator, and implementation search. Establishes a reproducible baseline, changes one causal surface at a time, measures under comparable conditions, keeps only demonstrated improvements, reverts failed candidates, records an experiment ledger, protects correctness guardrails, and stops on budget or convergence. Never self-modifies durable rules, merges, releases, force-pushes, or broadens scope merely to improve a score.
autoresearch-impl
Runs a Karpathy-autoresearch-style keep-or-discard iteration loop over an already-implemented branch — propose one variant, run it against tests/benchmarks, keep it if the metric improves or discard and revert, repeat within a fixed budget — before handing off to code-review/QA. Use this after subagent-driven-development (or opencode-subagent-driven-development) finishes a task, whenever the user wants to "squeeze out more performance", "try a few implementation variants", "iterate on this implementation before review", or mentions autoresearch/Karpathy about code that already runs.