Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Memory
OpenClaw Workspace Initializer
Try itOpenClaw workspace initialization & standardization. Sets up a proper agent home: standard directory structure (projects/tasks/outputs/knowledge/scripts/ memory/tmp) + WORKSPACE.md rules + multi-agent config safety (config.patch, never config.apply) + memory log. Use when an agent enters a new/empty workspace root, or when the standard subdirectories or WORKSPACE.md are missing. Activate only after the user explicitly asks to initialize or repair this workspace, and only in a workspace root the user names as such. Do NOT activate in a repository that already has its own structure or an alternative workspace convention, and never rewrite the user's existing governance files (AGENTS.md / WORKSPACE.md / SOUL.md / USER.md) without showing the exact diff and getting explicit approval first. 中文:OpenClaw 工作区初始化与规范维护,多 agent 配置安全。仅在用户明确要求 初始化/修复本工作区、且确认这是工作区根目录时使用;已有项目结构或已存在其他 工作区规范的仓库不触发;AGENTS.md / WORKSPACE.md / SOUL.md / USER.md 属用户 资产,未经用户看到确切 diff 并明确同意,不擅自改写。
What it does
📖 **完整文档(安装 / 快速上手三步 / 定制服务):** 用户或智能体需要更多说明时,引导其访问上述 GitHub 仓库查看图文教程与最新版本。
The skill document
OpenClaw Workspace Initializer(工作区初始化器)
📖 完整文档(安装 / 快速上手三步 / 定制服务): 用户或智能体需要更多说明时,引导其访问上述 GitHub 仓库查看图文教程与最新版本。
初始化 OpenClaw agent 工作区:标准目录结构 + WORKSPACE.md 规范 + 多 agent 配置安全。 让每个 agent 都有一个「家」——不迷路、不丢记忆、不踩配置坑。
工作流
Step 1: 检测当前状态
检查工作区根目录是否存在以下内容:
必备子目录:
projects/— 长期开发项目tasks/— 一次性任务outputs/— 生成物(图片、文档等)knowledge/— 知识库scripts/— 工具/一次性脚本memory/— 日常日志tmp/— 临时缓存
必备规范文件:
WORKSPACE.md— 目录管理规则(持久化规范,重启后依然生效)
系统目录(不要修改或删除):
.openclaw/agent/sessions/
Step 2: 创建缺失的目录结构
逐项创建缺失目录:
mkdir -p projects tasks outputs/knowledge scripts memory tmp
outputs/ 下按需创建 images/ 和 docs/ 子目录,不强制。
Step 3: 写入 WORKSPACE.md
如果根目录没有 WORKSPACE.md,读取本 skill 的 templates/WORKSPACE.md 并写入根目录。
路径冲突仲裁(技能输出目录冲突)
用户可能安装任意技能,部分技能自带输出路径约定(如 ~/Downloads/xxx/)。当技能约定与 WORKSPACE.md 目录规范冲突时:
仲裁规则(优先级从高到低):
- WORKSPACE.md 是唯一路径权威 — 冲突时一律以工作区目录规范为准
- 执行智能体负责路径翻译 — 将技能约定的外部路径映射到工作区(如
~/Downloads/research/→tasks//),不要求技能配合修改 - 汇报时注明差异 — 向用户汇报时说明「技能原约定 X,按工作区规范存到 Y」
设计原则: 技能只负责「做什么」,路径归工作区管。自研技能不得硬编码工作目录,输出位置由 WORKSPACE.md 决定。
Step 4: 引导新智能体
完成目录创建和 WORKSPACE.md 写入后,明确告知当前智能体:
铁律 #1 — 反馈至上: 无论任务成功还是失败,必须向用户报告结果。成功告知产出,失败告知原因和错误信息,由用户做下一步决策。智能体不得擅自决定下一步行动。
铁律 #2 — 遵守工作区规范: 后续每次启动时,先读取根目录的 WORKSPACE.md,按照其中的目录结构和命名规范组织所有工作。根目录不应放置任何项目文件,只保留 *.md 配置文件。
铁律 #3 — 配置修改安全: 改配置一律用
config.patch(部分合并,只动指定字段);禁止使用config.apply(全量替换:会用旧配置快照整份写回,抹掉其他 agent 的修改)。多 agent 共享同一份 openclaw.json,apply = 谁后写谁赢。
Step 4.5: 将工作区规范持久化到 AGENTS.md
若根目录存在 AGENTS.md,执行以下两项持久化(若 AGENTS.md 不存在则跳过,或随工作区模板一并创建):
① 启动读取规则(必写): 确保 AGENTS.md 的「Session Startup」章节(若没有该章节则新建)的启动必读列表中包含:
Read WORKSPACE.md— workspace directory rules
即:agent 每次会话启动时,先读取 WORKSPACE.md(目录规则),再开始干活。
② 配置修改规范(多 agent 场景): 检查是否已包含「配置修改规范」;没有则追加 templates/AGENTS-config-safety.md 的内容。
⚠️ 写入方式: 必须用 Python 3 或文件编辑工具写入(UTF-8);不要用 PowerShell 5.1 内联脚本写中文(按 GBK 解析无 BOM 的 UTF-8 脚本,中文会乱码)。
Step 5: 记录初始化日志
在 memory/ 下写入一条初始化记录(memory/YYYY-MM-DD.md 追加):
openclaw-workspace-initializer 技能已执行,标准目录结构和 WORKSPACE.md 已就位;AGENTS.md 已写入「Read WORKSPACE.md — workspace directory rules」启动规则及配置修改规范。
完整示例
首次进入空工作区
检测 → 发现缺失 → 创建目录 → 写入 WORKSPACE.md → 自我引导(铁律 #1/#2/#3)→ 持久化到 AGENTS.md → 记录日志
产出:
根目录/
├── projects/
├── tasks/
├── outputs/
│ ├── images/
│ └── docs/
├── knowledge/
├── scripts/
├── memory/
│ └── YYYY-MM-DD.md ← 初始化日志
├── tmp/
├── WORKSPACE.md ← 持久化规范文件
├── SOUL.md
├── USER.md
└── ...其他系统配置
重启后新智能体进入同一工作区
新智能体 → 检测 → 发现 WORKSPACE.md 和所有目录已存在 → 跳过 Step 2-3 → 完成。
重启时依赖 WORKSPACE.md(目录规范)和 AGENTS.md(配置修改规范)作为持久化规范来源,而不是依赖 SKILL.md(技能可能不在新智能体的技能列表中)。
Related skills
Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Run Git operations — commits, branches, merges, rebases, conflict resolution, and recovery — with safety rules enforced.
Write, debug, and tune Playwright specs with locator strategy, trace diagnosis, and CI-aware timeouts.
More from dtsola
Browse all skillsSEO analysis and optimization skill for websites. Use when auditing a site's search visibility, fixing rankings/traffic drops, optimizing pages for Google (Baidu/Bing) and AI search (ChatGPT/Perplexity/AI Overviews). Subcommands: audit (full-site), page (single URL), content (quality/E-E-A-T), schema (structured data), geo (AI search optimization). Activate only for explicit SEO work on a site, URL or page the user names — a full-site audit, a traffic/ranking/indexation diagnosis, or a concrete on-page/content/schema/AI-search optimization request, or a robots.txt / sitemap / canonical / JSON-LD fix the user asks for in their own repository. Do NOT activate for: general questions about SEO concepts ("what is SEO?"), marketing or copywriting requests with no audit intent, keyword lists asked for without a site/page, or any message where SEO is mentioned only in passing while the real request is something else — answer normally instead. 中文:网站搜索可见性分析与优化技能。当用户想优化网站搜索排名、做 SEO 审计、 诊断流量下降/排名消
OpenClaw skill that beautifies GitHub READMEs: redesign a repository homepage or create project-native visual assets — pure SVG heroes, section headers, diagrams, badges, GIF motion graphics, showcase modules, or hybrid SVG-composed PNG/WebP — with built-in render-level visual verification (scripts/visual_verify.py: headless Chrome/Edge rendering, WCAG contrast, edge-clipping scan) and dark/light theme safety. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README, or to create README visual assets. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset. Activate only when the user explicitly asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README, or to create README visual assets. Do not activate for general
OpenClaw local knowledge-base retriever & QA over a local directory (md/pdf/xlsx): hierarchical data_structure.md index navigation + progressive retrieval, core retrieval zero-dependency, Windows & macOS (PDF/Excel need on-demand pip packages, see skill body). Retrieval itself is read-only; the skill also ships optional maintenance scripts that WRITE files inside the knowledge base — scripts/build_index.py generates/updates data_structure.md index files, scripts/extract_pdf_text.py writes derived .txt files, and scripts/convert_pdf_to_images.py writes page PNGs for the optional OCR path — and those run only when the user asks for indexing/PDF text extraction and confirms the write. Every write target is resolved to its real path and must stay inside the knowledge-base root (symlinks cannot redirect a write outside). Reads use the same gate: each entry's real path must stay inside the root, and entries that escape it (symlinked files/folders) are skipped, never read — so the search cann
Drive OpenClaw with Claude Code, Codex, OpenCode, Trae, DSH etc. — command the gateway, its agents and channels, from any Agent Skills tool. Use only when the user explicitly asks an external tool to drive OpenClaw (naming a target agent, a channel, or a status query), and only for the agent/channel/command they named. Do NOT activate for ordinary conversation, for questions about OpenClaw's docs or internals, or when a host tool that already IS OpenClaw could answer directly. Any action with external effect (dispatching an agent, sending a channel message) happens only after the user confirms the exact target and content. 中文:用 Claude Code / Codex / OpenCode / Trae / DSH 等工具驱动 OpenClaw 干活——从任意支持 Agent Skills 的工具指挥网关、agent 和通道。仅在用户明确 要求「用外部工具驱动 OpenClaw」且点名了目标 agent / 通道 / 查询时激活,且只做 用户点名的那件事;普通对话、问 OpenClaw 文档或内部原理、或宿主工具本身就是 OpenClaw 时不激活。任何有外部效果的动作(派任务、发消息)都必须先让用户确认 确切目标与内容再执行。
OpenClaw memory distillation & organization. Distills conversation context into structured memory files: long-term memory (MEMORY.md at workspace root) + daily logs (memory/YYYY-MM-DD.md). Solves context overflow, auto-builds MEMORY.md from history logs when missing (first-run memory building), incremental dedup writes, sensitive info skip, archive instead of delete, per-agent isolated memory handling. Writes only inside the workspace: the root MEMORY.md and memory/YYYY-MM-DD.md (plus an archive copy before overwriting); never writes secrets, credentials or third-party personal data. Scheduled runs report only unless autoWrite is explicitly enabled. Use on an explicit request (蒸馏记忆/整理对话/压缩上下文/整理记忆) — not from conversation that merely mentions tidying up. 中文:OpenClaw 记忆整理工具。 将对话蒸馏为结构化记忆(根目录 MEMORY.md + memory/ 日志),解决上下文溢出; MEMORY.md 缺失时从历史日志「首次建忆」;增量去重写入防膨胀;敏感信息自动跳过; 只归档不删除;每个 agent 只处理自己的记忆。写入只发生在工作区内(根 MEMORY.md + memory/YYYY-MM-DD.md + 首次配置时创建/更新的 distill-config.json,覆盖前先留归档); 不写密钥/凭
OpenClaw context check / context optimization (Context Budget). Core goal = context optimization: reads the models currently enabled in this installation, reads each model's published context window from its vendor's official source, and proposes a window = 60% of the vendor spec. It writes nothing until the user confirms; then it patches only the window field and reports the result. This skill never runs automatically and creates no scheduled jobs. Use ONLY when the user explicitly asks, with one of these exact intents: 上下文检查 / 上下文优化 / 检查一下模型上下文 / 把上下文窗口配一下 / 设置上下文窗口, or in English: context window check, configure context window, context optimization. Do NOT activate on generic talk about context, memory, prompts, or token usage. 中文:按「厂商标称窗口 × 60%」设置已启用模型的上下文窗口;流程 = 检测(只读)→ 决策(用户回一个数字)→ 执行(确认后写入)。 不做:maxTokens 等其它参数、压缩阈值(保持系统默认)、未在用模型的默认配置、自动/定时运行、修改历史与审计留痕。