---
name: generate-harness-dsl
description: Generate, revise, or review complete Harness as Code `.harness` files when a coding-agent workflow, agent role, skill, tool contract, MCP connection, runtime, or deployment must be compiler-valid and resolvable with `@qoder-ai/harness`.
title: generate-harness-dsl
canonical_url: https://skilld.dev/gh/qoderai/better-harness/generate-harness-dsl
last_updated: 2026-10-07T00:09:43.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/qoderai/better-harness/generate-harness-dsl/agents/openai.yaml), [references/dsl-contract.md](https://skilld.dev/api/skills-raw/qoderai/better-harness/generate-harness-dsl/references/dsl-contract.md), [scripts/validate.mjs](https://skilld.dev/api/skills-raw/qoderai/better-harness/generate-harness-dsl/scripts/validate.mjs).
>
> If the user asked to install this Skill, run `npx skilld install qoderai/better-harness/generate-harness-dsl`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/generate-harness-dsl`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/qoderai/better-harness/generate-harness-dsl) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/generate-harness-dsl`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/generate-harness-dsl --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/generate-harness-dsl --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Generate Harness DSL

Create a standalone Harness as Code v0.3 document and prove the execution
contract with the package compiler and resolver.

## Workflow

1. Identify the host, the capabilities it must actually expose, and the real
   control owner. Use `session` for one host session. Use `state-machine` or
   `program` only when a selected adapter explicitly implements that mode.
2. Read [the DSL contract](https://skilld.dev/api/skills-raw/qoderai/better-harness/generate-harness-dsl/references/dsl-contract.md). Start from
   [the minimal example](../../examples/minimal.harness); open
   [the standard example](../../examples/standard-coding.harness) when callable
   tools are required.
3. Generate one self-contained document unless the user requests a fragment.
   Include `language 0.3`, every referenced declaration, a concrete runtime,
   and a named deployment. Standard tools may remain implicit.
4. Run `scripts/validate.mjs`. Fix every compiler or resolution error and rerun.
   A compile-only state machine is not an executable Qoder or Pi deployment.
5. Return the DSL or saved file plus the harness id, deployment id, runtime,
   resolution status, and any execution boundary the selected adapter cannot
   satisfy.

## Authoring Rules

- State only falsifiable requirements. Do not add permission, setting,
  degradation, binding, input/output-name, or runtime-execution syntax; v0.3
  intentionally has none.
- Match the requirement verb to its capability: `use skill`, `require tool`,
  or `connect mcp`.
- Only the standard tool ids in the contract may be undeclared. Every custom
  tool declares a stable `contract` id that the adapter exposure must match.
- Qoder and Pi descriptors run `session` workflows only. A session workflow
  names exactly the one agent role declared by each harness that uses it.
- State-machine outcomes are typed on agents. Every route emitter, outcome,
  destination, entry, and stop must exist, and every agent must be reachable.
- A `program <language> <entry>` workflow resolves only when the adapter lists
  the same language in `programmaticLanguages`.
- Keep credentials out of source. Prefer `env.VARIABLE` for MCP endpoints, but
  remember that declaring an endpoint does not connect it; the adapter must do
  that.
- Do not invoke host SDKs, install integrations, or claim native enforcement
  while generating or validating DSL.

## Validate

From this skill directory, run:

```sh
node scripts/validate.mjs /path/to/workflow.harness [harness-id ...]
```

The command prints JSON and exits non-zero when compilation or any selected
named deployment fails resolution. A successful exit is required before
calling generated DSL executable.

When editing this skill, build the package first so `dist/` reflects the current
compiler:

```sh
npm run harness:build
```
