mcpField
H
harness-engineering

harness-engineering

github.com/10xchengtuAgent workflows104137 installsUpdated 13w ago
Repository

About harness-engineering

A skill for setting up and improving the operating context around AI agents working on a project. It helps teams create or diagnose harness layers, from project files and context design to guardrails, evaluation, long-running tasks, loops, and memory.

Key features

  1. 01New-project harness setup
  2. 02Agent performance diagnosis
  3. 03Incremental harness improvement
  4. 04Context and guardrail design
  5. 05Evaluation and feedback loops
  6. 06Multi-agent and memory guidance

Use cases

  1. 01Preparing a new project for agent use
  2. 02Diagnosing why an agent performs poorly
  3. 03Improving an existing agent workflow
  4. 04Supporting long-running or unattended tasks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/10xchengtu/harness-engineering --skill harness-engineering

After installing, type/harness-engineeringin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
01-project-setup.md
02-context-engineering.md
03-constraints.md
04-multi-agent.md
05-eval-feedback.md
06-long-running.md
07-diagnosis.md
08-loops.md
09-memory.md

Details

From the project README

Harness Engineering

Harness = the operating system for AI agents working on your project. Model is CPU, context window is RAM, harness is OS.

Core Principle

Start simple, add complexity only when needed. Every harness component encodes an assumption about what the model can't do alone. Pressure-test these assumptions — they expire as models improve. Build for deletion.

When This Skill Activates

SignalAction
Empty/new project→ Full project setup (Section 1)
User frustrated with agent→ Diagnose & fix harness gaps (Section 7)
Existing project needs improvement→ Assess & incrementally improve
Explicit harness question→ Reference relevant sections

Workflow

For New Projects
  1. Assess — What's the project? Tech stack? Team size? How will agents be used?
  2. Setup — Create foundational harness files → read references/01-project-setup.md
  3. Context — Design information architecture → read references/02-context-engineering.md
  4. Constraints — Add guardrails and linters → read references/03-constraints.md
  5. Evaluate — Set up feedback loops → read references/05-eval-feedback.md
  6. If project involves multi-agent or long tasks → read references/04-multi-agent.md, references/06-long-running.md
  7. If agents will run unattended (scheduled tasks, CI loops) → read references/08-loops.md; if agents should learn across sessions → read references/09-memory.md
For Diagnosis (Agent Not Performing Well)
  1. Read references/07-diagnosis.md immediately
  2. Identify which harness layer is failing
  3. Apply targeted fix from the relevant reference
For Incremental Improvement

Assess current harness maturity, identify weakest layer, improve one layer at a time.

Harness Layers (Quick Reference)

LayerWhatReference
Project SetupAGENTS.md, docs/, directory conventions01-project-setup.md
Context EngineeringWhat info agents see, progressive disclosure, working state02-context-engineering.md
Constraints & GuardrailsLinters, type systems, architecture enforcement, safe autonomy03-constraints.md
Multi-Agent ArchitectureAgent separation, coordination protocols, delegation patterns04-multi-agent.md
Eval & FeedbackTesting, grading, GC agents, observability05-eval-feedback.md
Long-Running TasksProgress tracking, context resets, handoff artifacts06-long-running.md
LoopsVerifiers, stop conditions, guardrails, autonomous operation08-loops.md
MemoryCross-session memory, index-then-fetch, consolidation, forgetting09-memory.md
DiagnosisWhen agents fail — identify root cause in harness, not model07-diagnosis.md

Self-Update Protocol

When you discover a new reusable harness pattern during a project:

  1. Identify which reference file it belongs to (or if it needs a new one)
  2. Add the pattern with: what it solves, when to use it, how to implement it
  3. Keep it concise — no fluff, just the pattern

Comments

Markdown supported