Name: clickup-automation
Rating: 57.599999999999994 (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

66%

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-claude/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 well-structured and actionable with concrete tool sequences and typed parameters, but it carries notable redundancy across sections and lacks validation feedback loops for its destructive/batch operations. Splitting reference material into separate files and deduplicating pitfalls would lift it.

Suggestions

Add explicit validation checkpoints before destructive/batch ops, e.g. 'Run CLICKUP_GET_TASK to confirm the task before CLICKUP_DELETE_TASK' and a retry-on-429 loop honoring Retry-After for bulk creation.

Deduplicate: keep pitfalls only in the per-workflow sections or only in 'Known Pitfalls', not both, and consider trimming the Quick Reference table to only tools not already sequenced in a workflow.

Move the Quick Reference table and/or consolidated Known Pitfalls into a one-level-deep reference file (e.g. references/quick-reference.md) referenced from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but material is duplicated — per-workflow 'Pitfalls' blocks reappear in the consolidated 'Known Pitfalls' section, and the 'Quick Reference' table restates tool slugs already detailed in each workflow sequence.	3 / 5
Actionability	Provides concrete tool sequences with [Prerequisite]/[Required]/[Optional] markers, typed key parameters, and specific pitfalls; minor gaps only — no literal call examples, but for an MCP-tool skill the tool names and params are executable guidance.	4 / 5
Workflow Clarity	Steps are clearly numbered and sequenced with prerequisite markers, but destructive and batch operations (CLICKUP_DELETE_TASK, bulk task creation) lack explicit validate→fix→retry checkpoints, which caps workflow clarity at 3 per the rubric's feedback-loop rule.	3 / 5
Progressive Disclosure	Sectioning is clear and well-organized, but the skill is monolithic with no bundle files; reference material like the Quick Reference table and consolidated Known Pitfalls is inlined rather than split into one-level-deep reference files.	3 / 5
	Total	13 / 20 Passed

Description

75%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, distinctive, and names a concrete product niche, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness. Adding a trigger clause would push it toward the top band.

Suggestions

Append a 'Use when...' clause with concrete triggers, e.g. 'Use when the user wants to create or update ClickUp tasks, navigate spaces/folders/lists, or manage comments and team members.'

Add natural synonyms users might say — subtasks, assignees, due dates, tags — to widen trigger coverage.

Keep the third-person voice; it is already correct, so no change needed there.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain — 'tasks, spaces, folders, lists, comments, and team operations' — giving comprehensive coverage rather than a single generic verb.	5 / 5
Completeness	Has a clear 'what' (automate ClickUp project management incl. the listed resources), but there is no 'Use when...' clause or equivalent trigger guidance — the closing 'Always search tools first' is a how, not a when — so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Natural terms users say are present ('ClickUp', 'tasks', 'comments', 'team operations'), but common variations a user might utter (subtasks, assignees, due dates) are absent, so it is not a full 5.	4 / 5
Distinctiveness Conflict Risk	Names a single specific product ('ClickUp ... via Rube MCP (Composio)'), creating a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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-claude/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.