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.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill clickup-automation72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
50%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 effectively lists specific ClickUp operations and is clearly distinguishable from other skills due to platform-specific naming. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and could benefit from more natural user-facing keywords.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about ClickUp, project management in ClickUp, creating tasks, or managing team workflows'
Include more natural user terms like 'project tracking', 'to-do lists', 'assign tasks', 'due dates', or 'workspace management' that users would actually say
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'tasks, spaces, folders, lists, comments, and team operations' along with the automation context and tool search guidance. | 3 / 3 |
Completeness | Describes what it does (automate ClickUp operations) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'ClickUp', 'tasks', 'spaces', 'folders', 'lists', 'comments', and 'team operations', but missing common user variations like 'project tracking', 'to-do', 'assign task', or 'workspace'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly specific to ClickUp platform with distinct triggers; unlikely to conflict with other project management tools due to explicit ClickUp naming and Rube MCP/Composio reference. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill for ClickUp automation with clear workflows, specific parameters, and comprehensive pitfall documentation. The main weakness is length - the content is thorough but could be more concise by externalizing detailed workflow sections and reducing some redundancy between the workflows and quick reference table.
Suggestions
Consider moving detailed workflow sections (Create Tasks, Navigate Hierarchy, etc.) to separate files and keeping SKILL.md as a concise overview with links
Remove the Quick Reference table or the detailed Key Parameters sections - having both creates redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - the Quick Reference table duplicates information from the workflows, and some explanations could be tightened. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Provides specific tool names, exact parameter names with types, concrete values (e.g., priority 1-4, Unix timestamps in milliseconds), and clear tool sequences. The Quick Reference table makes it copy-paste ready for common operations. | 3 / 3 |
Workflow Clarity | Each workflow has numbered steps with clear sequencing, explicit prerequisites marked, and validation checkpoints (e.g., 'Verify task exists', 'Confirm connection status shows ACTIVE'). The pitfalls sections provide error recovery guidance. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~300 lines) and could benefit from splitting detailed workflow content into separate files. The external toolkit docs link is good, but more content could be externalized. | 2 / 3 |
Total | 10 / 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 | |
- 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.