agentleFS
hiteshbandhuhiteshbandhu/skills-i-use/skills/ai-engineer-talks/build-agent-harnesses/SKILL.md

build-agent-harnesses

Skill1 starsChanged 5 months agoMITView on GitHub

Runs checklists and workflows for designing, hardening, and operating agent harnesses — guardrails, verify steps, tool loops, durable sessions, eval, quotas, coding/deep-research/voice harnesses. Use when the user builds agent runtimes, asks what a harness is, scopes agent vs workflow, or says "agent harness", "guardrails", "verify step", "FOMAT", "durable session".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the decision tree below.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build agent harnesses

Action playbook from twenty-two AI Engineer talks on agent & harness engineering. Do not summarize talks — pick a workflow and execute it.

Supporting files (read when needed):

  • workflows.md — workflows A–L (steps, deliverables, stop conditions)
  • source-index.md — src-NNN → talk learnings in ingest-into-skills

Optional deliverables: {SKILL_OUTPUT_DIR}/build-agent-harnesses/ — see skills-i-use OUTPUT.md.


Step 0 — Pick workflow

Use the decision tree below. Open the matching section in workflows.md.

What is the user trying to do?
├─ Define harness vs agent loop + guardrails/verify     → A
├─ Decide agent vs workflow for a use case              → B
├─ Maturity path: framework → state machine → scale     → C
├─ Enterprise: quotas, skills, multi-agent platform     → D
├─ Agent evaluation + anti-hype discipline            → E
├─ Long-horizon research / deep research harness        → F
├─ Coding agent / computer-use / IDE harness            → G
├─ Production chat UX: resume, steer, multi-device      → H
├─ Operate many parallel coding agents (FOMAT)          → I
├─ Regulated / domain-vertical knowledge agents         → J
├─ Delete scaffold; maximize LLM compute in backend     → K
└─ Post-training / finetune / RL for tool agents        → L

Stop summarizing once a workflow is identified — run its checklist.


Install

cp -r skills/build-agent-harnesses ~/.claude/skills/
cp -r skills/build-agent-harnesses ~/.cursor/skills/
cp -r skills/build-agent-harnesses ~/.codex/skills/

From skills-i-use or ingest-into-skills after sync.

Source corpus: ingest-into-skills playlists/agent-harness-engineering-ai-engineer/.


Cross-cutting rules

RuleSource
Harness = tools + context + guardrails + verify around the model[src-001 @ 4:36]
Do not prompt harder when verify shows failure — fix harness[src-001 @ 9:37]
Agents only when ambiguity/value/error profile justify cost[src-002 @ 2:57]
Every agent is a state machine; prune prompts as models improve[src-003 @ 4:37]
Agent eval needs environments + actions, not I/O strings only[src-006 @ 7:52]
Decouple clients via durable sessions for resume/steer[src-015 @ 5:25]

Disputed steps: read talk in source-index.md.


Output to user

  1. Name the workflow (A–L) and what you are producing
  2. Save artifacts under ./skill-outputs/build-agent-harnesses/ when the user wants files
  3. Do not auto-commit

Invocation examples

@build-agent-harnesses design a harness for our browser agent
agent vs workflow for this support bot?
we need quotas and verify steps for production agents

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.