Repository overview

Below is the rendered repository README with site-safe links.

🧩 Clawin Agents — Install-Ready OpenClaw Agent Catalog

Skip the blank workspace. Start from a structured package.

Clawin is a public catalog of install-ready OpenClaw agents organized by industry, role, and real-world workflows. Browse the catalog, inspect structured packages, and install a faster starting point instead of building every agent from scratch.

New: Start by chat when you do not know the right agent yet — let Clawin help you find the best match before you install.

1395
install-ready agents

5
industries

198
role families

Website + GitHub + CLI
one connected flow

TL;DR

Discover OpenClaw agents by industry, role family, and workflow

Start by chat if you need help choosing the right package

Inspect what a package includes before you install it

Start from a structured package instead of raw prompts or a blank workspace

Use the Clawin website + catalog + CLI as one connected discovery-to-install flow

✨ Why Clawin
👥 Who Clawin is for
⭐ Why this repo is worth starring
🚀 Start here
💬 Start by chat
🧭 Highlights
💡 What you can do with Clawin
⚡ Quickstart
🆚 Why not start from scratch?
📦 What is inside a package?
📊 Current public catalog status
📈 Star history
❓ FAQ
🧱 What this repo is
⚖️ License

✨ Why Clawin

Pillar	Why it matters
Install-ready, not prompt-only	Each package is more than a role idea or isolated prompt snippet
Organized for discovery	Browse by industry, role family, and agent identity instead of guessing
Faster than building from scratch	Start from a structured package and adapt locally
Built as a connected system	Website + GitHub catalog + CLI create one browse-to-install flow

Clawin is designed to be useful before install, during evaluation, and when users are ready to activate a first agent.

👥 Who Clawin is for

Audience	Why Clawin fits
OpenClaw users	You want a faster starting point than building agents from scratch
Developers and technical teams	You want to explore role-based agent setups with real package structure
Operators, researchers, and business teams	You want workflow-specific packages, not random prompt fragments
GitHub resource collectors	You want a catalog worth starring now and revisiting later

Clawin is not a generic no-setup AI app. It is built for users who want installable OpenClaw agent packages and a clearer path to choosing among them.

⭐ Why this repo is worth starring

Star this repo if you want a reusable OpenClaw resource that helps you:

Reason	Value
Track the catalog	Follow how the public Clawin catalog expands over time
Bookmark structured packages	Revisit install-ready starting points when a new need appears
Compare before installing	Inspect real package structure instead of abstract descriptions
Keep a strong OpenClaw resource handy	Useful even before you install anything

🚀 Start here

If you are not sure where to begin, use one of these routes.

Route	Best for	Start here
Developer starting point	JS/TS, frontend performance, Core Web Vitals	`software-it-web-performance-engineer-js-ts`
Financial research starting point	Company research and structured analysis workflows	`financial-research-company-research-analyst`
Growth and marketing route	Strategy, attribution, paid media, SEO-oriented roles	Digital Marketing Agency
Content platform route	Moderation, creator ops, policy, risk, platform-product workflows	Content Media Platform
Full catalog route	Users who want breadth first	Browse all agents

Suggested starter-pack directions

Beginner OpenClaw Starter Pack
Developer Starter Pack
Growth and Marketing Starter Pack
Financial Research Starter Pack
Ecommerce Operations Starter Pack
Content Moderation Starter Pack

Large catalogs become easier to love when users can begin from a clear theme, not a blank list.

💬 Start by chat

If you do not know the right agent ID yet, the best first path is now chat-first discovery.

Why this path matters

Instead of asking users to guess from a large catalog, Clawin can now help narrow the options before installation.

Start here

Install the matching skill
- clawhub install clawin-agent-match-install
Make sure the public CLI is available
- npm install -g agents.clawin
- clawin init
Refresh the current public catalog
- clawin catalog refresh --catalog https://agents.clawin.club/releases/2026-03-18-p6-full-catalog-1395-agent/catalogs/published/catalog.json
Paste one prompt in chat
- Find me a Clawin agent for frontend performance work and install the best match.
Confirm the recommended package, then install it

Best for

first-time users who do not know where to start
users comparing several agents before committing
teams that want a more guided first install experience

🧭 Highlights

