Built on OpenClaw
Official public output catalog

Install-ready OpenClaw agents, organized like a real product library.

Clawin turns a deep repository tree into a clearer discovery surface. The recommended path is now prompt-first: copy one install prompt into your OpenClaw chat, install the matching skill, and let chat guide discovery and install from there.

Current public release: 2026-03-18-p6-full-catalog-1395-agent
Self-contained packages Install-path aware Source-linked detail pages
Start here

The easiest install now starts with one prompt.

The homepage should make one thing obvious: copy the install prompt, send it to your OpenClaw, install the matching skill, then let chat guide agent discovery and installation from there. ClawHub stays as the secondary path for users who prefer it.

Recommended now

Copy this prompt into your OpenClaw chat

This is the fastest path right now: one prompt installs the matching skill, then chat takes over discovery and installation.

Install prompt

Copy exactly as written

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 own OpenClaw.
2. Let it install `clawin-agent-match-install` and confirm readiness.
3. Then ask for the agent you want in chat.
Plan B

Use ClawHub after the skill is published there

Keep ClawHub as the backup install path for the skill itself. After the skill is installed, the rest of the experience still happens through chat.

ClawHub command clawhub install clawin-agent-match-install
Starter packs

Choose a route, not a blank list.

Curated entry paths help first-time users move faster through a large catalog.

Why teams choose Clawin

Better packaging, clearer discovery, lower friction.

  • Install-ready package structure instead of scattered prompt fragments.
  • A public website, GitHub catalog, and CLI flow that work as one system.
  • A chat-first path now helps users find the right agent before they install it.
  • A faster path from “I am exploring” to “I installed my first useful agent.”
Why it works

Everything from browsing to install follows one system.

The homepage should help you understand the catalog, open the right package page, and move into installation without digging through repo trees.

Discover

Browse by industry

Start from the business domain you care about, then drill into the role families published inside that slice.

Open catalog
Inspect

Inspect package detail

Every agent page shows package identity, bundled skills, install paths, config entry files, and source links.

See an agent page
Install

Install without guesswork

Use the install page to bootstrap the matching skill first, then let chat drive package selection and install without manually copying folders.

Read install guide
Source

GitHub-first publishing

The site builds from the source repository, so counts, package pages, and release scope stay close to the truth.

Read package rules
Skills

Bundled role-specific skills

Required role-specific skills stay inside the package so a copied folder remains usable on its own.

Understand the contract
Search

Fast catalog search

Search by agent id, role title, model, summary, or bundled skills without digging through folders manually.

Try the explorer
Browse flow

Three simple steps to move through the catalog.

Start wide, narrow quickly, then open the exact package page you want.

01

Pick an industry

If you know the domain first, start from software, marketplace, agency, or content media.

02

Narrow to a role family

Use families to reduce noise and compare agents doing adjacent jobs inside the same lane.

03

Open the package page

Check the role summary, bundled skills, install paths, and config files before you install anything locally.

Catalog entry points

Start from industries or high-coverage families.

Featured packages

Good starting points

See full catalog
Financial Research Sector Thematic Research

Supply Chain Signal Analyst

Monitors supplier, logistics, inventory, and procurement signals that may reveal demand shifts or operational strain before company reports fully catch up.

financial-research-supply-chain-signal-analyst openai-codex/gpt-5.4 clawin-research-analysis
Updated Mar 30, 2026
Financial Research Sector Thematic Research

Thematic Trend Analyst

Tracks structural themes such as AI adoption, electrification, reshoring, digitization, or cost deflation and shows how they may reshape coverage priorities.

financial-research-thematic-trend-analyst openai-codex/gpt-5.4 clawin-research-analysis
Updated Mar 30, 2026
Financial Research Sector Thematic Research

Competitive Landscape Analyst

Maps competitor positioning, strategic moves, pricing behavior, product differentiation, and share-shift drivers within a target market.

financial-research-competitive-landscape-analyst openai-codex/gpt-5.4 clawin-research-analysis
Updated Mar 30, 2026
Questions

What people usually want to know first.

What is this site for?

It is the public catalog site for Clawin agent packages. It helps you browse, inspect, and install packages from the clawin-agents repository.

Are these packages install-ready?

Yes. Each package is expected to ship with README, INSTALL, PACKAGE metadata, workspace content, and config files that target the final OpenClaw install path.

Do I need to install global skills separately?

Not for bundled package skills. Required role-specific skills are kept under workspace/skills inside the package so the copied folder stays self-contained.

Where does the site data come from?

The website is statically generated from the repository structure and PACKAGE.json files in clawin-agents, then published as a static site.

Ready to browse

Open the catalog, inspect a package, and install with confidence.

The homepage should get you to the next useful action quickly: browse, compare, or install.

Theme