Open Source Behavior Layer for OpenClaw

The concept of outfit for AI agents.

An outfit is not a prompt. Not a cron. Not a flow. It's the complete package of an agent's operational behavior: identity, automations, skills, model, channels, and work rules.

Explore the standard Contribute

12+ Official outfits

CLI First approach

100% Open Source

dressclaw

$ dressclaw wardrobe

official/

trader athlete developer

community/

alice/growth-operator

marco/eu-founder

$ dressclaw wear trader

✓ SOUL.md applied

✓ Cron jobs registered

✓ Flows deployed

✓ Skills configured

Agent now wears: trader

Features

From fragmented setup to an operating system for agent identities.

Wear / Strip / Swap

Apply an outfit, remove it, or swap it without reconfiguring everything manually. Snapshot management, restore, and active state lifecycle.

Lint / Doctor / Diff

Validate manifests, detect drift, compare configurations, and make changes visible before touching the runtime.

New / Eject / Mix

Create new outfits, clone existing ones, recombine soul, crons, flows, and skills to generate hybrid, specialized agents.

The Core Point

The outfit is the new standard.

DressClaw isn't interesting just because it automates commands. Its value lies in defining a new unit of exchange for the OpenClaw ecosystem.

Before, an agent's behavior was scattered: a piece in the prompt, a piece in the crons, a piece in the workflows, a piece in the skills. This made it hard to replicate, share, version, and reason about the overall behavior.

With DressClaw, the minimum unit is no longer the isolated file but the outfit: a declarative spec that says who the agent is, what it does, when it acts, with which tools, and within what boundaries.

01 SOUL.md

02 Cron Jobs

03 Lobster Flows

04 Skills Policy

05 Model Defaults

∑ Outfit Manifest

Composable

An outfit can extend other outfits, mix different layers, and become a building block for more sophisticated use cases.

Shareable

If the outfit is the true unit of behavior, then it can be published, reviewed, forked, and improved like any open source artifact.

Portable

The same operational role can move from one team to another without rebuilding from scratch. Less friction, more standardization.

Anatomy

Structure of an outfit.

outfit.yaml

# trader/outfit.yaml

name: trader
description: Crypto intelligence operator
soul: SOUL.md

crons:
  - name: morning-brief
    schedule: "0 7 * * *"
    message: "Prepare the morning market briefing"

flows:
  - name: whale-alert
    file: whale-alert.lobster

skills:
  allow: ["lobster"]

model:
  default: anthropic/claude-sonnet-4-20250514

File structure

trader/

outfit.yaml

SOUL.md

flows/

whale-alert.lobster

nova-score.lobster

templates/

portfolio-template.md

Architecture

A complementary, non-invasive layer.

Interface DressClaw CLI

Core Engine

Integration OpenClaw Bridge

External OpenClaw Runtime

DressClaw lives on top of OpenClaw as a behavior layer. It doesn't force runtime forks, doesn't rewrite the engine, and doesn't require changing how OpenClaw operates internally. Coherent, versionable, and reversible orchestration.

CLI

Operational interface to create, wear, validate, and compare outfits.

Engine

Manifest resolution, interpolation, snapshot, restore, and atomic application.

Bridge

Integration with OpenClaw commands for cron, config, workspace, and health checks.

Schema

Formal contract to define valid, readable, and shareable outfits.

Why It Matters

Focus shifts from prompts to designing operational roles.

For developers

Treat agent behavior as a software artifact: readable, testable, versionable, and diffable.

For teams

Move from ad-hoc configurations to reusable roles: founder, trader, developer, researcher, operator.

For the community

Outfits become the central collaboration object: public collections, forks, reviews, and marketplace.

For the ecosystem

A common language to build, share, and adopt vertical agents faster and with less fragility.

Community & Open Source

The best outfits are born from the community.

If DressClaw truly wants to introduce a standard, then the standard must be open. The best outfits won't come only from the core team: they'll emerge from vertical operators, independent developers, founders, researchers, and community leads.

Open source here is not a branding accessory. It's the mechanism through which the outfit catalog can evolve faster than the team building DressClaw.

Manifesto

I OpenClaw provides the runtime.
II DressClaw defines the behavior unit.
III The outfit becomes the artifact the community creates and exchanges.
IV The more quality outfits exist, the more the ecosystem grows.

Roadmap

From tool to ecosystem.

Phase 01

Standardization

The outfit becomes the format to describe an operational agent.

Phase 02

Distribution

Collections, registries, domain classifications, and community-driven bundles emerge.

Phase 03

Agent Marketplace

People don't just download tools: they install ready-to-use roles and remix them.

Phase 04

New Cultural Layer

We stop talking only about prompt engineering and start talking about behavior packaging.

Contribute

Build the future of agents with us.

DressClaw is open source. Every contribution counts: outfits, code, documentation, ideas. Join the community and help define the standard.

View on GitHub Read the Docs

npm install -g dressclaw