[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-2eb291b3-7faf-4323-b412-60ea7508e67a":3,"$fY7hNdnQvzBb_jLm13L9Ssfal79gBR4g1X9xBYd8J5Tc":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"2eb291b3-7faf-4323-b412-60ea7508e67a","wrike-automation","通过Rube MCP（Composio）自动化Wrike项目管理：创建任务\u002F文件夹，管理项目，分配工作，跟踪进度。始终首先搜索当前架构的工具。","cat_prod_automation","mod_productivity","sickn33,productivity","---\nname: wrike-automation\ndescription: \"Automate Wrike project management via Rube MCP (Composio): create tasks\u002Ffolders, manage projects, assign work, and track progress. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Wrike Automation via Rube MCP\n\nAutomate Wrike project management operations through Composio's Wrike toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Wrike connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wrike`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wrike`\n3. If connection is not ACTIVE, follow the returned auth link to complete Wrike OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Tasks\n\n**When to use**: User wants to create, assign, or update tasks in Wrike\n\n**Tool sequence**:\n1. `WRIKE_GET_FOLDERS` - Find the target folder\u002Fproject [Prerequisite]\n2. `WRIKE_GET_ALL_CUSTOM_FIELDS` - Get custom field IDs if needed [Optional]\n3. `WRIKE_CREATE_TASK` - Create a new task [Required]\n4. `WRIKE_MODIFY_TASK` - Update task properties [Optional]\n\n**Key parameters**:\n- `folderId`: Parent folder ID where the task will be created\n- `title`: Task title\n- `description`: Task description (supports HTML)\n- `responsibles`: Array of user IDs to assign\n- `status`: 'Active', 'Completed', 'Deferred', 'Cancelled'\n- `importance`: 'High', 'Normal', 'Low'\n- `customFields`: Array of {id, value} objects\n- `dates`: Object with type, start, due, duration\n\n**Pitfalls**:\n- folderId is required; tasks must belong to a folder\n- responsibles requires Wrike user IDs, not emails or names\n- Custom field IDs must be obtained from GET_ALL_CUSTOM_FIELDS\n- priorityBefore and priorityAfter are mutually exclusive\n- Status field may not be available on Team plan\n- dates.start and dates.due use 'YYYY-MM-DD' format\n\n### 2. Manage Folders and Projects\n\n**When to use**: User wants to create, modify, or organize folders and projects\n\n**Tool sequence**:\n1. `WRIKE_GET_FOLDERS` - List existing folders [Required]\n2. `WRIKE_CREATE_FOLDER` - Create a new folder\u002Fproject [Optional]\n3. `WRIKE_MODIFY_FOLDER` - Update folder properties [Optional]\n4. `WRIKE_LIST_SUBFOLDERS_BY_FOLDER_ID` - List subfolders [Optional]\n5. `WRIKE_DELETE_FOLDER` - Delete a folder permanently [Optional]\n\n**Key parameters**:\n- `folderId`: Parent folder ID for creation; target folder ID for modification\n- `title`: Folder name\n- `description`: Folder description\n- `customItemTypeId`: Set to create as a project instead of a folder\n- `shareds`: Array of user IDs or emails to share with\n- `project`: Filter for projects (true) or folders (false) in GET_FOLDERS\n\n**Pitfalls**:\n- DELETE_FOLDER is permanent and removes ALL contents (tasks, subfolders, documents)\n- Cannot modify rootFolderId or recycleBinId as parents\n- Folder creation auto-shares with the creator\n- customItemTypeId converts a folder into a project\n- GET_FOLDERS with descendants=true returns folder tree (may be large)\n\n### 3. Retrieve and Track Tasks\n\n**When to use**: User wants to find tasks, check status, or monitor progress\n\n**Tool sequence**:\n1. `WRIKE_FETCH_ALL_TASKS` - List tasks with optional filters [Required]\n2. `WRIKE_GET_TASK_BY_ID` - Get detailed info for a specific task [Optional]\n\n**Key parameters**:\n- `status`: Filter by task status ('Active', 'Completed', etc.)\n- `dueDate`: Filter by due date range (start\u002Fend\u002Fequal)\n- `fields`: Additional response fields to include\n- `page_size`: Results per page (1-100)\n- `taskId`: Specific task ID for detailed retrieval\n- `resolve_user_names`: Auto-resolve user IDs to names (default true)\n\n**Pitfalls**:\n- FETCH_ALL_TASKS paginates at max 100 items per page\n- dueDate filter supports 'equal', 'start', and 'end' fields\n- Date format: 'yyyy-MM-dd' or 'yyyy-MM-ddTHH:mm:ss'\n- GET_TASK_BY_ID returns read-only detailed information\n- customFields are returned by default for single task queries\n\n### 4. Launch Task Blueprints\n\n**When to use**: User wants to create tasks from predefined templates\n\n**Tool sequence**:\n1. `WRIKE_LIST_TASK_BLUEPRINTS` - List available blueprints [Prerequisite]\n2. `WRIKE_LIST_SPACE_TASK_BLUEPRINTS` - List blueprints in a specific space [Alternative]\n3. `WRIKE_LAUNCH_TASK_BLUEPRINT_ASYNC` - Launch a blueprint [Required]\n\n**Key parameters**:\n- `task_blueprint_id`: ID of the blueprint to launch\n- `title`: Title for the root task\n- `parent_id`: Parent folder\u002Fproject ID (OR super_task_id)\n- `super_task_id`: Parent task ID (OR parent_id)\n- `reschedule_date`: Target date for task rescheduling\n- `reschedule_mode`: 'RescheduleStartDate' or 'RescheduleFinishDate'\n- `entry_limit`: Max tasks to copy (1-250)\n\n**Pitfalls**:\n- Either parent_id or super_task_id is required, not both\n- Blueprint launch is asynchronous; tasks may take time to appear\n- reschedule_date requires reschedule_mode to be set\n- entry_limit caps at 250 tasks\u002Ffolders per blueprint launch\n- copy_descriptions defaults to false; set true to include task descriptions\n\n### 5. Manage Workspace and Members\n\n**When to use**: User wants to manage spaces, members, or invitations\n\n**Tool sequence**:\n1. `WRIKE_GET_SPACE` - Get space details [Optional]\n2. `WRIKE_GET_CONTACTS` - List workspace contacts\u002Fmembers [Optional]\n3. `WRIKE_CREATE_INVITATION` - Invite a user to the workspace [Optional]\n4. `WRIKE_DELETE_SPACE` - Delete a space permanently [Optional]\n\n**Key parameters**:\n- `spaceId`: Space identifier\n- `email`: Email for invitation\n- `role`: User role ('Admin', 'Regular User', 'External User')\n- `firstName`\u002F`lastName`: Invitee name\n\n**Pitfalls**:\n- DELETE_SPACE is irreversible and removes all space contents\n- userTypeId and role\u002Fexternal are mutually exclusive in invitations\n- Custom email subjects\u002Fmessages require a paid Wrike plan\n- GET_CONTACTS returns workspace-level contacts, not task-specific assignments\n\n## Common Patterns\n\n### Folder ID Resolution\n\n```\n1. Call WRIKE_GET_FOLDERS (optionally with project=true for projects only)\n2. Navigate folder tree to find target\n3. Extract folder id (e.g., 'IEAGKVLFK4IHGQOI')\n4. Use as folderId in task\u002Ffolder creation\n```\n\n### Custom Field Setup\n\n```\n1. Call WRIKE_GET_ALL_CUSTOM_FIELDS to get definitions\n2. Find field by name, extract id and type\n3. Format value according to type (text, dropdown, number, date)\n4. Include as {id: 'FIELD_ID', value: 'VALUE'} in customFields array\n```\n\n### Task Assignment\n\n```\n1. Call WRIKE_GET_CONTACTS to find user IDs\n2. Use user IDs in responsibles array when creating tasks\n3. Or use addResponsibles\u002FremoveResponsibles when modifying tasks\n```\n\n### Pagination\n\n- FETCH_ALL_TASKS: Use page_size (max 100) and check for more results\n- GET_FOLDERS: Use nextPageToken when descendants=false and pageSize is set\n- LIST_TASK_BLUEPRINTS: Use next_page_token and page_size (default 100)\n\n## Known Pitfalls\n\n**ID Formats**:\n- Wrike IDs are opaque alphanumeric strings (e.g., 'IEAGTXR7I4IHGABC')\n- Task IDs, folder IDs, space IDs, and user IDs all use this format\n- Custom field IDs follow the same pattern\n- Never guess IDs; always resolve from list\u002Fsearch operations\n\n**Permissions**:\n- Operations depend on user role and sharing settings\n- Shared folders\u002Ftasks are visible only to shared users\n- Admin operations require appropriate role\n- Some features (custom statuses, billing types) are plan-dependent\n\n**Deletion Safety**:\n- DELETE_FOLDER removes ALL contents permanently\n- DELETE_SPACE removes the entire space and contents\n- Consider using MODIFY_FOLDER to move to recycle bin instead\n- Restore from recycle bin is possible via MODIFY_FOLDER with restore=true\n\n**Date Handling**:\n- Dates use 'yyyy-MM-dd' format\n- DateTime uses 'yyyy-MM-ddTHH:mm:ssZ' or with timezone offset\n- Task dates include type ('Planned', 'Actual'), start, due, duration\n- Duration is in minutes\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Create task | WRIKE_CREATE_TASK | folderId, title, responsibles, status |\n| Modify task | WRIKE_MODIFY_TASK | taskId, title, status, addResponsibles |\n| Get task by ID | WRIKE_GET_TASK_BY_ID | taskId |\n| Fetch all tasks | WRIKE_FETCH_ALL_TASKS | status, dueDate, page_size |\n| Get folders | WRIKE_GET_FOLDERS | project, descendants |\n| Create folder | WRIKE_CREATE_FOLDER | folderId, title |\n| Modify folder | WRIKE_MODIFY_FOLDER | folderId, title, addShareds |\n| Delete folder | WRIKE_DELETE_FOLDER | folderId |\n| List subfolders | WRIKE_LIST_SUBFOLDERS_BY_FOLDER_ID | folderId |\n| Get custom fields | WRIKE_GET_ALL_CUSTOM_FIELDS | (none) |\n| List blueprints | WRIKE_LIST_TASK_BLUEPRINTS | limit, page_size |\n| Launch blueprint | WRIKE_LAUNCH_TASK_BLUEPRINT_ASYNC | task_blueprint_id, title, parent_id |\n| Get space | WRIKE_GET_SPACE | spaceId |\n| Delete space | WRIKE_DELETE_SPACE | spaceId |\n| Get contacts | WRIKE_GET_CONTACTS | (none) |\n| Invite user | WRIKE_CREATE_INVITATION | email, role |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,191,1835,"2026-05-16 13:47:40",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"效率工具","productivity","mdi-lightning-bolt-outline","文档处理、数据分析、自动化工作流",4,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"自动化","automation","mdi-robot-outline","工作流自动化、批处理",3,101,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"cc6988bb-dc1b-4324-8361-108a12abbf2f","1.0.0","wrike-automation.zip",3933,"uploads\u002Fskills\u002F2eb291b3-7faf-4323-b412-60ea7508e67a\u002Fwrike-automation.zip","d202abfcc78127518177dedae9e95f37ae9de7301d7b36f1a6951b7183815d23","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":9700}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]