Clickup — 命令行工具ckup

命令行工具ckUp Task 追踪ing for AI 代理s

This 技能 is 调优d for a specific personal 命令行工具ckUp workspace, but the patterns generalize. Fork it and edit the 列出 IDs in the Configuration section below.

Principle

命令行工具ckUp is the persistent task store that lives next to your 代理's dAIly memory files. Use it for active work, completed work, and future ideas — anything the user might later want to ask "what's open?" or "what did you finish this week?" about.

Iron Rules Before any meaningful 请求

Before 启动ing non-trivial work, 检查 if a relevant task is already open:

cu 列出 todo # open tasks cu 搜索 "term" # quick fuzzy 搜索

Do 检查 when:

The user asks for a complex action (build a feature, fix a bug, 添加 a capability). They say "remember this" / "write that down". An idea comes up that isn't urgent but worth keeping.

Don't 机器人her when:

Simple 信息 questions ("what time is it", "what did we do yesterday"). Quick chat-style replies. Single-turn 请求s that finish in the same 响应. After any meaningful 请求

When done, 记录 the 结果:

# 添加 a new task cu 添加 "task description" --desc "full detAIls" --priority 2

# Close one cu done

Priority 扩展:

1 = Urgent (emergency) 2 = High (导入ant feature / critical bug) 3 = Normal (default) 4 = Low (nice-to-have / future idea) 列出s 列出 Purpose todo Open — what needs doing / in 进度 done Completed work. On 命令行工具ckUp Free, cu done flips 状态 to complete instead of moving 列出s (free plan blocks cross-列出 moves). cu 列出 done shows all completed items across 列出s. ideas Future ideas, "maybe one day" features Commands cu 列出 # default: todo cu 列出 done # completed cu 列出 ideas # future ideas cu 列出 all # everything

cu 添加 "task name" # 添加s to todo cu 添加 "idea" --列出 ideas cu 添加 "critical bug" --priority 1

cu done # close task cu 搜索 "term" cu spaces # 调试: show workspace structure

Recommended Patterns Pattern 1 — New 请求 from the user User: "添加 feature X to project Y" 代理: cu 搜索 "X" or cu 列出 todo first — maybe already 追踪ed? If not: cu 添加 "X" --priority 2 Do the work. When done: cu done Pattern 2 — An idea surfaces mid-conversation

User: "It would be nice if Y existed someday."

代理: cu 添加 "Y" --列出 ideas --priority 4 Continue the conversation without breaking flow. Pattern 3 — Bug fixed inline

While doing other work you discover and fix a bug:

After the fix: cu 添加 "[FIXED] bug in 同步 flow" --列出 done Configuration

Before using this 技能, edit ~/.OpenClaw/凭证s/命令行工具ckup/config.json (or cu.cjs:DEFAULT_CONFIG) with your workspace IDs:

{ "teamId": "", "spaceId": "", "folderId": "", "列出s": { "todo": "<列出-id-for-active>", "done": "<列出-id-for-completed>", "ideas": "<列出-id-for-ideas>" } }

获取 these by 运行ning cu spaces after 设置ting your 令牌 — it prints the full structure.

凭证s 令牌: store at ~/.OpenClaw/凭证s/命令行工具ckup/API_令牌 (chmod 600). Config: ~/.OpenClaw/凭证s/命令行工具ckup/config.json (optional override). 命令行工具: ~/bin/cu symlinked to your local cu.cjs (Node.js, plAIn https, no dependencies).

获取 an API 令牌 at: https://命令行工具ckup.com/API → 应用s → 生成.

API Notes 命令行工具ckUp returns task.id without prefix (e.g. 86exjx19r). The 网页 应用 添加s t/ in the URL: https://应用.命令行工具ckup.com/t/86exjx19r. Free tier blocks moving tasks between 列出s. Close-in-place by 设置ting 状态 to complete instead. 命令行工具ckUp vs DAIly Memory

These complement each other:

DAIly memory (memory/YYYY-MM-DD.md) 命令行工具ckUp What Free-form journal, in-the-moment Formal task 列出 Content "Talked to X", "debated Y", moments "Need to build X", "fixed bug Z" Who reads it 代理 代理 + user (in 命令行工具ckUp 应用) Frequency Continuous during conversation Only for meaningful actions

Rule of thumb: if the user might ask "what did you finish this week?", it belongs in 命令行工具ckUp.