agent-harness-construction

Design stable tool action spaces and observation recovery contracts for agents.

Updated May 4, 2026
One-click install
npx skills add https://github.com/gganbukim1/myskills --skill agent-harness-construction-gganbukim1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-harness-construction
Source: https://github.com/gganbukim1/myskills/tree/main/agent-harness-construction
Command: npx skills add https://github.com/gganbukim1/myskills --skill agent-harness-construction-gganbukim1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you increase an AI agent’s task success by improving action-space/tool definitions, observation formatting, error recovery behavior, and context budgeting.

Core Features & Use Cases

  • Action space and tool design: Stabilizes tool naming, constrains input schemas, returns deterministic output shapes, and avoids overlapping or catch-all tools.
  • Observation and recovery contracts: Enforces tool responses that include clear status, summaries, next actions, and artifacts, with explicit root-cause hints, safe retry instructions, and stop conditions.
  • Context and architecture guidance: Applies practical rules for keeping system prompts minimal, loading guidance on demand, and choosing ReAct vs function-calling vs hybrid patterns for better convergence.
  • Benchmarking and anti-patterns: Tracks completion rate, retries, pass@1/pass@3, and cost per success while flagging common failure modes.

Quick Start

Ask an AI to redesign your agent’s tools and observation format by applying the Skill’s action-space rules, the required observation fields, and the error recovery contract to target higher completion rate.

Frequently Asked Questions about agent-harness-construction

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

FAQPage Schema
How do I improve AI agent completion rate when using tool workflows?

To improve agent completion rate, stabilize tool naming, constrain input schemas, and enforce deterministic output shapes. Apply observation contracts with status, summaries, next actions, and artifacts to ensure structured and reliable tool-using agent workflows.

What is an observation and recovery contract for agent tool design?

An observation and recovery contract enforces tool responses to include clear status, summaries, next actions, and artifacts. It provides explicit root-cause hints, safe retry instructions, and stop conditions to ensure robust handling of failures across exploratory and deterministic phases.

How do I structure tool inputs and outputs for deterministic agent behavior?

Structure deterministic tool inputs and outputs by constraining input schemas and returning deterministic output shapes. Avoid overlapping or catch-all tools to stabilize the action space, ensuring the agent receives consistent data formats for reliable processing.

What's the best way to choose between ReAct and function calling for agent architectures?

Choose between ReAct and function calling by evaluating convergence needs and context budgeting. Apply practical rules for keeping system prompts minimal, loading guidance on demand, and selecting hybrid patterns to optimize architecture selection for better agent completion performance.

How do I benchmark agent task success and track error recovery failures?

Benchmark agent task success by tracking completion rate, retries, pass@1, pass@3, and cost per success. Flag common failure modes and anti-patterns during exploratory and deterministic phases to measure and optimize error recovery behavior effectively.

Why does my AI agent get stuck in retry loops during tool execution?

Agents get stuck in retry loops when lacking explicit stop conditions and safe retry instructions. Implement an error recovery contract with root-cause hints and clear next actions within observation formatting to prevent infinite loops and ensure robust failure handling.