---
name: harness-skill-creator
description: Use when bootstrapping or tightening the smallest harness-oriented skill from an existing repository, workflow, evaluation corpus, or harness-analysis chain. Trigger for meta skills, reusable harness workflows, Qoder/Codex plugin skill sets, skill blueprints, and harness-analysis-like skills that need evidence-backed references, validation gates, and qodercli forward-tests.
title: harness-skill-creator
canonical_url: https://skilld.dev/gh/qoderai/better-harness/harness-skill-creator
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: [references/bootstrap-patterns.md](https://skilld.dev/api/skills-raw/qoderai/better-harness/harness-skill-creator/references/bootstrap-patterns.md).
>
> If the user asked to install this Skill, run `npx skilld install qoderai/better-harness/harness-skill-creator`. 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/harness-skill-creator`, 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/harness-skill-creator) 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/harness-skill-creator`. 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/harness-skill-creator --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/harness-skill-creator --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.

# Harness Skill Creator

Create the smallest skill that makes another agent repeat one harness job with
evidence, validation, and clear ownership.

## Workflow

1. Resolve source, target, and host: canonical `skills/<name>/`, `.agents/skills/` wrapper, or both.
2. Inspect the source chain before designing: entry `SKILL.md`, first-hop
   references, scripts, validators, templates, specs, tests, plugin manifests,
   and any real smoke evidence.
3. Load `references/bootstrap-patterns.md` after the first inventory. Use it to
   extract patterns, not product-specific rules.
4. Draft the minimum viable skill map:
   - skill name and trigger sentence
   - one job the skill owns
   - files to create under `skills/<skill-name>/`, usually `SKILL.md` plus one reference
   - evidence boundary and validation commands
   - forward-test prompt and pass/fail gates
5. Initialize new canonical skills with the system `skill-creator` helper when
   available. Add `scripts/` only for stable repeated automation; keep ad-hoc
   evaluation prompts out of runtime scripts.
6. Write the `SKILL.md` as a router. Put trigger conditions in frontmatter
   `description`, keep the body short, and route detailed rules to first-hop
   references.
7. Validate locally, then forward-test. Treat qodercli output as model evidence;
   local validators and file inspection decide pass/fail.

## Design Gates

- Prefer one skill over a stage tree until the target process proves multiple
  reusable stages.
- Copy ownership shape, not product names, branch policy, private commands, or
  source-specific team routing.
- Keep `.agents/skills/` as a wrapper or mirror when the workflow is shared by
  the plugin; canonical judgment belongs under root `skills/`.
- Do not add install, network, server, migration, or dependency-changing
  commands unless the user requested them and source evidence supports them.
- Prefer portable Node/Python validators or target-owned commands. Do not default generated validation gates to Unix-only `grep`/`find` checks.
- In attachment-only or no-tools forward-tests, never emit tool-call markup, shell probes, or inspection plans; return the skill map with `status: "insufficient-evidence"` when needed.
- Forward-test `files` is a string array of `skills/<skill-name>/...` paths, not objects.
- If the generated skill cannot pass `quick_validate.py <skill-dir>`, do not
  describe it as usable.
- After any forward-test, verify git status or file inventory for every repo the
  model was allowed to read or write.

## Validation

Run the narrowest useful gates for the created skill:

```bash
python3 <skill-creator-root>/scripts/quick_validate.py <skill-dir>
qodercli --cwd <neutral-dir> --plugin-dir <harness-root> -p "<forward-test prompt>"
qodercli plugin validate <harness-root>
```

Reject missing frontmatter, stale placeholders, broken links, unsupported
commands, source-only assumptions, pseudo tool calls, or broad reports.
