harness-improvement
SolidImprove Kandev's AI harness from session learnings or explicit requests. Use when the user asks to record learnings, update or create skills, agents, subagents, commands, AGENTS.md/CLAUDE.md guidance, or adapt harness files across Claude, Codex, Cursor, or OpenCode.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- kdlbs
- Repository
- kdlbs/kandev
- Created
- 8 months ago
- Last Updated
- today
- Language
- Go
- License
- AGPL-3.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
harness-eng
Use when designing, evaluating, or simplifying an agent project harness: AGENTS.md/CLAUDE.md rules, startup scripts, progress logs, feature trackers, handoffs, evaluator rubrics, quality documents, repo-local knowledge maps, and mechanical guardrails for coding agents. Especially useful when converting raw agent-workflow notes into a concise, verifiable project control layer.
craft-harness
Given a repo, decide where agent guidance belongs and make or propose the smallest useful harness change. Use for AGENTS.md/CLAUDE.md placement, skills, hooks, MCP, plugins, sync, or pruning.
harness-engineering
Principles and judgment for designing an "agent harness" — the repo-level scaffolding (docs, feedback loops, constraints, memory, review gates) that lets AI coding agents work reliably and autonomously on a codebase. Use this whenever the user asks to make a repo more agent-friendly, set up or audit AGENTS.md/CLAUDE.md, improve how well Claude Code (or another agent) performs on their project, design feedback loops or verification gates for agents, decide what should go in project docs vs skills vs memory, or is generally trying to get better/more reliable results from AI coding agents on a specific codebase. Do not treat this as a rigid setup script — apply the principles to the specific project's language, size, team, and risk profile, and recommend only what that project actually needs.