harness-validate SKILL.md skillA
harness-validate from harnessprotocol/harness-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add harnessprotocol/harness-kit/harness-validate@git:20260313.da67736Pins git:20260313.da67736 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- harnessprotocol/harness-kit
- Path
plugins/harness-share/skills/harness-validate/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260313.da67736, committed Mar 13, 2026
- First version recorded
- Mar 11, 2026
- Size
- 5,309 bytes
- Repository stars
- 10
- License
- Apache-2.0
Use when user invokes /harness-validate or wants to check whether a harness.yaml file is valid according to the Harness Protocol v1 JSON Schema. Reports validation errors with field paths and helpful fix suggestions.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Validate a Harness Configuration
You are helping the user validate a `harness.yaml` file against the Harness Protocol v1 JSON Schema.
## Workflow Order (MANDATORY)
**Follow these steps in order. Do not skip any step.**
---
### Step 1: Find the file
Check for the harness file in this order:
1. A path provided by the user after `/harness-validate` (e.g., `/harness-validate ~/dotfiles/harness.yaml`)
2. `./harness.yaml` in the current directory
If no file is found at either location, tell the user:
> "No `harness.yaml` found. Specify a path: `/harness-validate path/to/harness.yaml`"
Read the file contents.
---
### Step 2: Run validation
Install the validation tools if not present and run validation:
```bash
python3 -m venv /tmp/hk-validate-venv 2>/dev/null || true
/tmp/hk-validate-venv/bin/pip install jsonschema pyyaml -q 2>/dev/null || \
(python3 -m venv /tmp/hk-validate-venv && /tmp/hk-validate-venv/bin/pip install jsonschema pyyaml -q)
```
Then run this validation script:
```python
import json, sys, yaml
try:
from jsonschema import validate, ValidationError, SchemaError
from jsonschema.validators import validator_for
except ImportError:
…Read the whole file at its exact version.
How to install
mdr add harnessprotocol/harness-kit/harness-validate@sha256:cdd17799718e77ccThe line at the top of this page pins the label git:20260313.da67736, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_cov77oitg6ih6zj2)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Mar 11, 2026 and Mar 13, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260313.da67736 latest | 2026-03-13 | da67736 | 5,309 B | A | view · diff |
| git:20260311.6c33c6e | 2026-03-11 | 6c33c6e | 5,266 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5309 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
harnessprotocol/harness-kit · 10 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cov77oitg6ih6zj2 GET https://markdownregistry.com/api/v1/resolve?ref=harnessprotocol/harness-kit/harness-validate GET https://markdownregistry.com/api/v1/blob/cdd17799718e77cce2f0f70034b1bbe9a199d18156b8250c3059c782d8161ea4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.