harness-engineering

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

2|Updated May 30, 2026
One-click install
npx skills add https://github.com/virahitvin8/crafty-gis --skill harness-engineering-virahitvin8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-engineering
Source: https://github.com/virahitvin8/crafty-gis/tree/main/GIT_STAR/assignment-generator/antigravity-skills-main/antigravity-skills-main/skills/harness-engineering
Command: npx skills add https://github.com/virahitvin8/crafty-gis --skill harness-engineering-virahitvin8

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 score them. - Durable State & Logging: Externalize plans, results, and rejected attempts into thread logs and TSV/JSONL files that survive context compaction. - Search Discipline & Governance: Add novelty gates, pruning rounds, rollback policies, and explicit human approval boundaries for merges and deploys. - Use Case: You are building a background agent that reads new research posts and drafts skill updates as pull requests. Use this Skill to lock the evaluation rubrics, set up a results log, and ensure the agent prepares PRs but never merges them without human review. ## Quick Start Design a harness for my autonomous research agent with locked evaluation rubrics, an append-only results log, and human approval required before any PR is merged.

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?

Separate the agent from its environment by defining locked, editable, append-only, and human-controlled surfaces. Externalize all state into durable log files, lock the evaluator before the loop starts, and require human approval for merges or deploys.

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

Lock rubrics and evaluation code outside the agent's editable surface for the duration of the run. Report per-dimension scores, require source retrieval evidence, preserve rejected attempts, and route any governance changes to human review.

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

Locked surfaces like eval metrics, rubrics, and merge policies can be read but not modified by the agent. Editable surfaces like experiment files, prompts, and configs under test are what the agent may mutate during the loop.

Why do long-running agents lose their state and how do I fix it?

Agents lose state when plans live only in chat history that gets compacted. Write thread logs, result files, and handoff notes to disk from the start so future agent sessions can resume without relying on conversation memory.

Can an autonomous agent merge its own pull requests?

No, agents should prepare branches, run checks, and write PR summaries, but merging, deploying, and destructive operations require explicit human approval. Preparing a PR and merging a PR are distinct authority levels that must be explicit in the harness.

When should I not use a full autonomous harness pattern?

Skip the full 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 owned by separate concerns.