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.

1.67x

Quality

70%

Does it follow best practices?

Impact

92%

1.67x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/clickup-automation/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, information-dense reference with concrete tool sequences and genuinely useful pitfalls, weakened by internal duplication, no destructive-operation validation steps, and a monolithic single-file layout that inlines what should be split into reference files.

Suggestions

Add validation checkpoints for destructive and batch operations, e.g. fetch and display the task via CLICKUP_GET_TASK before CLICKUP_DELETE_TASK, and verify created task IDs after bulk creation.

Deduplicate the 'Known Pitfalls' section against per-workflow Pitfalls, keeping one canonical location and cross-referencing it.

Move the Quick Reference table and per-tool parameter details into a references/ file (e.g. reference/tools.md) and keep SKILL.md as an overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is dense and free of concept over-explanation, but pitfalls stated per workflow are repeated nearly verbatim in 'Known Pitfalls' (case-sensitive status, ms timestamps, team_id meaning), and the 20-row Quick Reference table re-lists parameters already tabulated — it could be tightened, matching anchor 3 rather than anchor 4's 'minor instances'.	3 / 5
Actionability	Concrete tool slugs, typed parameter lists ('due_date: Unix timestamp in milliseconds', 'priority: 1 (Urgent)...4 (Low)') and specific quirks give mostly executable guidance, but no example tool-call payloads are shown, leaving minor gaps versus the copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	Sequences are clearly ordered with [Prerequisite]/[Required]/[Optional] markers and setup includes connection-status validation, but destructive and batch operations lack validation checkpoints — 'Permanently remove a task' (CLICKUP_DELETE_TASK) has no verify-before-delete step and bulk creation only mentions 'track created task IDs' — so the batch/destruction cap holds the score at 3.	3 / 5
Progressive Disclosure	At ~230 lines with no bundle files, all per-tool API detail (full parameter tables and the Quick Reference) is inlined in SKILL.md; section structure is good, but content that belongs in separate reference files is inline, matching anchor 3.	3 / 5
	Total	13 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strongly differentiated, reasonably specific description that names the integration and the ClickUp objects it covers. Its main weakness is the missing 'when to use' trigger clause, which caps completeness and limits natural trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions ClickUp, asks to create or assign tasks, or wants to manage a ClickUp workspace.'

Include common user phrasings as trigger synonyms — 'assign a task', 'due dates', 'subtasks', 'workspace' — to raise trigger term coverage.

Lead with 2-3 concrete verbs (create/update tasks, resolve IDs to list_ids, comment) instead of the single generic 'Automate'.

Dimension	Reasoning	Score
Specificity	Enumerates concrete objects ('tasks, spaces, folders, lists, comments, and team operations') anchored to a specific integration ('via Rube MCP (Composio)'), but the single generic verb 'Automate' leaves minor gaps versus the comprehensive multi-action anchor 5.	4 / 5
Completeness	The 'what' is clear (automating ClickUp objects via Rube MCP), but there is no 'Use when...' or equivalent trigger guidance — 'Always search tools first' is an instruction, not a usage trigger — so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural terms like 'ClickUp', 'tasks', 'comments', and 'team' match what users would say, but common variations such as 'assign', 'due dates', 'subtasks', or 'workspace' are missing, fitting anchor 4 rather than the comprehensive synonym coverage of 5.	4 / 5
Distinctiveness Conflict Risk	The description is tightly niched to ClickUp via Rube MCP (Composio), so it would only conflict with another ClickUp-specific skill; it matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk' and is clearly above anchor 4's minor-overlap framing.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/clickup-automation/SKILL.md
Commit: 10bfc43

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.