mergisi/awesome-openclaw-agents

• **Archetype**: harness-framework
• **Stars**: 2,851
• **Last pushed**: 2026-04-07
• **License**: MIT
• **Discovered**: 2026-04-13
• **Source**: gh-search
• **Skills found**: 196 (SOUL.md agent templates)

Summary

Comprehensive collection of 196 production-ready AI agent templates for the OpenClaw harness ecosystem, organized by business domains (automation, business, creative, development, etc.) using SOUL.md format instead of SKILL.md. Features professional deployment infrastructure through crewclaw.com platform and structured agent template system with clear identity, responsibilities, skills, and operational rules.

Assessment

HIGH VALUE. This represents a complete alternative AI harness ecosystem with sophisticated agent template organization and deployment infrastructure. The OpenClaw platform uses SOUL.md format as an alternative to SKILL.md, providing insight into different approaches to agent specification. The business domain organization and professional deployment tools make this valuable for understanding alternative harness patterns and potentially creating a babysitter OpenClaw adapter. The agent template structure is well-designed with clear separation of identity, responsibilities, skills, rules, and tone.

Extraction Priority

HIGH - Contains alternative harness patterns and sophisticated agent template system:

• OpenClaw harness integration patterns → harness adapter development
• SOUL.md agent specification format → alternative agent specification methodology
• Business domain agent organization → specializations/business-domains/
• Professional deployment infrastructure patterns → specializations/deployment-automation/

Harness Integration Ideas

• **OpenClaw Harness Adapter**: New harness integration for OpenClaw platform similar to existing babysitter adapters

**Capability Assessment for Babysitter Integration:**

**Integration Viability:** PARTIAL - Strong plugin system and tool execution but **lacks critical stop-hook capability** for babysitter's orchestration loop interruption needs.

- Adapter implementation: OpenClaw CLI detection, SOUL.md format support, crewclaw.com API integration - Plugin structure: plugins/babysitter-openclaw/ with hooks, commands, and skills - CLI integration: OpenClaw command patterns, deployment workflows, agent template management - Current limitation: No OpenClaw support in babysitter harness adapter system + **no stop hooks for conversation interruption** - Integration approach: Create adapter for OpenClaw CLI with SOUL.md conversion to babysitter format - Implementation scope: packages/sdk/src/harness/adapters/openclawAdapter.ts and plugin structure

- Current limitation: Limited agent template infrastructure in babysitter - Integration approach: Adopt crewclaw.com deployment patterns for babysitter plugin marketplace - Implementation scope: Plugin deployment automation and template management systems

• **Agent Template Infrastructure**: Enhancement to agent template management and deployment

Processes

- Source: SOUL.md template structure across 196 agent examples - Placement: methodologies/agent-specification/ - Inputs: Agent requirements, business domain, operational constraints - Outputs: SOUL.md agent specifications, deployment configurations, operational guidelines - Complexity: moderate - Notes: Alternative to SKILL.md format with focus on agent identity and operational rules

• **soul-agent-specification**: Process for creating structured agent templates using SOUL.md format with identity, responsibilities, and operational rules

- Source: Agent directory structure organized by business domains - Placement: specializations/business-organization/ - Inputs: Business requirements, domain expertise needs, operational scope - Outputs: Domain-organized agent collections, business workflow patterns - Complexity: moderate - Notes: Clear separation of automation, business, creative, development, etc. domains

• **business-domain-agent-organization**: Systematic approach to organizing agents by business function rather than technical capability

- Source: crewclaw.com deployment infrastructure and template system - Placement: specializations/deployment-automation/ - Inputs: Agent specifications, deployment targets, configuration requirements - Outputs: Deployed agents, configuration dashboards, operational monitoring - Complexity: complex

• **agent-deployment-automation**: Process for automated agent deployment with web-based configuration and deployment tools

Plugin Ideas

- What install.md would do: Install template management tools, set up agent specification frameworks, configure deployment pipelines, create template registry - Processes it would copy: soul-agent-specification, business-domain-agent-organization - Configs/hooks it would create: Template frameworks, specification tools, organization systems, deployment configurations - Source evidence: Sophisticated agent template system with business domain organization and deployment automation

• **agent-template-management**: Plugin for systematic agent template creation, organization, and deployment

Implicit Procedural Knowledge

- Source: SOUL.md format with identity, responsibilities, skills, rules, and tone structure - Placement: methodologies/agent-specification/ - Why codify: Provides alternative to SKILL.md approach that may be more suitable for certain types of agents - Sketch: Identity definition → Responsibility mapping → Skill identification → Rule establishment → Tone specification → Operational validation

• **Alternative Agent Specification Methodology**: Framework for structuring agent capabilities using identity-driven approach rather than procedural skills

- Source: OpenClaw ecosystem with crewclaw.com platform, template system, and deployment automation - Placement: methodologies/ecosystem-development/ - Why codify: Systematic approach to building complete agent platforms beyond individual agent creation - Sketch: Platform definition → Template system design → Deployment automation → Management infrastructure → Community integration → Ecosystem growth

• **Cross-Platform Agent Ecosystem Design**: Methodology for building complete agent ecosystems with templates, deployment, and management infrastructure

- Source: Business domain organization pattern across automation, business, creative, development domains - Placement: specializations/business-architecture/ - Why codify: Framework for organizing agent capabilities that aligns with business needs rather than technical categorization - Sketch: Business function analysis → Domain boundary definition → Agent responsibility mapping → Cross-domain coordination → Business workflow integration

• **Business-Domain Agent Architecture**: Process for organizing agent capabilities around business functions rather than technical domains

Library Mapping

Plugin Marketplace Mapping