Borrowing it
Nothing to install: this file belongs to hrygo/hotplex-legacy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hrygo/hotplex-legacy/main/.agent/skills/openclaw-config-fix/SKILL.mdgit clone --depth 1 https://github.com/hrygo/hotplex-legacyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hrygo/hotplex-legacy/openclaw-config-fix)<a href="https://agentmods.dev/skills/hrygo/hotplex-legacy/openclaw-config-fix"><img src="https://agentmods.dev/badge/skills/hrygo/hotplex-legacy/openclaw-config-fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hrygo/hotplex-legacy/openclaw-config-fix"><img src="https://agentmods.dev/badge/skills/hrygo/hotplex-legacy/openclaw-config-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00119 | $0.02389 |
| Opus 5 | $0.00060 | $0.01195 |
| Sonnet 5 | $0.00024 | $0.00478 |
| Haiku 4.5 | $0.00012 | $0.00239 |
Grade A, and why
openclaw-config-fix scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
cd ~/openclaw && curl -sf http://127.0.0.1:18789/healthz && echo " Gateway 健康" How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw 配置诊断与修复
诊断工作流
1. 读日志 → 2. 定位字段 → 3. 查官方资料 → 4. 修复 → 5. 验证
不假设问题，按优先级验证每一步。
脚本工具说明
本技能包含 4 个 Python 脚本工具，位于 scripts/ 目录：
| 脚本 | 功能 | 关键特性 |
|---|---|---|
read_config.py |
读取配置 | 支持 --field 指定字段、--tree 树形输出、--keys 键列表 |
fix_enum_field.py |
修复枚举值 | 自动从日志解析错误、备份原配置、回滚机制 |
fix_json.py |
修复 JSON 格式 | 迭代修复、最多 5 轮、自动备份 |
check_health.py |
健康检查 | 支持 --nagios/--json 输出、容器状态检测 |
脚本自动适配：
- 自动检测
docker composevsdocker-compose - 自动查找项目目录（当前目录 →
~/openclaw→~/openclaw-devkit→ 环境变量） - 超时控制（日志 30s、doctor 60s、healthz 10s）
Step 1: 读日志
cd ~/openclaw && docker compose logs --tail=100 openclaw-gateway 2>&1
常见错误模式（按优先级）：
| 模式 | 含义 | 优先级 |
|---|---|---|
invalid config: must be equal to one of the allowed values |
枚举字段非法 | P0 |
JSONDecodeError / SyntaxError |
JSON 格式损坏 | P0 |
previously repaired, skipping |
sentinel 阻止修复 | P1 |
EACCES / ENOENT |
路径/权限问题 | P1 |
Config invalid (无具体字段) |
schema 校验失败 | P1 |
unauthorized / token |
认证配置问题 | P1 |
保存关键错误行，供后续分析。
Step 2: 读取配置并定位问题字段
在容器内读取配置（使用 read_config.py）：
# 完整配置
cd ~/openclaw && docker compose exec -T openclaw-gateway runuser -u node -- \
python3 /home/node/.claude/skills/openclaw-config-fix/scripts/read_config.py
# 指定字段（如日志报告 permissionMode 问题）
cd ~/openclaw && docker compose exec -T openclaw-gateway runuser -u node -- \
python3 /home/node/.claude/skills/openclaw-config-fix/scripts/read_config.py \
--field plugins.entries.acpx.config.permissionMode
# 树形结构（快速浏览）
cd ~/openclaw && docker compose exec -T openclaw-gateway runuser -u node -- \
python3 .../read_config.py --tree --max-depth 2
检查 sentinel（判断 entrypoint 是否跳过了自动修复）：
cd ~/openclaw && docker compose exec -T openclaw-gateway \
test -f /home/node/.openclaw_initialized && \
echo "sentinel 存在（修复被跳过）" || echo "sentinel 不存在"
Step 3: 查询官方资料确认根因
已知问题库（优先查阅）
references/known-issues.md 包含所有已知问题的错误信息、根因和修复方法。
先查这里 — 大多数问题可以快速定位。
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 268 lines · 119 tokens per session scan A 770ba47f58da
openclaw-config-fix is a skill published in the GitHub repository hrygo/hotplex-legacy (11 stars, last pushed 4mo ago), licensed MIT. It adds 119 tokens to every session and 2,389 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
lsp-inspect
Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…
lsp-dead-code
Enumerate exported symbols in a file and surface those with zero references across the workspace. Use when auditing for dead code, cleaning up APIs, or checking which exports are safe to remove.
lsp-refactor
End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.
lsp-safe-edit
Wrap any code edit with before/after diagnostic comparison. Speculatively previews the change first (previewedit), then applies to disk only if the error delta is acceptable. If post-edit errors appear, surfaces code actions for quick fixes. Handles single and multi-file edits.
lsp-understand
Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source. Broader than lsp-explore: accepts files, synthesizes multi-symbol relationships, and produces a navigable dependency map.
lsp-edit-export
Safe workflow for editing exported symbols or public APIs. Use when changing a function signature, modifying a public type, or altering any symbol used outside its own package — finds all callers first so nothing breaks silently.