harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is unreliable across sessions — forgets context, drifts out of scope, claims "done" before tests pass, or starts each session inconsistently — or when creating or assessing AGENTS.md, CLAUDE.md, feature_list.json, init.sh, progress.md, or session-handoff files. Reach for it even if the user never says the word "harness."
- License 许可
- MIT
- 最近更新
- 2026-10-29
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- harness-creator
- license
- MIT
- description
- Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is unreliable across sessions — forgets context, drifts out of scope, claims "done" before tests pass, or starts each session inconsistently — or when creating or assessing AGENTS.md, CLAUDE.md, feature_list.json, init.sh, progress.md, or session-handoff files. Reach for it even if the user never says the word "harness."
02 资源文件 24
- 参考文档agents/openai.yaml290 B
- 参考文档evals/evals.json7.1 KB
- 参考文档README-UK.md3.4 KB
- 参考文档README.md2.4 KB
- 参考文档references/context-engineering-pattern.md5.1 KB
- 参考文档references/gotchas.md6.6 KB
- 参考文档references/lifecycle-bootstrap-pattern.md8.1 KB
- 参考文档references/memory-persistence-pattern.md4.4 KB
- 参考文档references/multi-agent-pattern.md6.3 KB
- 参考文档references/skill-runtime-pattern.md1.8 KB
- 参考文档references/tool-registry-pattern.md6.0 KB
- 脚本scripts/create-harness.mjs2.7 KB
- 脚本scripts/lib/harness-utils.mjs16.1 KB
- 脚本scripts/render-assessment-html.mjs839 B
- 脚本scripts/run-benchmark.mjs7.1 KB
- 脚本scripts/validate-harness.mjs1.1 KB
- 其他SKILL.md.en5.1 KB
- 其他SKILL.md.uk8.1 KB
- 参考文档templates/agents.md2.3 KB
- 参考文档templates/feature-list.json1.4 KB
- 参考文档templates/feature-list.schema.json1.4 KB
- 脚本templates/init.sh2.6 KB
- 参考文档templates/progress.md1.0 KB
- 参考文档templates/session-handoff.md509 B
03 SKILL.md 正文
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:
| Subsystem | Minimal artifact | Purpose |
|---|---|---|
| Instructions | AGENTS.md or CLAUDE.md |
Startup path, working rules, definition of done |
| State | feature_list.json, progress.md |
Current feature, status, evidence, next step |
| Verification | init.sh or documented commands |
Tests/checks the agent must run before claiming done |
| Scope | Feature dependencies and done criteria | Prevents overreach and half-finished work |
| Lifecycle | session-handoff.md, end-of-session routine |
Makes the next session restartable |
First Move
- Inspect what already exists: instruction files, feature/state files, verification commands, docs, package manifests.
- Ask only for missing context that cannot be inferred safely: target agent, desired file name, tolerance for structure, and whether overwriting is allowed.
- 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.mdfor Claude-oriented projects.--package-manager npm|pnpm|yarn|bunwhen detection is wrong.--commands "cmd one,cmd two"for custom verification.--forceonly 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. The benchmark first runs a self-check — it scaffolds a throwaway harness and validates it, proving the bundled scripts work end-to-end — then scores the target and eval coverage. 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.mdorCLAUDE.md - [ ]
feature_list.json - [ ]
progress.md - [ ]
init.sh - [ ] Optional
session-handoff.mdfor multi-session work - [ ] Documented verification evidence or next action
If you cannot create files, provide exact file contents and commands instead.
04 同仓库更多 Skills
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
web-app-penetration-testing
Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature match. Runs with Strix, either the self-hosted open-source CLI or the managed app.strix.ai cloud. Use when the user asks to pentest, hack, security-test, or audit their web app, website, web application, or staging site.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
typescript-pro
Implements advanced TypeScript type systems, creates custom type guards, utility types, and branded types, and configures tRPC for end-to-end type safety. Use when building TypeScript applications requiring advanced generics, conditional or mapped types, discriminated unions, monorepo setup, or full-stack type safety with tRPC.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.