什么是 Wrike？

Openclaw Skills 的 Wrike 技能使开发人员和 AI 智能体能够直接与 Wrike REST API 进行交互。它通过提供用于处理任务、文件夹和项目的统一界面，简化了复杂的项目管理操作。对于需要弥合开发环境与企业项目管理工具之间差距的团队来说，这项技能特别有价值。它处理了 Wrike 生态系统的细微差别，例如文件夹和项目的双重性质，确保 Openclaw Skills 的用户可以精确地实现工作流自动化。

该集成专为可靠性而设计，包括针对美国和欧盟地区的自动数据中心检测以及复杂的速率限制逻辑。通过在 Openclaw Skills 框架内使用此技能，您可以以编程方式管理账户空间、解析任务永久链接，并通过自动评论保持清晰的沟通。该工具确保所有输出都以结构化 JSON 格式返回，使其成为高阶自动化和多智能体协作的理想选择。

下载入口:https://github.com/openclaw/skills/tree/main/skills/tallhamn/wrike

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

Wrike 应用场景

• 为新的开发冲刺自动创建标准化的项目文件夹和任务列表。
• 使用 Openclaw Skills 在多个团队之间同步任务状态和重要性级别。
• 将项目永久链接解析为可用于文档和报告的操作元数据。
• 通过可脚本化的 CLI 命令管理高成交量的任务分配和截止日期更新。
• 批量检索自定义字段数据和工作流状态，用于跨平台数据分析。

1. 配置：用户通过设置存储在本地配置中的 Wrike 永久令牌来初始化技能。
2. 环境检测：CLI 自动识别账户是托管在美服还是欧服，以便正确路由 API 调用。
3. 实体查询：用户执行空间、文件夹或联系人的查询，以获取 Wrike API 所需的字母数字 ID。
4. 执行：发出创建、更新或删除实体的命令，并提供可选的预检模式（dry-run）以在执行前验证逻辑。
5. JSON 处理：该技能返回一个标准的 JSON 对象，其中包含成功状态和原始数据负载，供 Openclaw Skills 进一步处理。

Wrike 配置指南

要在您的 Openclaw Skills 环境中开始使用此技能，请通过 npm 安装该包：

npm install -g claw-wrike

接下来，配置您的 API 令牌。此令牌将用于验证所有请求并检测您的数据中心：

claw-wrike config set --token 

您可以通过拉取账户信息来验证设置：

claw-wrike account

Wrike 数据架构与分类体系

Wrike 技能将数据组织为几个核心实体，所有实体都以包含 ok 和 data 键的 JSON 对象形式返回。以下是组织分类：

请注意，Wrike 使用字母数字字符串作为 ID（例如 IEABMHYCI5P7AYDW），这与浏览器 URL 中的数字 ID 不同。Openclaw Skills 的此技能会自动解析这些标识符以确保 API 的一致性。

name: wrike
description: Manage Wrike tasks, projects, folders, and comments via the Wrike REST API.
metadata: {"openclaw": {"emoji": "??", "requires": {"bins": ["claw-wrike"], "env": ["WRIKE_TOKEN"]}, "primaryEnv": "WRIKE_TOKEN", "install": [{"id": "npm", "kind": "node", "package": "claw-wrike", "bins": ["claw-wrike"], "label": "Install claw-wrike (npm)"}]}}

Wrike CLI

Manage Wrike tasks, projects, folders, and comments. All commands return JSON: {"ok": true, "data": ...} on success, {"ok": false, "error": "..."} on failure.

Setup

claw-wrike config set --token 
# Auto-detects US/EU data center. Token is stored in ~/.claw-wrike/config.json

Quick Reference

claw-wrike   [--flags]

Account & Spaces

claw-wrike account                          # Account info (name, root folder ID, etc.)
claw-wrike space list                       # List all spaces
claw-wrike space get --id               # Get a space

Folders & Projects

Wrike treats folders and projects as the same entity. Projects are folders with extra properties (owners, dates, status).

