The harness selects a bounded task
Choose validation, well-formedness, formatting, conversion, or a settings-based batch operation. Supply concrete input, schema, settings, and output paths.
Harness-neutral agent integration
Run deterministic XML workflows from any agent harness.
Connect an agent, orchestrator, or automation runner to ValBuddy through a local Windows command contract. The harness chooses the task and files; ValBuddy performs the XML operation and returns evidence the harness can evaluate.
- Harness-neutralNo hosted agent dependency
- Local executionFiles stay in the Windows workflow
- Deterministic contractExplicit commands and exit status
- Reviewable evidenceDiagnostics, logs, and output files
Integration contract
Keep orchestration separate from XML processing.
ValBuddy does not require a particular agent product. Any harness that can invoke a local command, pass explicit file paths, and inspect the result can place the same XML checks inside a larger workflow.
ValBuddy runs the operation
The agent invokes a wrapper script or valbuddy.exe on Windows. ValBuddy performs the requested work using installed product capabilities.
The harness reads evidence
Use the process exit status together with diagnostics, logs, and generated files. Do not infer success merely because the command started.
Portable invocation
Give every harness the same explicit inputs.
- Discover the capability.
Describe the supported task through a tool schema, project instructions, or an optionalSKILL.md. - Resolve local paths.
Pass absolute input, schema, settings, and output paths accessible to the Windows runner. - Run and capture.
Record the exit status and preserve diagnostics or batch logs with the input identifier. - Verify before continuing.
Inspect generated output and rerun the applicable validation before an agent publishes or replaces files.
Harness-invoked PowerShell
$env:VALBUDDY_EXE = "C:\Tools\ValBuddy\valbuddy.exe"
.\scripts\validate-xml.ps1 `
-SchemaPath "D:\Schemas\invoice.xsd" `
-InputFiles "D:\Data\invoice.xml"
if ($LASTEXITCODE -ne 0) {
throw "XML validation failed"
}Harness adapter
Use the integration shape your platform understands.
The published ValBuddy package follows the Agent Skills folder pattern, but that pattern is an adapter—not the execution engine. Harnesses without native skill discovery can call the same scripts or CLI contract directly.
| Harness responsibility | ValBuddy boundary | Evidence to retain |
|---|---|---|
| Capability discovery | SKILL.md, a tool definition, or project instructions describe the supported task | Selected operation and parameter values |
| Command execution | Local wrapper script or valbuddy.exe on Windows | Command line, working directory, and product version |
| Result interpretation | Exit status plus operation-specific diagnostics or logs | Process status, findings, and generated output paths |
| Follow-up action | The harness decides whether to stop, repair, retry, or continue | Validation rerun and final disposition |
Adapter examples: Codex, Claude Code, GitHub Copilot, CI runners, and custom orchestrators can act as the harness when they support the required local command workflow. Product-specific setup belongs in adapter documentation, not in the core execution contract.
Safety boundaries
Make agent execution predictable and reviewable.
- Run only explicitly supported ValBuddy operations.
- Keep the executable path outside prompts and generated source files.
- Use separate input and output paths for transformations.
- Treat non-zero status, missing output, and diagnostics as workflow failures.
- Require review before publishing or replacing important data.
Not a hosted agent service: XMLBuddy does not receive the agent conversation or run ValBuddy remotely. The harness invokes the installed Windows CLI in the environment that owns the files.