Harness context
A portable, cross-agent skill library for Claude Code and compatible AI agents.
npx -y skills add mifunedev/skills --skill harness-contextAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Explain the Open Harness architecture, layout, and conventions. Use this skill when the user asks about project structure, layout, git workflow, rules, or how things are organized. Returns specific file paths and `path:line` citations. TRIGGER when: asked about harness structure, layout, conventions, rules, process, or project organization.
SKILL.md
1.5 KB, as published. Nobody here has run it
Harness Context
Use this skill when the user asks about Open Harness layout, lifecycle, conventions, git workflow, or where files live.
Steps
- Read
CLAUDE.mdfor the orchestrator contract — what the root-level agent does and does not do. - For layout questions, read the per-directory
README.mdfiles (e.g.apps/README.md,crons/README.md,tasks/README.md,scripts/README.md,.worktrees/README.md) and theProject Structuresection ofCLAUDE.md. There is no single comprehensive tree — use the filesystem and the directory READMEs. - Read relevant rules under
.claude/rules/:git.md— issue / branch / commit / PR conventionssandbox-processes.md— tmux sessions for long-running processesdirectory-readme.md— when a directory needs a READMEadvisor-model.md— pattern for delegating to sub-agents
- Answer with
path:linecitations.
Output shape
- Short factual answer first, then file references.
- Lifecycle questions (setup / validate / teardown): cite the relevant
section of
CLAUDE.md. - Convention questions: cite the specific rule file under
.claude/rules/.