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

72%

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

75%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.

The body is highly actionable with clearly sequenced workflows and verification checkpoints, and it is well-structured for navigation. Its main weakness is conciseness: pitfalls and tool listings are duplicated across sections, inflating the token budget without adding new information.

Suggestions

Remove the duplicate global "Known Pitfalls" section or the per-workflow "Pitfalls" blocks, cross-referencing one from the other instead of restating, to cut repeated content.

Either trim the Quick Reference table to only tools not already detailed in workflow sequences, or move it to a separate reference file and link to it, reducing inline duplication.

Add an explicit confirm/verify step before CLICKUP_DELETE_TASK (e.g., GET_TASK to confirm the target) and a spelled-out "on 429, wait Retry-After then retry" loop to close the validation gap for destructive and batch operations.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and never explains concepts Claude already knows, but pitfalls are stated twice (once per workflow under "Pitfalls" and again globally under "Known Pitfalls") and the Quick Reference table repeats tool slugs already enumerated in each workflow, so it could be tightened.	3 / 5
Actionability	Provides exact tool slugs, typed key parameters with concrete values (priority 1-4, millisecond timestamps, status case-sensitivity), and copy-paste-ready call sequences covering the common cases, which is fully actionable guidance for an instruction-only MCP-tool skill.	5 / 5
Workflow Clarity	Each workflow has a numbered tool sequence with [Prerequisite]/[Required]/[Optional] tags and verification checkpoints (confirm ACTIVE connection, GET_LIST to validate statuses, GET_TASK to verify existence before commenting); the minor gap is no explicit confirm-before-delete step for the destructive CLICKUP_DELETE_TASK and no spelled-out 429 retry loop, so it sits just below the top anchor.	4 / 5
Progressive Disclosure	Content is organized into clear, navigable sections (Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) with no nested references, and the single external link is a docs pointer rather than a bundle file; the minor gap is that the ~230-line body is monolithic with the Quick Reference and consolidated pitfalls arguably separable, so it does not quite reach the one-level-deep reference ideal.	4 / 5
	Total	16 / 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.

The description is well-scoped to ClickUp with strong distinctiveness and good trigger-term coverage, but it omits an explicit "Use when..." trigger clause, which caps completeness. Specificity is strong on capability breadth but uses a generic governing verb.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to create, update, or query ClickUp tasks, navigate workspace hierarchy, or manage comments and team members."

Replace the generic "Automate" with a few distinct concrete verbs (e.g., "Create and update tasks, browse spaces/folders/lists, post comments, and look up team members") to lift specificity toward the top anchor.

Include a couple of natural user phrasings or synonyms (e.g., "manage ClickUp projects", "find tasks") to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names six concrete capability areas ("tasks, spaces, folders, lists, comments, and team operations"), but the governing verb is generic ("Automate"), so distinct concrete actions are implied rather than enumerated, leaving minor gaps versus the comprehensive-anchor example.	4 / 5
Completeness	The "what" is clear and comprehensive ("Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations"), but there is no "Use when..." clause or equivalent explicit trigger guidance; the trailing "Always search tools first" is an instruction, not a trigger, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say ("ClickUp", "tasks", "lists", "comments", "team operations", "project management"), but lacks common synonyms or phrasings a user might utter (e.g., "create tasks", "manage projects"), so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	Explicitly scoped to ClickUp via Rube MCP (Composio), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	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: a9fa86d

Reviewed: about 20 hours 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.