Highlight	Why it matters
1395 install-ready agents	Real catalog depth and strong bookmark value
5 industries / 198 role families	Structured browsing instead of random sprawl
Website + catalog + CLI	Discovery, inspection, and install in one system
Self-contained package shape	More than a role name or prompt fragment
Release-scoped publishing	Catalog growth is visible and easier to communicate

Browse by industry

Browse by surface

💡 What you can do with Clawin

Use Clawin when you want to:

browse role-specific agents by industry and function
inspect a package before committing to an install
compare multiple role families before choosing a path
build a shortlist of starter agents for a new workflow or experiment
start from a structured package instead of a raw prompt or empty workspace

Typical discovery paths

"I need a stronger starting point for an OpenClaw setup"
"I want to browse marketing, research, engineering, or moderation roles"
"I want a package I can inspect before installing"
"I want a catalog worth starring now and revisiting later"

⚡ Quickstart

Clawin now supports two practical install starts:

Option A — Discover by chat

clawhub install clawin-agent-match-install
npm install -g agents.clawin
clawin init
clawin catalog refresh --catalog https://agents.clawin.club/releases/2026-03-18-p6-full-catalog-1395-agent/catalogs/published/catalog.json

Then ask in chat for the kind of agent you need, confirm the best match, and install it.

Option B — Install directly by known ID

npm install -g agents.clawin
clawin init
clawin catalog refresh --catalog https://agents.clawin.club/releases/2026-03-18-p6-full-catalog-1395-agent/catalogs/published/catalog.json
clawin info software-it-web-performance-engineer-js-ts
clawin install software-it-web-performance-engineer-js-ts --allow-main
clawin status software-it-web-performance-engineer-js-ts

What happens in this flow

Install the CLI
Initialize Clawin locally
Refresh from the current public catalog release
Either ask Clawin to help you choose, or inspect a known package
Install that package into your OpenClaw environment
Review the local result and continue local configuration

Good first installs

Software/developer path: software-it-web-performance-engineer-js-ts
Research path: financial-research-company-research-analyst

For the full step-by-step flow, see INSTALL.md.

🆚 Why not start from scratch?

Start from scratch	Start from Clawin
Begin with a blank workspace	Begin with a role-specific starting point
Create package structure manually	Use a packaged folder shape designed for install
Gather skills and docs separately	Start with bundled package materials
Spend time deciding what to include	Inspect a concrete package first
Harder to compare options	Browse a structured public catalog

Clawin is not a replacement for local configuration or good judgment. It is a better starting point.

📦 What is inside a package?

Each published package is expected to be a directly shareable OpenClaw agent folder.

Package element	Why it exists
`README.md`	Explains the role and package intent
`INSTALL.md`	Gives install and local follow-up guidance
`PACKAGE.json`	Defines package metadata
`workspace/`	Contains role-specific workspace materials
`workspace/skills/`	Bundles required role-specific skills when needed
`config/`	Includes install-oriented config material

Clawin packages are intentionally self-contained. If an agent depends on skills to do its job well, those required skills stay bundled with the package even when similar capabilities appear elsewhere in the catalog.

That makes Clawin different from:

raw prompt libraries
loose template dumps
unstructured role lists with no install path

Formal contract:

docs/shareable-folder-package.md

📊 Current public catalog status

Metric	Value
Industries	5
Role families	198
Install-ready agents	1395
Current public release	`2026-03-18-p6-full-catalog-1395-agent`

Breakdown by industry

industry-1-software-it — 394
industry-3-marketplace-ecommerce — 355
industry-4-digital-marketing-agency — 283
industry-5-content-media-platform — 311
industry-6-financial-research — 52

For the full role-family and per-agent listing, see CATALOG.md.

📈 Star history

❓ FAQ

Do I need OpenClaw already?

Yes. Clawin is built for users who already have, or plan to use, an OpenClaw environment.

Are these prompts or install-ready packages?

These are install-ready agent packages for OpenClaw, not just raw prompts.

Do I still need local configuration?

Yes. Provider API keys, local environment setup, recipient bindings, and other machine-specific choices stay local.

Can I browse before installing?

Yes. You can browse the website catalog, inspect repository package folders, or read CATALOG.md before choosing anything to install.

What is the easiest first agent to try?

