wrike-automation – skill Agent & Tự động hóa cho agent AI
Tự động hóa quản lý dự án Wrike qua Rube MCP (Composio): tạo tác vụ/thư mục, quản lý dự án, phân công công việc và theo dõi tiến độ. Luôn tìm công cụ trước để lấy schema hiện tại.
Cài skill wrike-automation bằng một lệnh
Chọn công cụ bạn đang dùng, copy lệnh và dán vào terminal. Skill sẽ nằm trong thư mục skills của công cụ đó và sẵn sàng dùng ở phiên làm việc tiếp theo.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/wrike-automation-ea701.tgz | tar xz -C ~/.claude/skills
Gọi trong Claude Code: /wrike-automation – rồi mô tả công việc bạn muốn làm.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/wrike-automation-ea701.tgz | tar xz -C ~/.codex/skills
Gọi trong Codex: $wrike-automation – rồi mô tả công việc bạn muốn làm.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/wrike-automation-ea701.tgz | tar xz -C ~/.hermes/skills
Gọi trong Hermes Agent: /wrike-automation – rồi mô tả công việc bạn muốn làm.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/wrike-automation-ea701.tgz | tar xz -C ~/.deepcode/skills
Gọi trong DeepSeek: /wrike-automation – rồi mô tả công việc bạn muốn làm.
Nội dung SKILL.md
Nội dung SKILL.md gốc bằng tiếng Anh.
Wrike Automation via Rube MCP
Automate Wrike project management operations through Composio's Wrike toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Wrike connection via
RUBE_MANAGE_CONNECTIONSwith toolkitwrike - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. Wrike operations require a valid authenticated connection and its granted permissions; adding an endpoint alone does not grant access.
1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
2. Call RUBE_MANAGE_CONNECTIONS with toolkit wrike
3. If connection is not ACTIVE, follow the returned auth link to complete Wrike OAuth
4. Confirm connection status shows ACTIVE before running any workflows
Write and schema boundaries
Discover the installed tool schema and current vendor behavior before using any slug or parameter below. Confirm the exact workspace, folder and IDs; task creation, assignments, invitations, sharing and deletion are separate user-visible writes. Preview destructive scope and obtain the applicable explicit authorization. Never guess delete/recycle/restore semantics from this historical table, retry an uncertain write, or infer success from an asynchronous launch response; read back the resulting state first.
Core Workflows
1. Create and Manage Tasks
When to use: User wants to create, assign, or update tasks in Wrike
Tool sequence:
1. WRIKE_GET_FOLDERS - Find the target folder/project [Prerequisite]
2. WRIKE_GET_ALL_CUSTOM_FIELDS - Get custom field IDs if needed [Optional]
3. WRIKE_CREATE_TASK - Create a new task [Required]
4. WRIKE_MODIFY_TASK - Update task properties [Optional]
Key parameters:
folderId: Parent folder ID where the task will be createdtitle: Task titledescription: Task description (supports HTML)responsibles: Array of user IDs to assignstatus: 'Active', 'Completed', 'Deferred', 'Cancelled'importance: 'High', 'Normal', 'Low'customFields: Array of {id, value} objectsdates: Object with type, start, due, duration
Pitfalls:
- folderId is required; tasks must belong to a folder
- responsibles requires Wrike user IDs, not emails or names
- Custom field IDs must be obtained from GET_ALL_CUSTOM_FIELDS
- priorityBefore and priorityAfter are mutually exclusive
- Status field may not be available on Team plan
- dates.start and dates.due use 'YYYY-MM-DD' format
2. Manage Folders and Projects
When to use: User wants to create, modify, or organize folders and projects
Tool sequence:
1. WRIKE_GET_FOLDERS - List existing folders [Required]
2. WRIKE_CREATE_FOLDER - Create a new folder/project [Optional]
3. WRIKE_MODIFY_FOLDER - Update folder properties [Optional]
4. WRIKE_LIST_SUBFOLDERS_BY_FOLDER_ID - List subfolders [Optional]
5. WRIKE_DELETE_FOLDER - Delete a folder permanently [Optional]
Key parameters:
folderId: Parent folder ID for creation; target folder ID for modificationtitle: Folder namedescription: Folder descriptioncustomItemTypeId: Set to create as a project instead of a foldershareds: Array of user IDs or emails to share withproject: Filter for projects (true) or folders (false) in GET_FOLDERS
Pitfalls:
- DELETE_FOLDER is permanent and removes ALL contents (tasks, subfolders, documents)
- Cannot modify rootFolderId or recycleBinId as parents
- Folder creation auto-shares with the creator
- customItemTypeId converts a folder into a project
- GET_FOLDERS with descendants=true returns folder tree (may be large)
3. Retrieve and Track Tasks
When to use: User wants to find tasks, check status, or monitor progress
Tool sequence:
1. WRIKE_FETCH_ALL_TASKS - List tasks with optional filters [Required]
2. WRIKE_GET_TASK_BY_ID - Get detailed info for a specific task [Optional]
Key parameters:
status: Filter by task status ('Active', 'Completed', etc.)dueDate: Filter by due date range (start/end/equal)fields: Additional response fields to includepage_size: Results per page (1-100)taskId: Specific task ID for detailed retrievalresolve_user_names: Auto-resolve user IDs to names (default true)
Pitfalls:
- FETCH_ALL_TASKS paginates at max 100 items per page
- dueDate filter supports 'equal', 'start', and 'end' fields
- Date format: 'yyyy-MM-dd' or 'yyyy-MM-ddTHH:mm:ss'
- GET_TASK_BY_ID returns read-only detailed information
- customFields are returned by default for single task queries
4. Launch Task Blueprints
When to use: User wants to create tasks from predefined templates
Tool sequence:
1. WRIKE_LIST_TASK_BLUEPRINTS - List available blueprints [Prerequisite]
2. WRIKE_LIST_SPACE_TASK_BLUEPRINTS - List blueprints in a specific space [Alternative]
3. WRIKE_LAUNCH_TASK_BLUEPRINT_ASYNC - Launch a blueprint [Required]
Key parameters:
task_blueprint_id: ID of the blueprint to launchtitle: Title for the root taskparent_id: Parent folder/project ID (OR super_task_id)super_task_id: Parent task ID (OR parent_id)reschedule_date: Target date for task reschedulingreschedule_mode: 'RescheduleStartDate' or 'RescheduleFinishDate'entry_limit: Max tasks to copy (1-250)
Pitfalls:
- Either parent_id or super_task_id is required, not both
- Blueprint launch is asynchronous; tasks may take time to appear
- reschedule_date requires reschedule_mode to be set
- entry_limit caps at 250 tasks/folders per blueprint launch
- copy_descriptions defaults to false; set true to include task descriptions
5. Manage Workspace and Members
When to use: User wants to manage spaces, members, or invitations
Tool sequence:
1. WRIKE_GET_SPACE - Get space details [Optional]
2. WRIKE_GET_CONTACTS - List workspace contacts/members [Optional]
3. WRIKE_CREATE_INVITATION - Invite a user to the workspace [Optional]
4. WRIKE_DELETE_SPACE - Delete a space permanently [Optional]
Key parameters:
spaceId: Space identifieremail: Email for invitationrole: User role ('Admin', 'Regular User', 'External User')firstName/lastName: Invitee name
Pitfalls:
- DELETE_SPACE is irreversible and removes all space contents
- userTypeId and role/external are mutually exclusive in invitations
- Custom email subjects/messages require a paid Wrike plan
- GET_CONTACTS returns workspace-level contacts, not task-specific assignments
Common Patterns
Folder ID Resolution
1. Call WRIKE_GET_FOLDERS (optionally with project=true for projects only)
2. Navigate folder tree to find target
3. Extract folder id (e.g., 'IEAGKVLFK4IHGQOI')
4. Use as folderId in task/folder creationCustom Field Setup
1. Call WRIKE_GET_ALL_CUSTOM_FIELDS to get definitions
2. Find field by name, extract id and type
3. Format value according to type (text, dropdown, number, date)
4. Include as {id: 'FIELD_ID', value: 'VALUE'} in customFields arrayTask Assignment
1. Call WRIKE_GET_CONTACTS to find user IDs
2. Use user IDs in responsibles array when creating tasks
3. Or use addResponsibles/removeResponsibles when modifying tasksPagination
- FETCH_ALL_TASKS: Use page_size (max 100) and check for more results
- GET_FOLDERS: Use nextPageToken when descendants=false and pageSize is set
- LIST_TASK_BLUEPRINTS: Use next_page_token and page_size (default 100)
Known Pitfalls
ID Formats:
- Wrike IDs are opaque alphanumeric strings (e.g., 'IEAGTXR7I4IHGABC')
- Task IDs, folder IDs, space IDs, and user IDs all use this format
- Custom field IDs follow the same pattern
- Never guess IDs; always resolve from list/search operations
Permissions:
- Operations depend on user role and sharing settings
- Shared folders/tasks are visible only to shared users
- Admin operations require appropriate role
- Some features (custom statuses, billing types) are plan-dependent
Deletion Safety:
- DELETE_FOLDER removes ALL contents permanently
- DELETE_SPACE removes the entire space and contents
- Consider using MODIFY_FOLDER to move to recycle bin instead
- Restore from recycle bin is possible via MODIFY_FOLDER with restore=true
Date Handling:
- Dates use 'yyyy-MM-dd' format
- DateTime uses 'yyyy-MM-ddTHH:mm:ssZ' or with timezone offset
- Task dates include type ('Planned', 'Actual'), start, due, duration
- Duration is in minutes
Quick Reference
| Task | Tool Slug | Key Params |
|------|-----------|------------|
| Create task | WRIKE_CREATE_TASK | folderId, title, responsibles, status |
| Modify task | WRIKE_MODIFY_TASK | taskId, title, status, addResponsibles |
| Get task by ID | WRIKE_GET_TASK_BY_ID | taskId |
| Fetch all tasks | WRIKE_FETCH_ALL_TASKS | status, dueDate, page_size |
| Get folders | WRIKE_GET_FOLDERS | project, descendants |
| Create folder | WRIKE_CREATE_FOLDER | folderI
… (nội dung đầy đủ có trong gói tải về)
Skill liên quan
- x-twitter-scraper – Dùng Xquik cho các quy trình dữ liệu X: tìm kiếm tweet, tra cứu người dùng, xuất danh…
- x402-express-wrapper – Wrapper chính thức của M2MCent (Node.js) để gắn paywall x402 vào API hoặc máy chủ Model…
- yao-meta-skill – Tạo, tái cấu trúc, đánh giá và đóng gói agent skill từ quy trình, prompt, bản ghi hội…
- zendesk-automation – Tự động hóa tác vụ Zendesk qua Rube MCP (Composio): ticket, người dùng, tổ chức, phản…
- zipai-optimizer – Skill tối ưu token siêu gọn cho prompt caching, cắt tỉa log, kiểm tra dựa trên AST và…
- zoho-crm-automation – Tự động hóa tác vụ Zoho CRM qua Rube MCP (Composio): tạo/cập nhật bản ghi, tìm liên hệ…
- zoom-automation – Tự động hóa việc tạo và quản lý cuộc họp Zoom, bản ghi, webinar và theo dõi người tham…
- ai-debt-detector – Dùng sau khi tạo mã, sau khi chấp nhận gợi ý AI, hoặc khi xem xét module do AI viết…