Tencent SkillHub · Developer Tools

Openclaw Config

Edit and validate OpenClaw Gateway config (openclaw.json / JSON5). Use when adding/changing config keys (gateway.*, agents.*, models.*, channels.*, tools.*, skills.*, plugins.*, $include) or diagnosing openclaw doctor/config validation errors, to avoid schema mismatches that prevent the Gateway from starting or weaken security policies.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: SKILL.md, agents/openai.yaml, references/openclaw-config-fields.md, references/schema-sources.md, scripts/openclaw-config-check.sh

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 0.1.0

Provenance

Publisher: caopulan
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 6 sections Open source page

Overview

Safely edit ~/.openclaw/openclaw.json (or the path set by OPENCLAW_CONFIG_PATH) using a schema-first workflow. Validate before and after changes to avoid invalid keys/types that can break startup or change security behavior.

Workflow (Safe Edit)

Identify the active config path Precedence: OPENCLAW_CONFIG_PATH > OPENCLAW_STATE_DIR/openclaw.json > ~/.openclaw/openclaw.json The config file is JSON5 (comments + trailing commas allowed). Get an authoritative schema (do not guess keys) If the Gateway is running: use openclaw gateway call config.schema --params '{}' to fetch a JSON Schema matching the running version. Otherwise: use openclaw/openclaw source-of-truth, primarily: src/config/zod-schema.ts (OpenClawSchema root keys like gateway/skills/plugins) src/config/zod-schema.*.ts (submodules: channels/providers/models/agents/tools) docs/gateway/configuration.md (repo docs + examples) Apply changes with the smallest safe surface Prefer small edits: openclaw config get|set|unset (dot path or bracket notation). If the Gateway is online and you want "write + validate + restart" in one step: use RPC config.patch (merge patch) or config.apply (replaces the entire config; use carefully). For complex setups, split config with $include (see below). Validate strictly Run openclaw doctor, then fix issues using the reported path + message. Do not run openclaw doctor --fix/--yes without explicit user consent (it writes to config/state files).

Guardrails (Avoid Schema Bugs)

Most objects are strict (.strict()): unknown keys usually fail validation and the Gateway will refuse to start. channels is .passthrough(): extension channels (matrix/zalo/nostr, etc.) can add custom keys, but most provider configs remain strict. env is .catchall(z.string()): you can put string env vars directly under env, and you can also use env.vars. Secrets: prefer environment variables/credential files. Avoid committing long-lived tokens/API keys into openclaw.json.

$include (Modular Config)

$include is resolved before schema validation and lets you split config across JSON5 files: Supports "$include": "./base.json5" or "$include": ["./a.json5", "./b.json5"] Relative paths are resolved against the directory of the current config file. Deep-merge rules (per implementation): objects: merge recursively arrays: concatenate (not replace) primitives: later value wins If sibling keys exist alongside $include, sibling keys override included values. Limits: max depth 10; circular includes are detected and rejected.

Common Recipes (Examples)

Set default workspace openclaw config set agents.defaults.workspace '"~/.openclaw/workspace"' --json openclaw doctor Change Gateway port openclaw config set gateway.port 18789 --json openclaw doctor Split config (example) // ~/.openclaw/openclaw.json { "$include": ["./gateway.json5", "./channels/telegram.json5"], } Telegram open DMs (must explicitly allow senders) Schema constraint: when dmPolicy="open", allowFrom must include "*". openclaw config set channels.telegram.dmPolicy '"open"' --json openclaw config set channels.telegram.allowFrom '["*"]' --json openclaw doctor Discord token (config or env fallback) # Option A: write to config openclaw config set channels.discord.token '"YOUR_DISCORD_BOT_TOKEN"' --json # Option B: env var fallback (still recommend a channels.discord section exists) # export DISCORD_BOT_TOKEN="..." openclaw doctor Enable web_search (Brave / Perplexity) openclaw config set tools.web.search.enabled true --json openclaw config set tools.web.search.provider '"brave"' --json # Recommended: provide the key via env var (or write tools.web.search.apiKey) # export BRAVE_API_KEY="..." openclaw doctor

Resources

Load these when you need a field index or source locations: references/openclaw-config-fields.md (root key index + key field lists with sources) references/schema-sources.md (how to locate schema + constraints in openclaw repo) scripts/openclaw-config-check.sh (print config path + run doctor)

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

3 Docs1 Scripts1 Config

SKILL.md Primary doc
references/openclaw-config-fields.md Docs
references/schema-sources.md Docs
scripts/openclaw-config-check.sh Scripts
agents/openai.yaml Config