Built on OpenClaw
Official public output catalog

Install-ready OpenClaw agents, shaped like a product library.

Clawin Agents turns a deep repository tree into a cleaner browsing surface. Start wide, compare the right role family, inspect package detail, then move into installation with confidence.

Static, GitHub-driven, and generated from the source repository at build time.
Self-contained packages Install-path aware Source-linked detail pages
Catalog snapshot

See the library before you dive into the tree.

Generated from source
4
Industries
190
Role families
1,349
Agents
9
Skill variants
1,349 install-ready packages 190 role families
Why this site exists

Everything you need to choose and install a package.

The homepage should get out of your way: understand the catalog, inspect one package, and move into the install flow without hunting through the repo tree.

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

Packages are structured for direct copy into OpenClaw. The site mirrors the package contract and install flow.

Read install guide
Source

GitHub-first publishing

The site is built directly from the repository, so industry counts, family counts, and package pages come from source.

Read package rules
Skills

Bundled role-specific skills

Required skills stay inside each package so a single 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 ways 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 copy it locally.

Featured packages

Good starting points

See full catalog
Software IT Engineering

Frontend Engineer (JS/TS)

Builds production-grade web interfaces with JavaScript, TypeScript, and pragmatic frontend engineering discipline.

i1-frontend-engineer-js-ts openai-codex/gpt-5.4 coding-agent
Updated Mar 12, 2026
Software IT Engineering

Backend Engineer (Java)

Builds backend services and APIs with a Java-centric stack, production reliability, and pragmatic delivery quality.

i1-backend-engineer-java openai-codex/gpt-5.4 coding-agent
Updated Mar 12, 2026
Software IT Platform Engineering

Kubernetes Platform Engineer (Go)

Builds and operates Kubernetes-based platform capabilities for internal engineering teams with a Go-centric toolchain.

i1-kubernetes-platform-engineer-go openai-codex/gpt-5.4 coding-agent
Updated Mar 12, 2026
Get started

From catalog to install in 3 steps.

Pick the package, copy it into OpenClaw, then merge the config and fill local secrets.

1

Choose

Open the catalog, compare role summaries, and pick the package that matches the job you want.

categories/<industry>/agents/<family>/<agentId>
2

Copy

Move the package into your local OpenClaw agents directory using the target install path from the package.

~/.openclaw/agents/<agentId>/
3

Reload

Merge the config entry or snippet, fill the local secrets listed in SECRETS.md, then restart OpenClaw.

config/openclaw.agent.<agentId>.*.json
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 site is intentionally simple: fewer distractions on the homepage, stronger package pages where the real detail belongs.