Name: clickup-automation
Rating: 56.00000000000001 (1 reviews)
Author: administrakt0r

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.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/clickup-automation/SKILL.md

The canonical home for this skill is clickup-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

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.

The body is highly actionable — exact tool slugs, typed params, and a lookup table make the MCP workflows concrete — and well sequenced. Weaknesses are duplicated pitfall content, missing validation checkpoints around destructive/batch operations, and a monolithic single-file structure with no external references.

Suggestions

Add explicit validation/feedback checkpoints for destructive and batch operations, e.g. verify the task via `CLICKUP_GET_TASK` and confirm with the user before `CLICKUP_DELETE_TASK`, and confirm the target count/list before bulk task creation.

De-duplicate the pitfalls: keep either the per-workflow "Pitfalls" blocks or the consolidated "Known Pitfalls" section, not both, to remove the repeated ms-timestamp / case-sensitive-status / hierarchy content.

Move the detailed per-tool parameter reference and the Quick Reference table into a separate reference file (e.g. `references/tools.md`) and link to it from SKILL.md so the main file stays an overview.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient and reference-style (no over-explaining of what ClickUp is), but pitfalls are stated twice — once in each workflow's "Pitfalls" block and again verbatim in the consolidated "Known Pitfalls" section (ms-timestamp dates, case-sensitive status, hierarchy rules). That duplicated material is more than minor trimming, fitting anchor 3 rather than 4.	3 / 5
Actionability	Provides numbered tool sequences with exact slugs (e.g. `CLICKUP_CREATE_TASK`), typed required/optional parameters, enum values (priority 1-4), and a Quick Reference table mapping tasks to tool slugs and key params — concrete, executable MCP guidance with only minor gaps (no example call payload). It sits at anchor 4, short of 5's fully copy-paste-ready examples covering common cases.	4 / 5
Workflow Clarity	Workflows are clearly sequenced with [Prerequisite]/[Required]/[Optional] tags and the Setup section validates connection status (ACTIVE), but destructive operations (`CLICKUP_DELETE_TASK`) and batch operations (bulk task creation, 429 handling) lack explicit validation/feedback-loop checkpoints. The rubric caps workflow_clarity at 3 for destructive/batch skills missing validation, which overrides the otherwise strong sequencing.	3 / 5
Progressive Disclosure	Headers and the Quick Reference table give decent navigation, but ~230 lines of detailed workflows plus a consolidated pitfall reference plus a lookup table are all inlined into the single SKILL.md with zero references out (no bundle files exist). Reference material that belongs in a separate file is inlined, matching anchor 3 rather than 4's "most content appropriately placed".	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.

The description is specific and highly distinctive thanks to the named ClickUp + Rube MCP niche, with good natural trigger terms. Its main weakness is the missing explicit "Use when..." trigger guidance, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to automate ClickUp workflows — creating/updating tasks, navigating spaces, folders, and lists, posting comments, or managing team members via Rube MCP."

Replace the single "Automate" verb with distinct per-domain verbs (e.g. "create and update tasks, navigate spaces/folders/lists, post comments, and manage team members") to lift specificity from domain-naming to concrete actions.

Include a couple of natural synonyms users might say (e.g. "to-dos", "assignees", "due dates") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists six concrete ClickUp domains ("tasks, spaces, folders, lists, comments, and team operations") but bundles them under a single verb "Automate", so it lists several specific actions with minor coverage gaps rather than distinct per-action verbs. It fits anchor 4 better than 5 (which expects multiple distinct concrete actions) and clearly above 3 (which expects only 1-2 concrete actions).	4 / 5
Completeness	It clearly states the "what" ("Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP") but provides no "Use when..." clause or equivalent trigger guidance, which the rubric caps at 3. It is not 4 because the "when" is absent rather than merely weakly explicit.	3 / 5
Trigger Term Quality	Includes natural ClickUp vocabulary a user would say ("ClickUp", "tasks", "spaces, folders, lists, comments", "team operations", "project management") giving good keyword coverage, but lacks synonyms or product-specific variations (e.g. "to-do", "assignee", file extensions). It is above anchor 3 (some relevant keywords, missing variations) and just short of 5 (comprehensive synonyms/extensions).	4 / 5
Distinctiveness Conflict Risk	Naming a specific product ("ClickUp") plus a specific integration channel ("via Rube MCP (Composio)") gives it a clear niche with distinct triggers and minimal conflict risk, matching anchor 5. It is well above 4, which allows minor overlap with closely related 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/clickup-automation/SKILL.md
Commit: 57c135b

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