autoagent

Plan and run AutoAgent Harbor benchmark experiments with isolated output directories.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Handy369/passto-pi-frame --skill autoagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoagent
Source: https://github.com/Handy369/passto-pi-frame/tree/main/skills/autoagent
Command: npx skills add https://github.com/Handy369/passto-pi-frame --skill autoagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you run reliable AutoAgent Harbor benchmark and experiment loops while keeping infrastructure stable and ensuring results are analyzed and recorded consistently.

Core Features & Use Cases

  • Experiment planning-first workflow: Uses README.md, program.md, and optional .agent/baseline.md as the source of truth, then directs changes mainly through program.md, tasks/, and run configuration.
  • Two-phase handling (bootstrap vs formal experiments): Separates one-time provider/model compatibility bootstrap from repeatable benchmark iterations.
  • Benchmark-ready output discipline: Directs writing results to isolated experiment output directories (e.g., /Users/handy/autoagent-outputs/<experiment-name>/) and avoiding pollution of the baseline worktree.

Quick Start

Ask for an AutoAgent Harbor benchmark or an A/B test focused on routing/skill evaluation, and tell the agent to update program.md and tasks/ then run and analyze results into a dedicated experiment output folder.

Frequently Asked Questions about autoagent

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

FAQPage Schema
How do I design reliable A/B testing experiments for routing and skill evaluation?

A/B testing experiments for routing and skill evaluation require planning via program.md, controlled edits in tasks/, and isolated output recording to an experiment-specific directory. This ensures stable infrastructure and repeatable benchmark iterations without polluting the baseline worktree.

What is the best way to benchmark AutoAgent Harbor workflows?

Benchmarking AutoAgent Harbor workflows involves a two-phase handling approach: separating one-time provider/model compatibility bootstrap from repeatable benchmark iterations. You direct changes through program.md and run configuration, then analyze results.tsv, result.json, and trajectory outputs.

How does experiment design keep baseline worktrees clean during model benchmarking?

Experiment design keeps baseline worktrees clean by directing benchmark results to isolated experiment output directories, such as /Users/handy/autoagent-outputs/<experiment-name>/. It optionally uses a read-only baseline inheritance from .agent/baseline.md.

Do I need to run a bootstrap phase before starting formal benchmark iterations?

Yes, a bootstrap phase is required before formal benchmark iterations to establish one-time provider and model compatibility. This two-phase handling separates initial setup from repeatable benchmark loops to ensure results are analyzed consistently.

Can I inherit baseline configurations when running A/B testing for routing?

Yes, you can inherit baseline configurations for A/B testing by using an optional read-only baseline from .agent/baseline.md. The workflow uses README.md and program.md as the source of truth to direct controlled edits in tasks/ and run parameters.