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

—

Does it follow best practices?

Impact

92%

1.67x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

A highly actionable, well-structured ClickUp automation skill with concrete tool sequences and parameter detail, held back by duplicated pitfalls, missing feedback loops for batch/destructive ops, and a monolithic structure with no progressive file disclosure.

Suggestions

De-duplicate pitfalls: keep each gotcha in one place (either the per-workflow 'Pitfalls' block or 'Known Pitfalls', not both) and cross-reference instead.

Add an explicit validation/feedback loop for batch and destructive operations, e.g. 'After bulk CREATE_TASK, verify via CLICKUP_GET_TASKS that the count matches and no duplicates appeared; retry only missing items' and 'Confirm task_id with CLICKUP_GET_TASK before CLICKUP_DELETE_TASK.'

Split detailed parameter reference into a referenced file (e.g. REFERENCE.md) so SKILL.md stays a concise overview pointing one level deep, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of basic-concept padding, but pitfalls are duplicated across per-workflow 'Pitfalls' blocks and the 'Known Pitfalls' section (e.g. case-sensitive status, ms timestamps, team_id meaning Workspace ID), so it could be tightened; not the score-3 'every token earns its place'.	2 / 3
Actionability	It provides concrete tool slugs, exact typed parameters ('due_date: Unix timestamp in milliseconds', 'priority: 1 (Urgent), 2 (High)...'), and actionable quirks (URL-encoding spaces), matching the score-3 'fully executable ... copy-paste ready' anchor.	3 / 3
Workflow Clarity	Tool sequences are clearly numbered with [Prerequisite]/[Required]/[Optional] tags and the setup has an explicit ACTIVE-status validation checkpoint, but batch (bulk task creation) and destructive (DELETE_TASK) operations lack an explicit validate→fix→retry feedback loop, which per the rubric caps workflow_clarity at 2.	2 / 3
Progressive Disclosure	Sections are well-organized and the Quick Reference table aids navigation, but this is a ~230-line monolithic file with no bundle files and substantial inline reference content (parameter lists, pitfalls) that could be split out, matching the score-2 'content that should be separate is inline' rather than the score-3 overview-with-one-level-references.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific, well-scoped description with strong trigger terms and low conflict risk, weakened only by the absence of an explicit 'Use when' trigger clause.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to create or manage ClickUp tasks, navigate workspaces/spaces/folders/lists, add task comments, or manage team members and seats.'

Add common natural variations to broaden trigger matching: 'ClickUp tasks, to-dos, lists, comments, workspace members, seats.'

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — 'tasks, spaces, folders, lists, comments, and team operations' — rather than vague language, matching the score-3 anchor 'Lists multiple specific concrete actions'; it exceeds the score-2 'Names domain and some actions'.	3 / 3
Completeness	It clearly answers 'what' (automate tasks/spaces/folders/lists/comments/team ops) but lacks any 'Use when...' or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	It uses natural user vocabulary ('ClickUp project management', 'tasks', 'lists', 'comments') a person would say when requesting this, giving good coverage; the only jargon ('Rube MCP (Composio)') is the transport, not the trigger.	3 / 3
Distinctiveness Conflict Risk	The ClickUp-specific scope ('ClickUp project management ... via Rube MCP') is a clear niche with distinct triggers unlikely to conflict with other skills, matching the score-3 anchor.	3 / 3
	Total	11 / 12 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
Commit: 366e45b

Reviewed: 3 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.