Name: clickup
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

clickup

Clickup integration. Manage project management and ticketing data, records, and workflows. Use when the user wants to interact with Clickup data.

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 ./skills/clickup/SKILL.md

Quality

Content

61%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 gives concrete, executable Membrane commands with a clear connection-state workflow, but it pads the intro with general ClickUp background and exposes destructive actions without validation checkpoints. Trimming the overview and adding a confirm-before-delete step would lift the lowest dimensions.

Suggestions

Cut or shrink the opening "ClickUp is a project management platform..." paragraph; Claude already knows what ClickUp is.

Add a validation/confirmation checkpoint before running destructive actions (delete-task, delete-list), e.g. require an explicit user confirmation or a dry-run listing of what will be deleted.

Move the bulk popular-actions table into a referenced file (e.g. ACTIONS.md) and keep only a few representative examples inline to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and a reference table, but it opens by explaining what ClickUp is ("ClickUp is a project management platform used by individuals and teams...") and includes filler like "This is the fastest way to get a connection," which Claude does not need, matching the anchor for mostly efficient content with some unnecessary explanation.	3 / 5
Actionability	It provides concrete, executable commands throughout (membrane login, connection ensure, action list/run, request) plus a popular-actions table with keys and a proxy flag table, with only minor gaps such as the CONNECTION_ID placeholder, fitting the anchor for mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	The install-auth-connect-poll-search-run sequence is clear and includes a state-based decision tree with a polling feedback loop, but destructive actions (delete-task, delete-list) appear in the action table with no validation or confirmation checkpoint before running, so per the destructive-operation guideline workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	It is a single well-organized file with clearly labeled sections (Overview, Working with Clickup, Popular actions, Best practices) and no nested references, though the large inline action and flag tables could plausibly live in separate files, matching the anchor for good structure with minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

66%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 clearly identifies a product-specific niche and includes both a what- and when-clause, but its actions are generic and it omits the natural ClickUp vocabulary (tasks, lists, spaces) users actually say. Tightening it to concrete actions and richer trigger terms would move it toward the top anchors.

Suggestions

Replace generic verbs ("Manage ... data, records, and workflows") with concrete ClickUp actions such as "create and update tasks, lists, spaces, and folders".

Expand the trigger phrase to include natural user vocabulary: "Use when the user wants to manage tasks, lists, spaces, folders, or tickets in ClickUp."

Keep the explicit 'Use when ...' clause but pair it with a sharper what-list so both halves are equally concrete.

Dimension	Reasoning	Score
Specificity	The description names the domain ("project management and ticketing") and a few generic actions ("Manage ... data, records, and workflows") but lacks concrete ClickUp-specific actions like create tasks, list spaces, or move tickets, so it lands at the anchor with named domain and 1-2 actions that are not comprehensive.	3 / 5
Completeness	It states both what it does ("Manage project management and ticketing data, records, and workflows") and an explicit when ("Use when the user wants to interact with Clickup data"), but the when-clause is generic and could name concrete triggers, matching the anchor where both are present but when could be more specific.	4 / 5
Trigger Term Quality	It includes relevant natural terms ("Clickup," "project management," "ticketing," "interact with Clickup data") but misses common variations and synonyms users would say ("tasks," "spaces," "lists," "tickets"), matching the anchor for some relevant keywords with missing synonyms.	3 / 5
Distinctiveness Conflict Risk	Tied to a single named product ("Clickup integration") with a product-specific trigger ("interact with Clickup data"), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	15 / 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: membranedev/application-skills
Path: skills/clickup/SKILL.md
Commit: f484c82

Reviewed: ~10 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.