harness-engineering

Design control surfaces, feedback loops, and governance boundaries for autonomous agent workflows.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Sambhav242005/Major-Project --skill harness-engineering-sambhav242005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-engineering
Source: https://github.com/Sambhav242005/Major-Project/tree/main/.agents/skills/harness-engineering
Command: npx skills add https://github.com/Sambhav242005/Major-Project --skill harness-engineering-sambhav242005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous agents running long research or experimentation loops can corrupt their objectives, game their own metrics, lose state after context compaction, or take irreversible actions without approval. This Skill provides the design patterns for building a harness around an agent so it can run safely for extended periods. ## Core Features & Use Cases - Surface Classification: Define locked, editable, append-only, and human-controlled surfaces so agents cannot modify the evaluators that judge them. - Loop Patterns: Implement autoresearch-style optimization loops and research-to-skill pipelines with durable logs, novelty gates, pruning, and rollback. - Governance Boundaries: Separate PR preparation from merge authority and route destructive operations through explicit human approval. - Use Case: You are building a background agent that reads new engineering blog posts and drafts skill updates. Use this Skill to lock the source rubric, require retrieval evidence before citation, log rejected attempts, and have the agent prepare PRs that wait for human merge approval. ## Quick Start Ask the agent to design a harness for an autonomous research loop with locked evaluation rubrics, durable thread logs, and human approval for merges.

Frequently Asked Questions about harness-engineering

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

FAQPage Schema
How do I build an autonomous agent loop that runs safely for days?

Define locked, editable, append-only, and human-controlled surfaces before starting. Externalize all state into durable files like thread logs and result TSVs so the agent survives context compaction, and require human approval for merges or deploys.

How do I prevent an agent from gaming its own evaluation metrics?

Lock the evaluator outside the editable surface for the duration of the run. Report per-dimension scores instead of aggregates, require source retrieval evidence, preserve rejected attempts, and route any rubric changes to human review.

What is the difference between locked and editable surfaces in an agent harness?

Locked surfaces include evaluation metrics, rubrics, and merge policies that the agent may read but not modify. Editable surfaces are the artifacts under test, such as experiment files, prompts, or configs, which the agent may mutate during the loop.

Can an autonomous agent merge its own pull requests?

No, PR preparation and merge authority should be separate. The agent can draft changes, run checks, and write PR summaries, but merging, deploying, or destructive operations require explicit human approval unless specifically granted.

Why do long-running agents lose their state and repeat failed experiments?

State kept only in chat history disappears after context compaction. Write plans, results, and rejected attempts to append-only log files from the start so future sessions can resume without rediscovering failed ideas.

When should I not use a full autonomous harness?

Skip the harness for general quality gates or regression suites without autonomous control surfaces, which belong to evaluation work. Tool schema design, project-level planning, and hosted sandbox infrastructure are also owned by separate concerns.