harness-validate

Validate harness.yaml files against the Harness Protocol v1 JSON schema.

9|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/harnessprotocol/harness-kit --skill harness-validate-harnessprotocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-validate
Source: https://github.com/harnessprotocol/harness-kit/tree/main/plugins/harness-share/skills/harness-validate
Command: npx skills add https://github.com/harnessprotocol/harness-kit --skill harness-validate-harnessprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jsonschema, pyyaml, urllib.request.

What problem does it solve?

Validates your Harness Protocol configuration so you catch schema mistakes before sharing or compiling, preventing broken deployments and time-consuming debugging.

Core Features & Use Cases

  • Schema validation with field-level errors: Checks harness.yaml against the Harness Protocol v1 JSON Schema and reports failures with precise field paths and actionable messages.
  • Helpful fix suggestions and common error guidance: Points you toward specific corrections like required fields, property renames, and invalid combinations.
  • Offline fallback when schema fetch fails: Performs basic checks (such as version and metadata.name) so you still get signal even without network access.

Quick Start

Run /harness-validate harness.yaml to validate the Harness configuration in your current directory and receive PASS/FAIL with field paths and suggested fixes.

Frequently Asked Questions about harness-validate

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

FAQPage Schema
How do I validate a harness.yaml file before running compile operations?

Run the validator against your harness.yaml path to check the configuration against the Harness Protocol v1 JSON schema, returning PASS or FAIL with field-level error paths and actionable fix suggestions.

What is the best way to check harness.yaml for schema compliance and protocol errors?

Validating harness.yaml against the Harness Protocol v1 JSON schema prevents configuration errors from reaching downstream tooling by catching schema mistakes before sharing or compiling.

Why does harness.yaml schema validation fail with missing required fields?

Validation fails on missing required fields or invalid property combinations, reporting precise field paths and actionable messages to help you correct specific schema mistakes in harness.yaml.

Does harness.yaml validation work offline when the schema fetch fails?

When the remote schema fetch fails, an offline fallback executes basic checks on fields like version and metadata.name so you still receive validation signal without network access.

Can I validate harness.yaml changes after manual edits to prevent broken deployments?

You can validate manually edited harness.yaml files against the Harness Protocol v1 schema to catch configuration mistakes early, preventing broken deployments and time-consuming debugging.