clickup-automation
Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.
71
58%
Does it follow best practices?
Impact
92%
1.67xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/clickup-automation/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description does a good job of specifying the concrete ClickUp entities it can manage and is clearly distinctive due to the ClickUp branding. However, it lacks an explicit 'Use when...' clause, which hurts completeness, and the trigger terms could be broader to capture more natural user language patterns.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ClickUp, managing projects in ClickUp, creating or updating tasks, or organizing ClickUp workspaces.'
Include more natural user-facing trigger terms like 'project tracking', 'assign tasks', 'due dates', 'workspace', or 'board' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete entities and actions: 'tasks, spaces, folders, lists, comments, and team operations' along with the automation context and the instruction to search tools first for current schemas. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate ClickUp project management across various entities), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good domain keywords like 'ClickUp', 'tasks', 'spaces', 'folders', 'lists', 'comments', and 'team operations', but misses common user variations like 'project tracking', 'task management', 'assign tasks', 'due dates', or 'workspace'. The term 'Rube MCP (Composio)' is technical jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit mention of 'ClickUp' and the specific ClickUp entities (spaces, folders, lists) creates a very clear niche that is unlikely to conflict with other project management or generic task skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive ClickUp automation skill that covers the full workspace hierarchy and major operations with clear tool sequences and useful pitfall documentation. Its main weaknesses are redundancy (pitfalls repeated in multiple places), lack of concrete executable examples showing actual tool invocations with sample payloads, and missing validation/error-recovery steps for destructive or bulk operations. The content would benefit from being more concise and splitting detailed reference material into separate files.
Suggestions
Add concrete tool invocation examples with sample payloads and expected responses for at least the most common workflows (e.g., creating a task with specific parameters).
Consolidate pitfalls into the single 'Known Pitfalls' section and remove duplicates from individual workflow sections to reduce redundancy.
Add explicit validation checkpoints and error-recovery feedback loops, especially before CLICKUP_DELETE_TASK and during bulk task creation (e.g., 'Verify task exists with GET_TASK before deleting').
Split the quick reference table and detailed parameter documentation into a separate REFERENCE.md file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~200+ lines) with some redundancy—pitfalls are repeated across individual workflows and then again in a consolidated 'Known Pitfalls' section (e.g., millisecond timestamps, case-sensitive status, team_id meaning). The quick reference table also duplicates information from the workflows. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter lists, and clear sequences, which is good. However, there are no executable code examples or copy-paste ready commands—everything is described at the tool-call level with parameter names but no concrete invocation examples showing actual payloads or responses. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and labeled as Required/Optional/Prerequisite, which is helpful. However, there are no explicit validation checkpoints or feedback loops for error recovery—particularly important for destructive operations like CLICKUP_DELETE_TASK or bulk task creation that could create duplicates. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's monolithic—all content is inline in a single long file. The toolkit docs link is provided but no content is split into separate reference files. For a skill this long, splitting detailed parameter docs or the quick reference table into separate files would improve navigation. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Lingjie-chen/MT5
- Commit
3069d33
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.