clawin-agents

Install-ready OpenClaw agents, organized by industry and role.

This repository is the public output catalog for Clawin. It publishes curated agent packages that can be copied into an OpenClaw installation and used directly after local configuration.

Quick links

• Install guide
• Full catalog
• Package contract
• Engineering family index
• Platform engineering family index

What this repo is for

Use this repository if you want to:

• browse ready-to-install OpenClaw agents by role
• pick a specialist agent instead of starting from a blank workspace
• copy one package into your own OpenClaw setup and start using it quickly

What this repo is not

This repository does not include the private production pipeline. It does not contain:

• raw role-source documents
• normalization or generation scripts
• internal review queues
• private run logs or private specs
• production environment details

Current public release

Current published catalog snapshot:

• Industries (4):
  • industry-1-software-it
  • industry-3-marketplace-ecommerce
  • industry-4-digital-marketing-agency
  • industry-5-content-media-platform
• Total install-ready agent packages: 1349
• Breakdown by industry:
  • industry-1-software-it — 394
  • industry-3-marketplace-ecommerce — 355
  • industry-4-digital-marketing-agency — 285
  • industry-5-content-media-platform — 315

For the full breakdown by role family and per-agent links, see:

• CATALOG.md

Featured starting points

If you want a quick place to start, these are strong entry points:

Frontend Engineer (JS/TS)

• Path: categories/industry-1-software-it/agents/engineering/i1-frontend-engineer-js-ts/
• Direct link: open package
• Good for: web UI implementation, component work, frontend delivery
• Bundled skills: coding-agent, ui-ux-pro-max, frontend-design

Backend Engineer (Java)

• Path: categories/industry-1-software-it/agents/engineering/i1-backend-engineer-java/
• Direct link: open package
• Good for: backend services, APIs, Java-centric delivery
• Bundled skills: coding-agent

Kubernetes Platform Engineer (Go)

• Path: categories/industry-1-software-it/agents/platform-engineering/i1-kubernetes-platform-engineer-go/
• Direct link: open package
• Good for: platform operations, Kubernetes-heavy engineering environments
• Bundled skills: coding-agent, healthcheck

See the full catalog in:

• CATALOG.md

Install in a few minutes

1. Pick one agent folder under categories/<industry>/agents/<family>/<agentId>/
2. Copy that folder into:
   • ~/.openclaw/agents/<agentId>/
3. Merge the included config entry or config snippet into your OpenClaw config
4. Fill your local provider secrets and environment-specific settings
5. Reload OpenClaw
6. Start chatting with the installed agent

Detailed instructions:

• INSTALL.md

Package contract

Each published package is expected to be a directly shareable agent folder. A package includes:

• README.md
• INSTALL.md
• PACKAGE.json
• workspace/
• workspace/skills/
• config/

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 in other agents. That overlap is treated as part of the agent's role-specific identity, not as a catalog mistake.

Formal contract:

• docs/shareable-folder-package.md

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

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.

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:

• LICENSE
• NOTICE
• THIRD_PARTY.md

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 direct OpenClaw use, not as standalone apps.
• Future releases should continue expanding this catalog with curated agent outputs from the private source repository.

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 without an extra export step.

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/
    openclaw.agent.<agentId>.entry.json
    openclaw.agent.<agentId>.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

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.

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 and wrapper snippet both exist
• config paths point to the target install path, not the repository path
• no secrets are stored in the package