Agent skill

openclaw-customizer

Expert guide for configuring, customizing, and creatively leveraging OpenClaw — the self-hosted AI gateway that connects LLMs to messaging channels (Telegram, WhatsApp, Discord, Slack, iMessage, etc.). Use when the user wants to: (1) Set up or modify their openclaw.json configuration, (2) Write or edit bootstrap files (SOUL.md, USER.md, AGENTS.md, IDENTITY.md, TOOLS.md), (3) Configure messaging channels, (4) Set up models and providers, (5) Create multi-agent routing, (6) Build skills, hooks, or cron jobs, (7) Troubleshoot OpenClaw issues, (8) Get creative ideas for leveraging OpenClaw in non-obvious ways. Triggers on: openclaw, gateway, SOUL.md, USER.md, AGENTS.md, IDENTITY.md, channels setup, agent routing, heartbeat, cron jobs, openclaw hooks, openclaw skills, openclaw config, openclaw.json, personal assistant setup.

View SKILL.md on GitHub Repository
Stars 3
Forks 1

Install this agent skill to your Project

npx add-skill https://github.com/petekp/agent-skills/tree/main/skills/openclaw-customizer

SKILL.md

OpenClaw Customizer

Help the user configure, customize, and creatively leverage their OpenClaw instance.

Approach

Be imaginative and inventive. OpenClaw is a flexible system — suggest non-obvious combinations of features that solve real problems. Think beyond basic chat: cron jobs, multi-agent routing, hooks, channel-specific personas, memory pipelines, and automation patterns.

When the user asks about a specific area, load the relevant reference file before responding.

Reference Files

Load these on demand based on what the user needs:

Topic File When to load
Config schema & settings references/configuration.md Editing openclaw.json, any config question
Bootstrap files references/bootstrap-files.md SOUL.md, USER.md, AGENTS.md, IDENTITY.md, TOOLS.md
Channel setup references/channels.md Any messaging channel (Telegram, WhatsApp, Discord, Slack, iMessage, etc.)
Models & providers references/models-providers.md Model selection, provider config, failover, auth
Tools, skills, hooks, cron references/tools-skills-hooks.md Tool policy, skills, hooks, cron jobs, memory system
Multi-agent routing references/multi-agent.md Multiple agents, routing, bindings, isolation
Creative patterns references/creative-patterns.md Ideas, inspiration, non-obvious uses, advanced patterns

Workflow

  1. Understand what the user wants to customize — ask clarifying questions if needed
  2. Load the relevant reference(s) — read the specific file(s) for the topic at hand
  3. Propose changes — show the exact JSON5 config or markdown content to add/modify
  4. Explain the "why" — help the user understand what each setting does and why you chose it
  5. Suggest adjacent improvements — if you see an opportunity to make their setup better, mention it

Key File Locations

  • Config: ~/.openclaw/openclaw.json
  • Workspace: ~/.openclaw/workspace/ (or ~/.openclaw/workspace-<agentId>/)
  • Bootstrap: SOUL.md, USER.md, AGENTS.md, IDENTITY.md, TOOLS.md in workspace root
  • Skills: ~/.openclaw/skills/ (shared) or <workspace>/skills/ (per-agent)
  • Hooks: ~/.openclaw/hooks/ (shared) or <workspace>/hooks/ (per-agent)
  • Memory: <workspace>/memory/YYYY-MM-DD.md (daily), <workspace>/MEMORY.md (long-term)
  • Sessions: ~/.openclaw/agents/<agentId>/sessions/
  • Logs: /tmp/openclaw/openclaw-YYYY-MM-DD.log
  • Cron: ~/.openclaw/cron/jobs.json

Live Documentation

For anything not covered in the reference files, fetch from the OpenClaw docs:

  • Docs index: https://docs.openclaw.ai/llms.txt
  • Getting started: https://docs.openclaw.ai/start/getting-started
  • Configuration: https://docs.openclaw.ai/gateway/configuration.md
  • Configuration examples: https://docs.openclaw.ai/gateway/configuration-examples.md

Guidelines

  • Always show concrete JSON5 snippets or markdown content — not just descriptions
  • Use JSON5 format (comments and trailing commas are OK in openclaw.json)
  • When suggesting SOUL.md or USER.md content, tailor it to what you know about the user
  • Suggest openclaw doctor when troubleshooting
  • Remind about allowFrom security — never suggest open DM policy without a warning
  • For multi-agent setups, emphasize workspace isolation and credential separation
  • When suggesting cron jobs, always include timezone awareness

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

petekp/agent-skills

multi-model-meta-analysis

Synthesize outputs from multiple AI models into a comprehensive, verified assessment. Use when: (1) User pastes feedback/analysis from multiple LLMs (Claude, GPT, Gemini, etc.) about code or a project, (2) User wants to consolidate model outputs into a single reliable document, (3) User needs conflicting model claims resolved against actual source code. This skill verifies model claims against the codebase, resolves contradictions with evidence, and produces a more reliable assessment than any single model.

3 1
Explore
petekp/agent-skills

capture-learning

Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.

3 1
Explore
petekp/agent-skills

optimize-agent-docs

Build a retrieval-optimized knowledge layer over agent documentation in dotfiles (.claude, .codex, .cursor, .aider). Use when asked to "optimize docs", "improve agent knowledge", "make docs more efficient", or when documentation has accumulated and retrieval feels inefficient. Generates a manifest mapping task-contexts to knowledge chunks, optimizes information density, and creates compiled artifacts for efficient agent consumption.

3 1
Explore
petekp/agent-skills

agent-changelog

Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.

3 1
Explore
petekp/agent-skills

literate-guide

Create a narrative guide to a codebase or feature in the style of Knuth's Literate Programming — code and prose interwoven as a single essay, ordered for human understanding rather than compiler needs. Use when the user asks to 'explain this codebase as a story', 'write a literate guide', 'create a narrative walkthrough', 'tell the story of this code', 'Knuth-style documentation', 'weave a guide for this feature', or when they want deep, readable documentation that treats the program as literature. Also trigger when someone wants a document that a thoughtful reader could follow from start to finish and come away understanding both WHAT the code does and WHY every design choice was made.

3 1
Explore
petekp/agent-skills

autonomous-agent-readiness

Assess a codebase's readiness for autonomous agent development and provide tailored recommendations. Use when asked to evaluate how well a project supports unattended agent execution, assess development practices for agent autonomy, audit infrastructure for agent reliability, or improve a codebase for autonomous agent workflows. Triggers on requests like "assess this project for agent readiness", "how autonomous-ready is this codebase", "evaluate agent infrastructure", or "improve development practices for agents".

3 1
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results