harness-initializer

Audits repository harness layers and reports gaps without writing files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams adopting an agent harness often cannot tell which artifacts (entry instructions, context docs, state files, feedback commands, evaluation rubrics, skills) exist or are missing in a repository. This Skill performs a read-only audit of any project and reports exactly what is present, what is missing, and what to fix first. ## Core Features & Use Cases - Six-layer audit: Inspects Entry (AGENTS.md, CLAUDE.md, README.md), Context (docs/ARCHITECTURE.md, docs/PRODUCT.md, docs/RELIABILITY.md), State (feature_list.json, .specs files, progress docs), Feedback (init scripts, test/build/lint commands), Evaluation (judges, rubrics, CI checks), and Skills (harness-* skills). - Fresh-session test: Answers orientation questions (what the repo does, how to start it, what is unfinished, next task) using only files found in the repo. - Non-mutating guarantee: Produces a status table and a minimal bootstrap plan, then stops and asks for approval before writing anything. - Use Case: Run it on a newly cloned repository before starting agent work to discover that no AGENTS.md exists and the documented startup command fails, then get a prioritized fix plan. ## Quick Start Ask the agent to run a harness-init audit on the current repository and report which harness layers are present or missing.

Frequently Asked Questions about harness-initializer

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

FAQPage Schema
How do I audit a repository for agent harness readiness?

Run the harness-init audit, which inspects six layers in order: Entry, Context, State, Feedback, Evaluation, and Skills. It records each result, outputs a status table with gaps and recommended fixes, and writes nothing without your approval.

What files does a harness audit check for?

It looks for AGENTS.md, CLAUDE.md, or README.md at Entry; docs/ARCHITECTURE.md, docs/PRODUCT.md, docs/RELIABILITY.md at Context; feature_list.json, .specs files, and progress docs at State; init scripts and test/build/lint commands at Feedback; judges and rubrics at Evaluation.

Does the harness initializer create or modify files automatically?

No. The audit is strictly non-mutating: it produces a report table and a minimal bootstrap plan, then stops. Files are only created after you explicitly approve the proposed plan.

What happens if a discovered startup command fails during the audit?

A failing startup command becomes the first recommended fix in the audit output, unless you request an audit-only report. The skill never assumes commands like init.ps1 exist; it verifies them from the repository.

Are missing context documents a blocking problem in the audit?

No. Context layer gaps such as a missing docs/ARCHITECTURE.md are non-blocking. The audit flags them in the report and continues checking the remaining layers.