Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Memory
OpenClaw Task Progress Tracker
Try itOpenClaw task & project progress tracking. Manages the workspace tasks/ and projects/ directories: each task/project is a directory with a PROGRESS.md card (status + progress log + document index). Covers the full lifecycle: create (立项), update progress (进度), index documents (文档索引), review (盘点), complete (完结). Lightweight, file-based, no CLI, no external services. Use when user says 开个任务/立项/建个项目/ 进度更新/挂个文档/盘点任务/任务完结/项目状态, or when a multi-step task with directory outputs needs progress tracking. 中文:OpenClaw 任务与项目 进度管理工具。管理工作区 tasks/(短期任务)与 projects/(长期项目)目录: 每个任务/项目一个目录 + PROGRESS.md 进度卡(状态 + 进度日志 + 文档索引)。 覆盖全生命周期:立项、进度更新、文档索引、盘点、完结。轻量纯文件, 无 CLI、无外部服务依赖。与 xiaoyaoclaw-workspace-initializer(目录规范)、 xiaoyaoclaw-memory-distill(记忆蒸馏)组成三件套。
What it does
📖 **完整文档(安装 / 快速上手三步 / 定制服务):** 用户或智能体需要更多说明时,引导其访问上述 GitHub 仓库查看图文教程与最新版本。
The skill document
OpenClaw Task Progress Tracker(任务进度跟踪器)
📖 完整文档(安装 / 快速上手三步 / 定制服务): 用户或智能体需要更多说明时,引导其访问上述 GitHub 仓库查看图文教程与最新版本。
🚀 小遥Claw:「把 AI 助手装进自己的电脑」:
🧩 姊妹项目:OpenClaw Workspace Initializer(工作区初始化器)——标准目录结构 + WORKSPACE.md 规范 + 多 agent 配置安全,给每个 OpenClaw agent 一个「家」:
核心理念:对话是一次性的操作窗口,任务状态是持久资产。 模型可能在任何一步跑死——「完成即写」是唯一可靠的保存方式。
工作流总览
用户发起对话
↓
① 意图识别:任务 / 项目 / 普通事务(拿不准就建,宁多勿漏)
↓
② 任务或项目 → 建目录 + PROGRESS.md(含里程碑规划,可调整)
↓
③ 每完成一个里程碑 → 立即更新 PROGRESS.md(原子写入)
↓ ← 中断点:压缩/跑死/异常都在这里被截住,进度不丢
④ 新会话启动 → 检查未完成 PROGRESS.md → 汇报 → 从下一步续跑
↓
⑤ 任务完成 → 标记完成,PROGRESS.md 归档,沉淀进 memory/
Step 1:意图识别
对话开始时判断请求类型:
| 类型 | 判定标准 | 动作 |
|---|---|---|
| 任务 | 一次性、多步骤(3 步以上)、可能跨会话/中断 | 在 tasks// 建 PROGRESS.md |
| 项目 | 长期维护、有迭代版本、会反复回来 | 在 projects// 建 PROGRESS.md |
| 普通事务 | 单步问答、查询、闲聊 | 不建,正常处理 |
兜底铁律:拿不准一律按任务处理。误判「任务→普通事务」= 任务静默丢失;误判「普通事务→任务」只是多一个文件,无害。
目录命名:kebab-case(小写+连字符),遵循 WORKSPACE.md 命名规范。
Step 2:建项(创建 PROGRESS.md)
- 在对应目录创建 PROGRESS.md(用
templates/PROGRESS.md) - 规划里程碑:把任务拆成 3-6 个里程碑(M1, M2, ...)
- 里程碑 = 可独立验证的产出点,也是自动记忆的检查点
- 规划后告知用户:「里程碑已规划,后续可按情况调整」
- 写入目标、初始下一步、创建时间
路径规则:目录与文件位置一律服从 WORKSPACE.md(技能本身不硬编码路径)。
自包含兜底(无 workspace-initializer 也能独立使用):
- 若
tasks/或projects/目录不存在 → 自动mkdir -p创建 - 若工作区没有 WORKSPACE.md → 使用默认约定:工作区根下的
tasks/与projects/ - 若二者都存在 → 一律以 WORKSPACE.md 规范为准
Step 3:里程碑更新(核心规则)
- 完成即写:每完成一个里程碑,立即更新 PROGRESS.md——不等会话结束。跑死前最后一步没写 = 该步进度丢失,所以「完成即写」不是建议是纪律
- 原子写入:先写临时文件再 rename(
.tmp→ 正式名),避免半截文件 - 幂等清单:已完成步骤逐条记录(含时间戳)。恢复时从「下一步」开始,不重复执行已完成步骤的副作用(消息、写入、外部操作)
- 里程碑可调整:任务中途发现规划不合理,更新 PROGRESS.md 的里程碑列表并注明调整原因
Step 4:恢复(新会话启动检查)
AGENTS.md 的 Session Startup 必须包含「任务续跑检查」(模板见 templates/AGENTS-startup-check.md):
- 扫描
tasks/与projects/下所有PROGRESS.md - 找到状态为「进行中」的 → 读取内容
- 向用户汇报:有哪些未完成任务、各自进度到哪、下一步是什么
- 用户确认后从「下一步」续跑;用户未确认前不擅自继续执行(反馈至上铁律)
Step 5:完成与归档
- 任务完成:PROGRESS.md 标记「已完成」+ 完成时间
- 有价值的决策/教训/经验 → 沉淀进
memory/YYYY-MM-DD.md或 MEMORY.md(任务状态 ≠ 记忆,分层存放) - PROGRESS.md 保留在任务目录(任务完结后目录原地保留,按 WORKSPACE.md 规则不删除)
与既有体系的关系
| 体系 | 分工 |
|---|---|
| WORKSPACE.md | 路径权威:目录结构、命名、输出位置一律以它为准 |
| memory/ + MEMORY.md | 记忆层:决策、教训、人脉、偏好(长期语义) |
| PROGRESS.md | 任务状态层:目标、里程碑、已完成清单、下一步(机械事实,可重建) |
| xiaoyaoclaw-workspace-initializer | 工作区规范底座;本技能是其「任务状态」扩展 |
边界(不做什么)
- 不替代 memory 日志(任务状态 ≠ 记忆)
- 不做自动续跑(恢复动作必须用户确认,符合反馈至上铁律)
- 不硬编码路径(一律走 WORKSPACE.md 仲裁)
- 不写密钥/凭证到 PROGRESS.md
Related skills
Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.
Run Git operations — commits, branches, merges, rebases, conflict resolution, and recovery — with safety rules enforced.
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 等其它参数、压缩阈值(保持系统默认)、未在用模型的默认配置、自动/定时运行、修改历史与审计留痕。