agentleFS
berekvolgyipeterberekvolgyipeter/dotclaude/skills/agent-harness/SKILL.md

agent-harness

Skill2 starsChanged 18 days agoMITView on GitHub

Browse and explore agent harness frameworks and Claude Code resource collections. Use when the user wants to learn about, explore, or use agent orchestration frameworks, multi-agent architectures, or Claude Code resource catalogs — e.g., "how does Archon work?", "show me ECC (everything-claude-code) resources", "find an agent pattern for X", "explore agent harness repos", "what's in the agent harness catalog?". Make sure to use this skill whenever the user asks about any agent framework, multi-agent pattern, or Claude Code resource collection — even if they don't explicitly say "agent harness" or name a specific repo.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All repos are cloned and indexed together under a single path:

    line 21
  2. Distinctive:

    Check for plugin manifests if present:

    line 56

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Harness

Help users discover, explore, and understand agent harness frameworks and Claude Code resource collections from curated repositories.

Catalog

The catalog at ~/.claude/skills/agent-harness/references/catalog.json lists all indexed repositories with descriptions and topics. Read it first to understand what's available and which repo is most relevant to the user's need.

Each entry has these fields: github (source repo), local_path (where it's cloned), description (what it contains), topics (keyword tags), and content_types (e.g. frameworks, workflows, agents, skills, rules).

All repos are cloned and indexed together under a single path:

~/.claude/skills-references/agent-harness/

Each repo lives at the local_path specified in the catalog (e.g., ~/.claude/skills-references/agent-harness/coleam00-archon/).

Search

Always start with semantic search — it combines semantic understanding with BM25 keyword matching, so it surfaces conceptually relevant results even when exact keywords differ. Only fall back to keyword search if semantic search returns no results or the index is unavailable.

Primary — semantic search:

mcp__claude-context__search_code(
  path="~/.claude/skills-references/agent-harness",
  query="<user need>"
)

Fallback — keyword search (only when semantic search fails or is unavailable). Use grep and find through Bash: they also search hidden folders such as .archon/ and .claude/, where workflows and skills live.

grep -ril --include='*.md' --include='*.yaml' "<keyword>" ~/.claude/skills-references/agent-harness/

Browse

To list contents of a specific repo — docs and skills are Markdown, workflow definitions are YAML:

find ~/.claude/skills-references/agent-harness/<repo-dir> \( -name '*.md' -o -name '*.yaml' \) -not -path '*/.git/*'

Check for plugin manifests if present:

find ~/.claude/skills-references/agent-harness/<repo-dir> -name '*plugin*.json' -not -path '*/.git/*'

Workflow

  1. Understand the need — ask clarifying questions if the user's request is vague (e.g., "agent" could mean orchestration framework, a specific Claude Code agent, or a resource collection).
  2. Catalog — read ~/.claude/skills/agent-harness/references/catalog.json to identify which repos are relevant based on descriptions and topics.
  3. Search — use semantic search to find matching content across all repos.
  4. Read before recommending — read the relevant README, docs, or workflow definitions before presenting findings. Understand what it does, what dependencies it needs, and how to use it.
  5. Present matches — show name, description, source repo, and category. When multiple options exist, compare them briefly.
  6. Guide usage — explain how to run, configure, or integrate what was found. Point to setup docs, env vars, or prerequisites as needed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.