Recommended now

Copy one install prompt, send it to your OpenClaw, then let chat do the rest.

This is the cleanest user path before the skill is published on ClawHub. The prompt installs the chat install skill from public files, then OpenClaw can recommend and install agents for you by need.

Please install the OpenClaw skill `clawin-agent-match-install` from these public files.

Files:
- SKILL.md: https://agents.clawin.club/downloads/skills/clawin-agent-match-install/SKILL.md
- catalog_match.py: https://agents.clawin.club/downloads/skills/clawin-agent-match-install/scripts/catalog_match.py
- response-patterns.md: https://agents.clawin.club/downloads/skills/clawin-agent-match-install/references/response-patterns.md

What to do:
1. Create ~/.openclaw/workspace/skills/clawin-agent-match-install if it does not exist.
2. Download the files above into matching paths under that folder.
3. Verify the installed folder contains SKILL.md, scripts/catalog_match.py, and references/response-patterns.md.
4. If OpenClaw needs a restart to load the new skill, restart safely.
5. After installation, report the installed path and whether the skill is ready to use.

Do not claim success unless the files are actually installed.

1. Copy the prompt and send it to your OpenClaw.

2. Let it install the skill and confirm readiness.

3. Then ask for the agent you want in chat.

Secondary path

Prefer package-manager style install? Keep ClawHub as the backup path.

This path is useful once the skill is published on ClawHub. It installs the skill itself; discovery and agent installation still happen in chat after that.

Secondary Use after publish

ClawHub command clawhub install clawin-agent-match-install

Install the skill itself through ClawHub.
Then use chat to describe the agent you need.
Confirm before OpenClaw runs the install.

1

Prepare your local OpenClaw once

You do not need to manually operate the CLI during the preferred user flow, but your OpenClaw environment still needs its local runtime and install tools available in the background.

OpenClaw installed locally Clawin CLI available to OpenClaw

2

Bootstrap the install skill

Preferred now: copy the install prompt above into your own OpenClaw chat. Secondary path: use ClawHub when the skill is published there.

Copy install prompt → send to OpenClaw clawhub install clawin-agent-match-install

3

Install agents through chat

Once the skill is available, the user-facing flow is conversational: describe the goal, review the shortlist, confirm the recommendation, and let OpenClaw complete the install for the chosen agent.

Ask chat: “Find me a Clawin agent for frontend performance work.” Then confirm the install when OpenClaw asks.

What you get

A callable starting point inside OpenClaw.

A role-specific package installed into your local OpenClaw environment.
Registration and main-call access handled by the recommended direct install flow.
Package docs, workspace material, and config guidance that travel together.

What stays local

Clawin shortens setup, but local ownership still matters.

Provider API keys and model access.
Channel auth state and recipient-specific bindings.
Machine-specific environment choices and routing.
Any follow-up safety review before real use.

Good first install

Start with a package that is easy to evaluate.

A strong software default is the web performance engineer package. A strong research default is the company research analyst package.

clawin info software-it-web-performance-engineer-js-ts
clawin install software-it-web-performance-engineer-js-ts --allow-main
clawin info financial-research-company-research-analyst

Common blockers

Most installation confusion is predictable.

OpenClaw still needs to exist locally.
The skill-first path does not remove the background dependency on Clawin CLI; it only removes the need for the user to run those commands manually.
The public catalog does not replace your local provider setup.
Some packages still need local follow-up after installation.
Conversational install helps you choose, but it may still ask you to confirm before the install runs.

Install Clawin Agents from the Public Catalog

Clawin now supports two practical install paths:

Discover by chat when you do not know the right agent yet
Install by known ID when you already know the exact package you want

Both paths use the same public catalog and end in the same local OpenClaw install flow.

Prerequisites

Node.js and npm available on the target machine
an existing OpenClaw installation
permission to edit the target OpenClaw config
a working model/provider setup for the machine where the agent will run

Path A — Discover and install by chat

Use this path when you want OpenClaw to help you find the right Clawin package first.

