neo-harness
Skill7 starsChanged 6 months agoMITView on GitHub
Use this skill when you need to inspect a target project codebase and generate or improve a tailored, comprehensive AGENTS.md file (Harness Workflow Specification) that enforces strict AI agent harness rules, feedback sensors, execution SOP, orchestration topologies, and safety redlines. Supports non-interactive script execution via scripts/generate-agents-md.py. The generated AGENTS.md MUST NOT exceed 32 KiB in size.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- generate-skillSkill
- neo-azure-pipelinesSkill
- neo-clarificationSkill
- neo-clean-architectureSkill
- neo-code-reviewSkill
- neo-csharp-interface-generatorSkill
- neo-csharpSkill
- neo-dotnet-ef-coreSkill
- neo-dotnet-minimal-apisSkill
- neo-dotnet-mvcSkill
- neo-dotnetSkill
- neo-dotnet-tag-helperSkill
- neo-dotnet-webapiSkill
- neo-harness-projectSkill
- neo-javascriptSkill
- neo-opentelemetrySkill
- neo-prSkill
- neo-python-managerSkill
- neo-pythonSkill
- neo-rabbitmqSkill
- neo-rustSkill
- neo-stop-slopSkill
- neo-sub-agentSkill
- neo-swiftSkill
- neo-swift-uiSkill
- neo-typescriptSkill
- neo-vueSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 62
Harness Assessment & Sensors: Read references/harness-assessment.md to rate harnessability and define computational vs.
- Distinctive: line 63
Execution Protocol & SOP: Read references/execution-protocol.md to enforce the 5 Harness Laws, dual-loop SOP, zero-fake pass, and …
- Distinctive: line 64
Orchestration Topologies: Read references/orchestration-patterns.md to select appropriate routing, chaining, or human-in-the-loop (HITL) …
- Very specific: line 67
Use scripts/generate-agents-md.py with assets/AGENTS.md.template as the strict baseline template.
- Distinctive: line 68
All created or modified AGENTS.md files MUST strictly contain the following 4 structural sections in order:
- Distinctive: line 77
Check the file size of the generated AGENTS.md:
- Very specific: line 79
If over 32 KiB, prune redundant descriptions or move extended reference docs to separate files under .agents/ or docs/.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Unified Agent Harness Architect & Workflow Generator
This skill integrates three core Agent engineering domains (Harness Assessment, Execution Protocol, and Orchestration Architecture) to analyze a target project and generate a tailored, strict AGENTS.md file (Harness Workflow Specification).
Core Principle
Agent = Model (Reasoning & Generation) + Harness (Guides + Sensors + Gates + Topologies)The generated AGENTS.md acts as the single source of truth governing all AI Agents operating in the project.
[!IMPORTANT] Template Compliance & Size Constraint: Any created or modified
AGENTS.mdMUST strictly adhere to the design specification ofassets/AGENTS.md.template(containing 4 mandatory sections: Project Overview, Commands Table, 9-stage Workflow Mermaid loop, and Forbidden Antipattern Redlines Table) and MUST NOT exceed 32 KiB (32,768 bytes).
Quick Automation (Non-Interactive Generator Script)
To quickly analyze a repository and generate or preview an AGENTS.md file, run the non-interactive script:
# Preview generated content (dry-run)
python3 skills/neo-harness/scripts/generate-agents-md.py --target-dir /path/to/repo --dry-run
# Generate AGENTS.md directly in target repository
python3 skills/neo-harness/scripts/generate-agents-md.py --target-dir /path/to/repo --force
# Validate existing AGENTS.md against assets/AGENTS.md.template design specification
python3 skills/neo-harness/scripts/generate-agents-md.py --target-dir /path/to/repo --validateWorkflow SOP
Step 1 — Perceive Target Repository
- Inspect project root and structure manually or via
scripts/generate-agents-md.py:- Configuration files:
package.json,pyproject.toml,Cargo.toml,go.mod,Makefile, etc. - Build, lint, and test toolchains.
- Existing guidelines:
AGENTS.md,CLAUDE.md,GEMINI.md, README. - CI workflows:
.github/workflows/, GitLab CI, etc.
- Configuration files:
- Identify primary languages, test suites, and fast local feedback sensors.
Step 2 — Reason & Synthesize Harness Rules
Load detailed reference knowledge as needed:
- Harness Assessment & Sensors: Read references/harness-assessment.md to rate harnessability and define computational vs. inferential sensors.
- Execution Protocol & SOP: Read references/execution-protocol.md to enforce the 5 Harness Laws, dual-loop SOP, zero-fake pass, and antipattern rules.
- Orchestration Topologies: Read references/orchestration-patterns.md to select appropriate routing, chaining, or human-in-the-loop (HITL) gates.
Step 3 — Generate & Format AGENTS.md
Use scripts/generate-agents-md.py with assets/AGENTS.md.template as the strict baseline template.
All created or modified AGENTS.md files MUST strictly contain the following 4 structural sections in order:
## 1. Project Overview: Primary tech stack, modular architecture, and coding conventions.## 2. Commands: Standard markdown table (Command Type,Exact Command Line,Purpose / Scope) listing test, typecheck, lint, build, or syntax check commands.## 3. Workflow: The mandatory 9-stage closed loop Mermaid diagram (graph TDfrom Step1 to Step9) followed by the 9 numbered step definitions.## 4. Forbidden Antipattern Redlines: Standard markdown table (Forbidden Action,Why It Is Prohibited,Required Behavior) specifying non-negotiable redlines.
Step 4 — Verify Template Compliance & Quality Gate
- Validate structural compliance against
assets/AGENTS.md.template:- Run
python3 skills/neo-harness/scripts/generate-agents-md.py --target-dir /path/to/repo --validate.
- Run
- Check the file size of the generated
AGENTS.md:- Must be
<= 32,768 bytes. - If over 32 KiB, prune redundant descriptions or move extended reference docs to separate files under
.agents/ordocs/.
- Must be
- Validate syntax and markdown formatting.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

