CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

1.67x
Quality

58%

Does it follow best practices?

Impact

92%

1.67x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/clickup-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

This is a comprehensive ClickUp automation skill that covers the major workflows well with clear tool sequences and useful pitfall documentation. Its main weaknesses are significant content repetition (especially around pitfalls), lack of concrete executable examples showing actual tool invocations with sample data, and missing validation/verification steps in workflows that involve task creation and bulk operations. The monolithic structure would benefit from splitting detailed references into separate files.

Suggestions

Deduplicate repeated pitfalls (millisecond timestamps, case-sensitive statuses, team_id = workspace ID) by consolidating them in the Known Pitfalls section only and referencing that section from workflows.

Add at least one concrete example showing an actual MCP tool call with sample input parameters and expected response structure for a common operation like creating a task.

Add explicit validation steps to workflows, e.g., after CLICKUP_CREATE_TASK, verify with CLICKUP_GET_TASK that the task was created with correct properties; for bulk operations, add a deduplication check step.

Consider moving the Quick Reference table and detailed parameter lists into a separate REFERENCE.md file to reduce the main skill's length and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The skill is quite long (~200+ lines) with significant repetition. Pitfalls about millisecond timestamps, case-sensitive statuses, and team_id meaning workspace ID are repeated across multiple sections and again in the 'Known Pitfalls' summary. The quick reference table largely duplicates information already covered in the workflow sections. However, the content is mostly factual and avoids explaining basic concepts Claude would know.

2 / 3

Actionability

The skill provides clear tool names, parameter lists, and sequences, which is good. However, there are no executable code examples or concrete command invocations showing actual MCP tool calls with sample payloads. The guidance is specific about what tools to call and what parameters to pass, but stops short of showing copy-paste-ready examples with sample data.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with numbered steps and labeled as Required/Optional/Prerequisite, which is helpful. However, there are no explicit validation checkpoints or error recovery feedback loops. For example, task creation doesn't include a step to verify the task was created successfully, and bulk operations lack retry/deduplication verification steps despite the pitfall about duplicates being mentioned.

2 / 3

Progressive Disclosure

The content is well-structured with clear sections and headers, but it's a monolithic document with no bundle files to offload detailed content. The detailed parameter lists, pitfalls repeated in multiple places, and the full quick reference table could be split into separate reference files. For a skill of this length and complexity, having everything inline makes it harder to navigate.

2 / 3

Total

8

/

12

Passed

Description

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 does a good job naming the specific platform (ClickUp) and listing concrete entities it operates on, making it distinctive and specific. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill, and the trigger terms could better reflect natural user language rather than platform-specific jargon.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ClickUp tasks, project tracking, or managing ClickUp workspaces.'

Include more natural user-facing trigger terms like 'project tracking', 'assign tasks', 'due dates', 'task status', or 'workspace management' to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete entities and actions: 'tasks, spaces, folders, lists, comments, and team operations' along with the automation context and the instruction to search tools first for current schemas.

3 / 3

Completeness

Clearly answers 'what does this do' (automate ClickUp project management across various entities), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, capping this at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes good domain keywords like 'ClickUp', 'tasks', 'spaces', 'folders', 'lists', 'comments', and 'team operations', but misses common user variations like 'project tracking', 'task management', 'assign tasks', 'due dates', or 'workspace'. The term 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users.

2 / 3

Distinctiveness Conflict Risk

The explicit mention of 'ClickUp' and the specific platform entities (spaces, folders, lists) make this highly distinctive and unlikely to conflict with other project management or generic task skills.

3 / 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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
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.