arbor-agent-tools

Emulates Arbor tree, eval, merge, and report tools with a stdlib Python state script.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When running Arbor-style research workflows in Codex or Claude Code without native Arbor tools (TreeView, TreeAddNode, TreeSetMeta, RunExecutor, GitMergeBranch, report tooling), there is no deterministic way to manage idea-tree state, capture eval scores, generate executor prompts, or validate runs. This Skill provides a local helper layer that stores state in the same shape as open-source Arbor. ## Core Features & Use Cases - Local Idea-Tree State Management: Initialize, view, add, update, prune, and propagate nodes in .arbor/sessions/<run>/.coordinator/idea_tree.json with file locking and atomic writes. - Eval Score Capture and Log Parsing: Run templated eval commands, parse scores from output or cached logs (normalizing carriage-return progress logs), and record baseline/trunk metadata. - Executor Prompts, Merge Checks, and Reports: Generate executor or smoke-mode prompts, create worktrees, guard merges, validate trees with check, and produce a final REPORT.md. - Use Case: Forward-test the Arbor skill suite by copying a project to a disposable directory, initializing a short run, adding one hypothesis, generating a smoke executor prompt, recording a mocked score, and finishing with check and report. ## Quick Start Ask the agent to use the arbor-agent-tools skill to initialize an Arbor run in the current project, set the baseline score metadata, add one hypothesis node, and generate a smoke-mode executor prompt.

Frequently Asked Questions about arbor-agent-tools

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

FAQPage Schema
How do I emulate Arbor tools in Claude Code or Codex?▼

Use the bundled arbor_state.py script, which mirrors native Arbor commands like init, view, add, update, meta, eval, record, merge, check, and report. It stores state in .arbor/sessions/<run>/.coordinator/idea_tree.json, matching the open-source Arbor layout.

How do I capture eval scores from training logs?▼

Run arbor_state.py eval with a templated command to execute and parse scores automatically, or use parse-log on an existing log file. parse-log normalizes carriage-return progress logs before extracting metrics like val_bpb, accuracy, or loss.

Does arbor-agent-tools require external Python packages?▼

No, arbor_state.py is stdlib-only and works with a standard Python 3 installation. It optionally uses fcntl for file locking on POSIX systems but falls back gracefully elsewhere.

Can I run tree-mutating commands in parallel?▼

No, mutating commands such as init, meta, add, update, prune, propagate, eval, record, worktree, and merge must be serialized for the same run. The script uses a lock file, but parallel mutation is explicitly disallowed to keep tree state consistent.

What are the limitations of the smoke test mode?▼

Smoke mode must not edit source code, create real worktrees, run training, GPU jobs, or minute-scale evals. Expensive eval commands should be replaced with cached-score parsers or clearly labeled mocked scores, ending with check and report.