Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
walkinglabs avatar

Harness Creator

  • 1.6k installs
  • 11k repo stars
  • Updated August 4, 2026
  • walkinglabs/learn-harness-engineering

harness-creator is an agent skill for build lightweight agent harnesses with agents.md, state files, verification, and handoff.

About

The harness-creator skill is designed for build lightweight agent harnesses with AGENTS.md, state files, verification, and handoff. Harness Creator Use this skill to make a repository easier for coding agents to start, stay in scope, verify work, and resume across sessions. Keep the harness small enough that agents actually follow it. Invoke when the user creates or audits AGENTS.md, feature state, verification commands, or handoff docs.

  • --agent-file CLAUDE.md for Claude-oriented projects.
  • --package-manager npm|pnpm|yarn|bun when detection is wrong.
  • --commands "cmd one,cmd two" for custom verification.
  • --force only after confirming overwrites are acceptable.
  • Memory across sessions: Memory Persistence.

Harness Creator by the numbers

  • 1,618 all-time installs (skills.sh)
  • +64 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #352 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

harness-creator capabilities & compatibility

Capabilities
agent file claude.md for claude oriented proje · package manager npm|pnpm|yarn|bun when detecti · commands "cmd one,cmd two" for custom verifica · force only after confirming overwrites are acc
From the docs

What harness-creator says it does

Harness Creator Use this skill to make a repository easier for coding agents to start, stay in scope, verify work, and resume across sessions.
SKILL.md
>-
SKILL.md
npx skills add https://github.com/walkinglabs/learn-harness-engineering --skill harness-creator

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.6k
repo stars11k
Security audit2 / 3 scanners passed
Last updatedAugust 4, 2026
Repositorywalkinglabs/learn-harness-engineering

How do I build lightweight agent harnesses with agents.md, state files, verification, and handoff?

Build lightweight agent harnesses with AGENTS.md, state files, verification, and handoff.

Who is it for?

Teams making repos agent-friendly with instructions, state, and verification loops.

Skip if: Skip for model selection or chat UI design without repo harness artifacts.

When should I use this skill?

User creates or audits AGENTS.md, feature state, verification commands, or handoff docs.

What you get

Completed harness-creator workflow with documented commands, files, and expected deliverables.

  • AGENTS.md or CLAUDE.md
  • Feature state files
  • Verification workflow definitions

By the numbers

  • Models five core harness subsystems for coding agent repositories
  • Licensed MIT under walkinglabs/learn-harness-engineering

Files

SKILL.mdMarkdownGitHub ↗

Harness Creator

Use this skill to make a repository easier for coding agents to start, stay in scope, verify work, and resume across sessions. Keep the harness small enough that agents actually follow it.

Not for model selection, prompt tuning in isolation, chat UI design, or general app architecture.

Core Model

Every useful coding-agent harness has five subsystems:

SubsystemMinimal artifactPurpose
InstructionsAGENTS.md or CLAUDE.mdStartup path, working rules, definition of done
Statefeature_list.json, progress.mdCurrent feature, status, evidence, next step
Verificationinit.sh or documented commandsTests/checks the agent must run before claiming done
ScopeFeature dependencies and done criteriaPrevents overreach and half-finished work
Lifecyclesession-handoff.md, end-of-session routineMakes the next session restartable

First Move

1. Inspect what already exists: instruction files, feature/state files, verification commands, docs, package manifests. 2. Ask only for missing context that cannot be inferred safely: target agent, desired file name, tolerance for structure, and whether overwriting is allowed. 3. Prefer a minimal harness first. Add memory, tool safety, multi-agent, or benchmark details only when the user's problem calls for them.

Common Tasks

Create a harness

Use the bundled script when working on a local repository:

node skills/harness-creator/scripts/create-harness.mjs --target /path/to/project

Options:

  • --agent-file CLAUDE.md for Claude-oriented projects.
  • --package-manager npm|pnpm|yarn|bun when detection is wrong.
  • --commands "cmd one,cmd two" for custom verification.
  • --force only after confirming overwrites are acceptable.

Then explain what was created and how the user should replace placeholder feature entries.

Audit an existing harness

Run:

node skills/harness-creator/scripts/validate-harness.mjs --target /path/to/project

Report the five subsystem scores, the lowest-scoring area, and the first 2-3 changes that would improve reliability. Treat the lowest score as a candidate bottleneck; confirm with failures, logs, or task outcomes before claiming causality.

Produce a report

Use when the user wants a shareable assessment:

node skills/harness-creator/scripts/render-assessment-html.mjs --target /path/to/project
node skills/harness-creator/scripts/run-benchmark.mjs --target /path/to/project --html /path/to/report.html

Be clear that this is a structural benchmark. Real effectiveness still needs before/after agent sessions on representative tasks.

When to Read References

Load only the reference needed for the user's problem:

  • Memory across sessions: Memory Persistence
  • Reusable workflows as skills: Skill Runtime
  • Permissions, tools, concurrency: Tool Registry & Safety
  • Context budget and progressive disclosure: Context Engineering
  • Delegation and parallel agents: Multi-Agent Coordination
  • Hooks, startup, long-running work: Lifecycle & Bootstrap
  • Non-obvious failure modes: Gotchas

Design Rules

  • Keep the root instruction file short: routing and invariants, not a full manual.
  • Put project facts in project docs, not in the skill.
  • Make verification commands explicit and runnable.
  • Require evidence before marking a feature done.
  • Use one active feature unless the harness has explicit multi-agent ownership boundaries.
  • Prefer append/update state files over relying on chat history.
  • Never hide destructive behavior in scripts; overwrites require explicit user approval.

Deliverable Checklist

For a usable minimal harness, leave the target project with:

  • [ ] AGENTS.md or CLAUDE.md
  • [ ] feature_list.json
  • [ ] progress.md
  • [ ] init.sh
  • [ ] Optional session-handoff.md for multi-session work
  • [ ] Documented verification evidence or next action

If you cannot create files, provide exact file contents and commands instead.

Related skills

How it compares

Choose harness-creator when you need a full agent harness audit across AGENTS.md, verification, and handoff rather than a single-session handoff document alone.

FAQ

What does harness-creator do?

Build lightweight agent harnesses with AGENTS.md, state files, verification, and handoff.

When should I use harness-creator?

User creates or audits AGENTS.md, feature state, verification commands, or handoff docs.

Is harness-creator safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.