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:davepoon/buildwithclaude --skill clickup-automation80
Quality
72%
Does it follow best practices?
Impact
92%
1.67xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/clickup-automation/SKILL.mdDiscovery
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 effectively identifies specific ClickUp entities and operations, making it clear what the skill does. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill. The technical reference to 'Rube MCP (Composio)' and 'search tools first' is implementation detail that doesn't help with skill selection.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user mentions ClickUp, wants to manage tasks, create projects, or automate project workflows'
Include common user action phrases like 'create task', 'assign work', 'track progress', 'manage projects' that users would naturally say
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'tasks, spaces, folders, lists, comments, and team operations' - these are distinct, actionable capabilities within ClickUp project management. | 3 / 3 |
Completeness | Clearly answers 'what' (automate ClickUp operations including tasks, spaces, etc.) but lacks an explicit 'Use when...' clause. The 'when' is only implied by mentioning ClickUp. | 2 / 3 |
Trigger Term Quality | Includes 'ClickUp', 'project management', 'tasks', 'comments' which are natural terms, but missing common variations like 'to-do', 'project tracking', 'task management', or action verbs users might say like 'create task', 'assign'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct with 'ClickUp' as a specific platform identifier and 'Rube MCP (Composio)' as implementation detail. Unlikely to conflict with other project management tools like Jira or Asana skills. | 3 / 3 |
Total | 10 / 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 workflow sequences and comprehensive pitfall documentation. The main weakness is length - the document tries to be both a quick reference and comprehensive guide, resulting in some redundancy. Splitting detailed workflows into separate files would improve token efficiency while maintaining the excellent actionability.
Suggestions
Consider moving detailed workflow sections (Create Tasks, Navigate Hierarchy, etc.) to separate files and keeping SKILL.md as a concise overview with the Quick Reference table
Remove the Quick Reference table duplication by either keeping it as the primary reference or keeping the detailed workflows, not both
| 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 tighter. However, it avoids explaining basic concepts Claude knows and focuses on ClickUp-specific details. | 2 / 3 |
Actionability | Provides concrete tool sequences with specific parameter names, types, and values. Key parameters are clearly documented with exact formats (e.g., Unix timestamps in milliseconds, priority integers 1-4). The Quick Reference table gives copy-ready tool slugs and params. | 3 / 3 |
Workflow Clarity | Each workflow has clear numbered sequences with [Required], [Optional], and [Prerequisite] markers. Includes explicit validation steps (e.g., 'Verify task exists', 'Confirm connection status shows ACTIVE'). Pitfalls sections provide error recovery guidance for each workflow. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~300 lines) and could benefit from splitting detailed workflow documentation into separate files. The Quick Reference table at the end is helpful but the main content could be more concise with references to detailed docs. | 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.