A good default software path is:

software-it-web-performance-engineer-js-ts

A good default research path is:

financial-research-company-research-analyst

🧱 What this repo is

This repo is	This repo is not
A public output catalog for Clawin	The private production pipeline
A place to browse ready-to-install OpenClaw agents	A dump of raw role-source documents
A resource for choosing a specialist package by role and domain	A repo for internal review queues or private run logs
A public install surface for published packages	A record of production environment details

Repository layout

categories/<industry-id>/agents/<role-family-key>/<agentId>/

This repository intentionally stays simple:

categories/ — public install-ready agent packages
docs/ — public packaging contract
top-level docs — install and catalog navigation

Public/private publishing model

Clawin uses a private-source / public-output split:

private repo: production pipeline, specs, review artifacts, generation workflow
this public repo: curated, install-ready agent packages only

That keeps the public catalog clean while allowing the private production system to continue evolving.

🔗 Final links

Browse the full catalog → · Read the install guide → · Visit the website → · Star this repo →

⚖️ License

Repository-level Clawin-authored catalog materials are released under Apache License 2.0.

Because some published packages include bundled skills and embedded upstream components, also read:

If a bundled component ships with its own license file or origin metadata, treat that component according to its own terms.

Notes

Secrets are intentionally excluded.
Users must provide their own local provider configuration.
These packages are designed for catalog-driven OpenClaw installs, not as standalone apps.
Future releases should continue expanding this catalog with curated agent outputs from the private source repository. s must provide their own local provider configuration.
These packages are designed for catalog-driven OpenClaw installs, not as standalone apps.
Future releases should continue expanding this catalog with curated agent outputs from the private source repository.

Shareable package contract

This is the package-level contract used to keep the public catalog install-ready and self-contained.

Shareable Folder Package Contract

This document defines the expected shape of a release-ready Clawin agent folder package.

Goal

Each fine-grained role package in the repository should be directly shareable as a folder and also package cleanly into a release zip without changing package internals.

Canonical Repository Location

categories/<industry-id>/agents/<role-family-key>/<agentId>/

Canonical Package Contents

<agentId>/
  README.md
  INSTALL.md
  PACKAGE.json
  workspace/
    README.md
    SOUL.md
    IDENTITY.md
    USER.md
    AGENTS.md
    PLAYBOOK.md
    TOOLS.md
    HEARTBEAT.md
    skills/
  config/
    entry.json
    snippet.json
    SECRETS.md

Packaging Rules

Keep all persisted content in English.
Treat the repository path as the catalog path.
Treat ~/.openclaw/agents/<agentId>/ as the target install path.
Bundle each required skill under workspace/skills/ so the package remains self-contained.
Do not require a separate global skill copy step for bundled skills.
Accept repeated skill families across packages when they reflect role-specific behavior, depth, or workflow differences.
Keep secrets out of the package.

Config Rules

Preferred layout for new and regenerated packages:

config/entry.json
config/snippet.json

During the legacy transition window, repository tooling may also accept:

config/openclaw.agent.<agentId>.entry.json
config/openclaw.agent.<agentId>.snippet.json

A release-ready package should provide:

a single-agent entry JSON object for agents.list
a wrapper snippet JSON for users who prefer full-structure merge fragments
explicit workspace and agentDir install paths
a concrete recommended model id

A release-ready package should not include:

provider API keys
channel auth state
recipient-specific bindings

Install Rule

The package must be installable by copying the folder and merging the config entry, with only recipient-specific secrets left to fill.

The same package must also remain installable after zip packaging for release output generation.

Validation Checklist

A package passes the shareable-folder contract only if:

package-level docs exist
workspace files exist
bundled skills live under workspace/skills/
config entry (config/entry.json) and wrapper snippet (config/snippet.json) both exist
generator preflight must fail before overwrite when generated paths would exceed the conservative 240-char Windows safety budget
forced overwrite may remove only the exact target package directory after confirming it stays within the allowed package root
config paths point to the target install path, not the repository path
no secrets are stored in the package

Public catalog rules, package structure, and install references.

Where the data comes from

2026-03-18-p6-full-catalog-1395-agent

Localized summary first, source docs second.

Understand the new install flow first

See what the public catalog actually ships

Check the package contract before you copy anything