claw-wrike folder list                      # List all folders (tree structure)
claw-wrike folder list --space          # List folders in a space
claw-wrike folder list --parent         # List child folders
claw-wrike folder get --id              # Get folder details

claw-wrike folder create --parent  --title "Folder name"
claw-wrike folder create --parent  --title "Project name" --project
claw-wrike folder create --parent  --title "Project name" --project --owner  --start-date 2026-03-01 --end-date 2026-06-01
claw-wrike folder create --parent  --title "Folder name" --dry-run   # Preview without creating

claw-wrike folder update --id  --title "New title"
claw-wrike folder update --id  --description "New description"
claw-wrike folder update --id  --add-parent               # Move into another parent
claw-wrike folder update --id  --remove-parent            # Remove from a parent
claw-wrike folder update --id  --dry-run                            # Preview without updating

claw-wrike folder delete --id                                       # Moves to recycle bin
claw-wrike folder delete --id  --dry-run                            # Preview without deleting

Tasks

claw-wrike task list                        # List tasks (default: 100, Active)
claw-wrike task list --folder           # Tasks in a folder/project
claw-wrike task list --space            # Tasks in a space
claw-wrike task list --status Active        # Filter: Active|Completed|Deferred|Cancelled
claw-wrike task list --assignee "Jane"      # Filter by assignee name
claw-wrike task list --importance High      # Filter: High|Normal|Low
claw-wrike task list --limit 20             # Limit results

claw-wrike task get --id                # Full task details (description, custom fields, etc.)

claw-wrike task create --folder  --title "Task name"
claw-wrike task create --folder  --title "Task name" --assignee "Jane" --due 2026-03-01 --importance High
claw-wrike task create --folder  --title "Task name" --dry-run   # Preview without creating

claw-wrike task update --id  --title "New title"
claw-wrike task update --id  --add-assignee "Jane"
claw-wrike task update --id  --remove-assignee "Jane"
claw-wrike task update --id  --due 2026-04-01 --importance Low
claw-wrike task update --id  --status 
claw-wrike task update --id  --dry-run                           # Preview without updating

claw-wrike task delete --id                                      # Moves to recycle bin
claw-wrike task delete --id  --dry-run                           # Preview without deleting

Comments

claw-wrike comment list --task          # List comments on a task
claw-wrike comment add --task  --text "Comment text"
claw-wrike comment update --id  --text "Updated text"
claw-wrike comment delete --id 

Contacts, Workflows, Custom Fields

claw-wrike contact list                     # All contacts (users) in the account
claw-wrike contact get --id             # Single contact details
claw-wrike workflow list                    # Workflows with custom statuses
claw-wrike customfield list                 # All custom field definitions

Utilities

claw-wrike lookup --permalink          # Resolve a Wrike permalink to task details
claw-wrike cache refresh                    # Force refresh cached contacts/workflows/fields
claw-wrike config show                      # Show current config (token masked)

Important Notes

• IDs: Wrike API IDs are alphanumeric strings like IEABMHYCI5P7AYDW. They are NOT the numeric IDs in permalink URLs.
• Assignee resolution: Use names ("Jane", "Jane Doe") or IDs. Names are resolved via cached contacts.
• Custom statuses: Use claw-wrike workflow list to find custom status IDs, then pass them to --status.
• Folders = Projects: A project is a folder with a project property. Use folder commands for both.
• Tasks can have multiple parents: A task can belong to multiple folders/projects.
• Dry run: Use --dry-run on create/update commands to see the API call without executing it.
• Rate limit: ~400 requests/minute. The CLI handles rate limiting and retries automatically.

Before Any Operation

1. Use claw-wrike space list or claw-wrike folder list to find the right container ID.
2. Use claw-wrike workflow list to understand available statuses before changing task status.
3. Use claw-wrike task get --id to read current state before updating.

NEVER

• Never guess task or folder IDs. Always look them up first.
• Never update tasks without reading their current state.
• Never bulk-modify tasks without user confirmation.