# N Agentic Harnesses

Design, evaluate, and improve agentic harnesses for developer tools, assistants...

- Repository: https://github.com/NateBJones-Projects/OB1 (4752 stars)
- Category: Design
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add NateBJones-Projects/OB1 --skill n-agentic-harnesses -g -a claude-code -y`
Codex: `npx skills add NateBJones-Projects/OB1 --skill n-agentic-harnesses -g -a codex -y`
Cursor: `npx skills add NateBJones-Projects/OB1 --skill n-agentic-harnesses -g -a cursor -y`
Gemini CLI: `npx skills add NateBJones-Projects/OB1 --skill n-agentic-harnesses -g -a gemini-cli -y`

## Description

Design, evaluate, and improve agentic harnesses for developer tools, assistants, workflow runtimes, copilots, and AI-powered products. Use when work involves tool-use architecture, permissions, approval gates, workflow state, durability, context and memory systems, evaluation strategy, observability, operator visibility, or phased implementation plans for an AI system. Trigger when symptoms imply harness gaps too: stale context, surprising tool calls, sessions that die on crash, missing approval controls, or costs spiraling without clear visibility.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# N Agentic Harnesses

## Problem

Most AI products do not break because the model is too weak. They break at the harness layer: unclear tool boundaries, missing approval policy, brittle state, sloppy context assembly, no evaluation loop, and weak operator visibility. This skill turns those vague issues into concrete primitives, boundaries, phases, and checks.

## Trigger Conditions

- The user is designing or rebuilding an agent, assistant, copilot, or AI workflow
- The request mentions harness architecture, tool-use architecture, tool registries, permission layers, approval gates, workflow state, session persistence, retries, resumability, memory, evals, observability, or multi-agent design
- The user wants to evaluate an existing harness for risks, missing primitives, UX gaps, or operational weakness
- The symptoms point to harness problems even if the word "harness" never appears:
  - tools fire without clear permission
  - sessions fail on crash or long waits
  - context gets stale or bloated
  - operators cannot see what happened or why
  - costs, retries, or handoffs are drifting out of control

## Default Posture

- Bias toward lean, solo-maintainable architecture.
- Start with a single-agent design unless clear constraints justify more.
- Require an evaluation plan even for greenfield builds.
- Prefer explicit system boundaries, permission policy, and workflow state over prompt cleverness.
- Translate ideas into implementation phases, success criteria, and failure tests.

## Step 0: Gather Context

Before routing, make sure you have enough to work with.

For design work, confirm:

- what product or system the harness serves
- what actions the agent will take
- who the users are
- any known constraints such as solo maintenance, existing stack, or timeline

For evaluation work, inspect the harness itself:

The rest: https://github.com/NateBJones-Projects/OB1/blob/HEAD/skills/n-agentic-harnesses/SKILL.md