Harness Starter — AI skill for Claude Code
A working AI harness you can open in Claude Code and ask questions of, then make your own.
How to install Harness Starter
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open kju4q/harness-starter and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Harness Starter does
A working AI harness you can open in Claude Code and ask questions of, then make your own. One folder, one domain, one CLAUDE.md map.
Alternatives in AI
- Osaurus — Own your AI. The native macOS harness for AI agents -- any model, persistent memory, autonomous execution, cry 5.1k ★
- Abu Cowork — Open-source alternative to Claude Cowork — a local-first AI agent desktop app · multi-model · self-evolving sk 349 ★
- BossConsole — Open-source, multi-platform harness for AI agents — a native, multi-threaded operator's console (JVM, not Elec 227 ★
README
Harness Starter
This is a working harness. Not a worksheet, an actual folder you can open in an agent and ask questions of right now.
The architecture is tool-agnostic:
- one identity file
- one map file
- one real domain with actual data inside
The only thing that changes across tools is the instruction filename. The system itself stays the same.
What's here
me.md— who the person is, what they are building, and how they work.content/— a real example domain with ideas, scripts, and performance notes.logs/— weekly working notes.CLAUDE.md— the Claude Code version of the map.AGENTS.md— the Codex-style version of the same map.
Which file does my tool read?
- Use
CLAUDE.mdfor Claude Code. - Use
AGENTS.mdfor Codex and other AGENTS-style coding agents.
If your tool expects a different instruction filename, keep the same map and copy it into the file that tool reads.
Try it before you change anything
- Open this folder in your coding agent.
- Ask:
what should I post this week based on what's been working? - Watch it read the map, find that
content/andlogs/are relevant, and answer from the actual files.
Nothing is stored. Everything is re-read from the folder in that moment.
That is the harness. The answer is good because the files are good and the map told the agent where to look.
Folder structure
.
├── AGENTS.md
├── CLAUDE.md
├── content
│ ├── ideas.md
│ ├── performance.md
│ ├── README.md
│ └── scripts
│ └── video-3-how-to-build-it.md
├── logs
│ └── week.md
└── me.md
Make it yours
- Rewrite
me.mdso it is actually you. - Replace the example files in
content/with your real domain. - Keep one live map file for the agent you use, or keep both map files in sync if you use multiple tools.
Keep it to one domain at first. One folder, one domain, one map. Add more only after this already feels useful.
Related Skills
Plan Mode Arken
Create detailed technical implementation plans for Arken AI development. Ask clarifying questions one at a tim
Nami Win Linux
Nami for Windows and Linux. This is the Nami AI agent workbench (originally Mac-only) made available on Window
Suzielaw
An open-source alternative to Harvey. A legal-AI workspace where lawyers chat with a specialized assistant ("C
Buyer Eval Skill
B2B software vendor evaluation skill for Claude Code — domain-expert questions, vendor AI agent conversations,
Ontology
Stage 03. Invoke the ontology-engineer to promote discovery output into the client domain model. Assembles the
Al Context Map
Build and sharpen a project's domain model — CONTEXT.md glossary and ADRs
Related Agents
Diff Explainer
Explains a diff (staged, working tree, branch, or commit) in the project's domain language and then asks the u
Harness Code Reviewer
Code reviewer — two-stage review against a pinned SHA: spec compliance first, then code quality, hunting fail-
Design Doc Expert
Expert engineering planning specialist who creates design docs, DRI working docs, and ADRs. Use proactively wh