Status: v0.1.7 review release — template sync, guidance, and validation workflow are in place for community contributions
Organization templates for deploying multiagent teams. Each template defines agents, communication channels, workflows, and a kickoff sequence.
spec/ # Format specification
template-spec.md # TEMPLATE.md format spec
templates/ # Organization templates
dev-team/
TEMPLATE.md # Lean markdown format
template.json # JSON format (equivalent)
support-team/
TEMPLATE.md
template.json
...
Templates can be defined as TEMPLATE.md (markdown) or template.json (JSON). Both are equivalent — tools auto-detect the format.
TEMPLATE.md uses minimal YAML frontmatter + structured markdown body:
---
name: Dev Team
type: organization
version: "1.0.0"
category: technical
author: ClawMax Team
tags: [engineering, software]
testedWith:
- platform: OpenClaw
version: "0.9.0"
- platform: ClawMax
version: "1.4.2"
---
A multiagent software development team.
## Agents
| id | name | role | tags | skills |
|----|------|------|------|--------|
| tech-lead | Tech Lead | Technical leadership | lead | github |
| engineer | Software Engineer | Feature development | engineering | github |
## Communities
- **Dev Team** — All engineering coordination
## Groups
- **Engineering** — Code review and development (Dev Team)
- **QA** — Testing and quality (Dev Team)
## Workflows
### Team Kickoff
- **Schedule:** manual
- **Mode:** managed (owner: tech-lead)
- **Targets:** agents: tech-lead
# Dev Team Kickoff
...See spec/template-spec.md for the full specification.
Some templates may declare secretRequirements in template.json for runtime values such as API keys, event URLs, slugs, export paths, or other user-provided inputs.
- ClawMax surfaces these requirements in a browser-local
Secretsstep during template apply - sensitive values can stay in the browser instead of being written into workflow markdown
- non-sensitive values can optionally prefill kickoff workflow fields when the template declares that mapping
The Lu.ma template is the reference example for this pattern.
| Category | Template | Agents | Workflows |
|---|---|---|---|
| Business | Sales Team | 4 | 4 |
| Business | HR Team | 4 | 4 |
| Business | Support Team | 4 | 4 |
| Business | Legal Team | 3 | 4 |
| Business | Marketing Team | 4 | 4 |
| Business | Convenience Store | 3 | 4 |
| Business | Specialty Retailer | 4 | 4 |
| Technical | Dev Team | 4 | 5 |
| Technical | Data Team | 4 | 4 |
| Technical | RAG Team | 5 | 6 |
| Technical | Engineering Team | 4 | 5 |
| Personal | Student Research | 4 | 4 |
| Personal | Technical Writing | 4 | 5 |
| Personal | Chief Of Staff | 4 | 4 |
| Personal | Email & Calendar Manager | 4 | 4 |
| Personal | Meeting Prep Desk | 4 | 4 |
| Personal | Meeting Capture & Follow-up | 4 | 4 |
| Personal | Personal Research Desk | 4 | 4 |
| Personal | Tax Planning Desk | 4 | 4 |
| Personal | Investing Research Desk | 4 | 4 |
| Science | Biological Research Lab | 4 | 4 |
| Science | Mathematics Proof Studio | 4 | 4 |
| Science | Materials Discovery Lab | 4 | 4 |
| Science | Physics Research Group | 4 | 4 |
| Science | Statistics Research Lab | 4 | 4 |
| Science | Computer Science Lab | 4 | 4 |
| Science | AI Research Lab | 4 | 4 |
These personal assistant, science, travel, hobbies, and family templates are intentionally marked as proposal/early-idea starters and are designed to be adapted rather than treated as fully validated workflows.
All templates include:
- Kickoff workflow with user-fillable Project Configuration
- DAG dependencies between workflows
- GitHub coordination skills (where applicable)
- Category tags for filtering
- Optional
secretRequirementsmetadata for secure runtime inputs when a template needs API keys or similar values
Contributions welcome. Please follow the TEMPLATE.md format and include both .md and .json versions.
Start with docs/CONTRIBUTING.md for the submission checklist, local workflow, and review expectations.
Known-good examples live in:
ClawMax originated the current TEMPLATE.md spec and the initial organization templates in this repository.
For now:
- ClawMax-derived templates should stay synced with the source templates in Maximilien-ai/clawmax
- Repo-specific validation metadata, guidance docs, and contribution fixtures are maintained in this repository
The intended direction is to make this repository the primary public home for the template spec and examples, with ClawMax eventually pulling from here instead of acting as the long-term upstream source.
- JSON templates are defined by schemas/template.schema.json
TEMPLATE.mddocuments are parsed and checked against schemas/template-markdown.schema.jsontestedWithmetadata is validated when present so platform/version pairs stay explicit in both formats- Run
python3 scripts/validate_templates.pyto validate all templates locally - Run
./format.shto normalize Markdown before linting
GitHub Actions runs on pull requests and pushes to main to:
- lint Markdown
- lint GitHub Actions and repository Python scripts
- validate every
templates/*/template.json - validate every
templates/*/TEMPLATE.md - verify that each template directory has both formats and that key metadata stays in sync
For local use, run ./setup.sh, then ./format.sh, ./lint.sh, and ./test.sh.
Local developer workflow:
./setup.shinstalls the pinned repo-local tooling used by formatting and linting./format.shnormalizes Markdown formatting before review or submission./lint.shruns Markdown linting, Python script checks, and GitHub Actions linting./test.shvalidates every template directory, includingtemplate.jsonandTEMPLATE.mdparity
Recommended flow before opening a PR:
- Run
./setup.sh - Run
./format.sh - Run
./lint.sh - Run
./test.sh
The desired protection policy for main lives in .github/branch-protection-main.json.
After authenticating GitHub CLI with admin access to the repo, apply it with:
./scripts/apply_branch_protection.sh
MIT