harness

Designs agent teams and generates their skills for domain-specific automation harnesses.

366|90|Updated Aug 22, 2026
One-click install
npx skills add https://github.com/bam-bam-2/solo-skills --skill harness-bam-bam-2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness
Source: https://github.com/bam-bam-2/solo-skills/tree/main/skills/harness
Command: npx skills add https://github.com/bam-bam-2/solo-skills --skill harness-bam-bam-2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building a multi-agent automation setup from scratch requires deciding how to split work across agents, writing agent definitions, authoring skills, and wiring an orchestrator together. This Skill systematizes that entire process so a new domain or project gets a coherent, tested agent harness instead of ad-hoc prompts. ## Core Features & Use Cases - Harness Architecture Design: Audits existing agents/skills, analyzes the domain, and selects an execution mode (agent team, sub-agents, or hybrid) plus an architecture pattern such as pipeline, fan-out/fan-in, or supervisor. - Agent & Skill Generation: Creates agent definition files in .claude/agents/ and skill files in .claude/skills/ with pushy trigger descriptions, progressive disclosure, and team communication protocols. - Orchestration & Evolution: Builds an orchestrator skill with data-flow protocols, error handling, and test scenarios, registers a trigger pointer in CLAUDE.md, and maintains a change log so the harness keeps evolving with feedback. - Use Case: Ask to set up a harness for a content-pipeline project, and it audits the repo, defines researcher/writer/reviewer agents, generates their skills, builds an orchestrator, and validates triggers with should-trigger and near-miss queries. ## Quick Start Ask the agent to configure a harness for your project, for example by saying "이 프로젝트에 하네스 구성해줘" (set up a harness for this project).

Frequently Asked Questions about harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a multi-agent harness for a new project?

Request harness configuration for your domain and the skill audits existing agents and skills, analyzes the domain, then generates agent definitions in .claude/agents/, skills in .claude/skills/, and an orchestrator that coordinates the team.

What is the difference between agent teams and sub-agents?

Agent teams use TeamCreate, SendMessage, and shared task lists so members communicate directly and self-coordinate, making them the default for two or more collaborating agents. Sub-agents are invoked via the Agent tool and only return results to the main agent, suiting isolated single tasks.

How are agent skills triggered and validated?

Each skill's description acts as its only trigger mechanism, so it is written aggressively with concrete trigger situations. Validation uses 8-10 should-trigger queries plus 8-10 near-miss should-not-trigger queries to check boundary accuracy and conflicts with existing skills.

Can I extend or modify an existing harness instead of rebuilding?

Yes. A Phase 0 audit detects the current state and branches into extension or maintenance modes, applying only the needed phases per a change-type matrix, then records every modification in the CLAUDE.md change history table.

What architecture patterns does the harness support?

Six patterns are supported: pipeline, fan-out/fan-in, expert pool, producer-reviewer, supervisor, and hierarchical delegation. Complex real-world setups typically combine patterns, such as parallel collection followed by consensus-based integration.

When should I not use an agent team?

Skip the team mode when only one agent is needed or when agents require no intercommunication and only return results, since team coordination adds token overhead. Single isolated tasks are better served by a lightweight sub-agent call.