harness-root-instructions

Audit and draft concise root agent instruction files like AGENTS.md.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-root-instructions-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-root-instructions
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-root-instructions
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-root-instructions-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Root instruction files such as AGENTS.md often grow bloated with details that belong in documentation, or miss essential rules entirely. This Skill audits or drafts root agent instructions so they stay short, durable, and routing-focused. ## Core Features & Use Cases - Structured Audit: Reads AGENTS.md (falling back to CLAUDE.md, README.md, and docs), counts lines against a 50-200 line target, and classifies content as essential rules versus material that should move elsewhere. - Standard Target Shape: Provides a canonical section outline covering Harness, Project Summary, Quick Start, Verification, State Files, Hard Rules, and Links. - Safe Editing Workflow: Produces a structured audit report with a proposed replacement outline, and requires approval before writing or trimming anything. - Use Case: When bootstrapping a new project or cleaning up an overgrown AGENTS.md, run the audit to identify which rules to preserve, which details to relocate into docs or skills, and what is missing. ## Quick Start Audit my AGENTS.md file and propose a trimmed 50-200 line version that keeps the essential project rules.

Frequently Asked Questions about harness-root-instructions

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

FAQPage Schema
How do I audit an AGENTS.md file for an AI coding agent?

Read AGENTS.md if present, otherwise check CLAUDE.md, README.md, and docs. Count the lines against a 50-200 line target, identify essential rules like startup, handoff, and verification, and flag details that belong in docs or skills instead.

What sections should root agent instructions contain?

The recommended target shape includes Harness, Project Summary, Quick Start, Verification, State Files, Hard Rules, and Links sections. Root instructions should act as a router pointing to deeper documentation, not a full manual.

How long should an AGENTS.md file be?

Root instructions should target 50-200 lines. Files longer than that usually contain details that belong in dedicated docs or skills, while shorter files may be missing essential rules like verification or handoff procedures.

Will the audit modify my AGENTS.md automatically?

No. The audit produces a structured report with a proposed replacement outline, and approval is required before writing or trimming anything. Project-specific rules are never deleted silently or replaced with generic text.

What if my project has no AGENTS.md file?

The audit falls back to reading CLAUDE.md, README.md, and the docs directory to understand the project. It can then draft new root instructions following the standard section outline while preserving project-specific constraints.