arbor

Coordinate autonomous optimization of an artifact against a measurable objective.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/jasrajtulsi/GRAD-SCOPE --skill arbor-jasrajtulsi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arbor
Source: https://github.com/jasrajtulsi/GRAD-SCOPE/tree/main/.claude/skills/arbor
Command: npx skills add https://github.com/jasrajtulsi/GRAD-SCOPE --skill arbor-jasrajtulsi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Arbor helps you improve a real artifact through many experiment-and-evaluate cycles without losing track of what was tried, what failed, and what actually transferred to held-out evaluation.

Core Features & Use Cases

  • Hypothesis-driven search: Organize competing ideas as a tree so each experiment has a clear claim.
  • Isolated execution: Test changes in separate worktrees so experiments do not clobber one another.
  • Dev/test discipline: Use dev scores to guide search and test scores to admit only transferable improvements.
  • Use cases: Model training, agent or harness tuning, data pipeline refinement, and benchmark optimization.

Quick Start

Use the arbor skill to define your objective, separate dev and test evaluators, and iteratively test isolated hypotheses until the best artifact is confirmed.

Frequently Asked Questions about arbor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run autonomous optimization cycles without losing track of failed experiments?

Use a hypothesis tree to organize competing optimization ideas so each experiment has a clear claim. This structure tracks what was tried, what failed, and what transferred to held-out evaluation during long-horizon artifact tuning.

How does dev/test split discipline work for benchmark-style experimentation?

Dev/test evaluator separation uses dev scores to guide the hypothesis search and test scores to admit only transferable improvements. This held-out merge gating ensures optimizations generalize beyond the dev set.

What's the best way to isolate code changes during long-horizon training recipe search?

Test changes in isolated executor worktrees so experiments do not clobber one another. This isolation protects the main artifact until a hypothesis passes held-out merge gating and is admitted.

Can I use worktrees for pipeline refinement and harness improvement?

Yes, isolated executor worktrees support pipeline refinement and harness improvement by testing changes independently. This prevents experiments from clobbering one another during long-horizon code tuning.

Why does evidence backpropagation matter for experiment tracking?

Evidence backpropagation feeds evaluation results back into the hypothesis tree to guide future search directions. This ensures the optimization process learns from both successful and failed experiments to refine the artifact efficiently.

When should I use a hypothesis tree for model training optimization?

Use a hypothesis tree for model training when you need long-horizon optimization with clear claims for each experiment. It is essential when tracking competing ideas, isolating changes, and ensuring improvements transfer to held-out evaluation.