arbor-agent-orchestrator

Coordinates Arbor-style research runs by loading phase skills for ideation, execution, and merging.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/xlinh2301/EditCTC --skill arbor-agent-orchestrator-xlinh2301
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arbor-agent-orchestrator
Source: https://github.com/xlinh2301/EditCTC/tree/main/.agents/skills/arbor-agent-orchestrator
Command: npx skills add https://github.com/xlinh2301/EditCTC --skill arbor-agent-orchestrator-xlinh2301

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running an Arbor-style autonomous research workflow requires coordinating many phases—intake, ideation, executor dispatch, merge evaluation, related-work search, resume, and reporting—without losing run state or violating experiment discipline. This Skill acts as the top-level controller that loads the right phase skill at the right time and enforces the non-negotiable invariants of the workflow. ## Core Features & Use Cases - Phase Loading Order: Defines exactly when to load setup-intake, coordinator, ideate, executor, merge-eval, search, plugins/HITL/budget, resume-report, and tools skills. - Invariant Enforcement: Protects B_test from contamination, keeps the main branch protected, requires Idea Tree metadata before executor dispatch, and mandates durable artifacts. - Smoke and Forward-Test Mode: Propagates smoke-only behavior through contracts, executor prompts, and reports so the suite can be validated without running expensive training jobs. - Use Case: A user asks to recreate the open-source AutoResearch workflow on a new benchmark; this orchestrator sequences the phase skills, maintains the Idea Tree as durable memory, and produces a final REPORT.md with preserved evidence. ## Quick Start Ask the agent to run an Arbor-style research cycle using the arbor-agent-orchestrator, starting with intake and a smoke-only validation run.

Frequently Asked Questions about arbor-agent-orchestrator

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

FAQPage Schema
How do I run an Arbor-style research workflow without the Arbor CLI?▼

Load the orchestrator skill and follow its minimal run skeleton: initialize a session with the setup-intake skill, run coordinator cycles with ideate and executor skills, then finalize with resume-report. The companion arbor-agent-tools skill provides a state helper script to emulate tree operations.

What is the correct order to load Arbor phase skills?▼

Load setup-intake first for the research contract, then coordinator for the ReAct loop, ideate before adding tree nodes, executor for dispatch, merge-eval before merging, search for validated winners, plugins-hitl-budget for domain adaptation, and resume-report for finalization.

Can I run a smoke test of the skill suite without real training?▼

Yes, propagate smoke-only through the contract, metadata, executor prompts, and reports. Replace expensive eval commands with cached-score parsers or mocked scores, and avoid creating real worktrees or merging branches.

Why must B_test not be used for routine idea selection?▼

Using B_test for iteration contaminates the evaluation and invalidates final results. The orchestrator requires B_dev for iteration and reserves B_test for merge verification and final reporting only when the contract permits it.

What happens if an executor evaluates in the main repo instead of its worktree?▼

That score must be discarded and the evaluation rerun with {cwd} substitution pointing at the executor's worktree. Eval commands must use templates with {cwd} and {node_id}, never hardcoded repository paths.