1. Install or update the Clawin install skill

clawhub install clawin-agent-match-install

2. Make sure the public Clawin CLI is available locally

npm install -g agents.clawin
clawin init

3. Refresh from the current public catalog release

clawin catalog refresh --catalog https://agents.clawin.club/releases/2026-03-18-p6-full-catalog-1395-agent/catalogs/published/catalog.json

4. Ask OpenClaw to find the right agent

Example prompts:

Find me a Clawin agent for frontend performance work.
I need a Clawin agent for financial research company analysis.
Recommend a Clawin agent for growth and attribution work.

Expected flow:

the skill searches the public Clawin catalog
it recommends one or more candidate agents
it may compare options or explain tradeoffs
it should ask for confirmation before the actual install step

5. Confirm the install

After confirmation, use the recommended install path for the chosen agent. If you want to run the final install step yourself, use the direct path below.

Path B — Install directly by known agent ID

Use this path when you already know the exact package you want.

1. Install the Clawin CLI

npm install -g agents.clawin

2. Initialize Clawin on the machine

clawin init

This prepares the local Clawin workspace and config wiring used for catalog-driven installs.

3. Refresh from a published catalog

Catalog URL pattern:

https://agents.clawin.club/releases/<release>/catalogs/published/catalog.json

Current full-catalog public release:

clawin catalog refresh --catalog https://agents.clawin.club/releases/2026-03-18-p6-full-catalog-1395-agent/catalogs/published/catalog.json

Current scoped financial research release (52 agents):

clawin catalog refresh --catalog https://agents.clawin.club/releases/2026-03-16-p5-financial-research-v2-52-agent/catalogs/published/catalog.json

Use the published release you want. The URL always points to a release-scoped catalog snapshot under /releases/<release>/catalogs/published/catalog.json.

4. Search and inspect agents

Search the catalog you just refreshed. For the full public catalog, a software example is:

clawin search "web performance"

For the financial research slice, an example is:

clawin search "financial research"

Inspect one package before install. Example financial research package:

clawin info financial-research-company-research-analyst

The scoped financial research release publishes 52 agent ids across the broader financial research industry roster, including equity analysis, screening and comparison, market monitoring, event and earnings monitoring, and portfolio research support.

5. Install the agent

Recommended direct command:

clawin install financial-research-company-research-analyst --allow-main

The recommended direct path installs the agent and completes the registration steps needed so main can call it.

If you prefer the older explicit mental model, this is the modern one-step equivalent of install + register + allow-main.

The install command handles the package fetch and local placement for you. You do not need to manually copy a folder from categories/... into ~/.openclaw/agents/<agentId>/.

6. Review status and local config follow-up

Check the local install result:

clawin status financial-research-company-research-analyst

After install, finish the local-only pieces required by your environment:

review the generated registration/config output
keep provider credentials and other secrets local
apply any environment-specific routing or recipient bindings

If the installed package ships a config entry or snippet, treat it as local configuration material. In safe-mode flows, review the generated registration/config snippet before enabling the agent in your own OpenClaw setup.

7. Reload OpenClaw if needed

If your OpenClaw process does not hot-reload the new registration automatically, reload or restart it so the agent becomes available.

Good first installs

Software / developer path:

clawin info software-it-web-performance-engineer-js-ts
clawin install software-it-web-performance-engineer-js-ts --allow-main

Research path:

clawin info financial-research-company-research-analyst
clawin install financial-research-company-research-analyst --allow-main

Important notes

Do not commit your local secrets back into this repository.
The public catalog is release-scoped; refresh the catalog again when you want a newer published release.
Bundled agent-specific skills still live under workspace/skills/ inside installed packages when included.
Clawin packages intentionally keep required skills inside each agent package so a single install remains usable on its own.
The conversational install skill helps you choose, but it may still ask you to confirm before the final install runs.
Provider API keys, channel auth state, recipient-specific bindings, and environment-specific routing choices remain local responsibilities.

Install agents through chat first, with ClawHub as the secondary path.