clickup
Skill38 starsChanged 8 months agoMITView on GitHub
Manage ClickUp tasks, lists, spaces, time tracking and comments via REST API
7 other projects use a version of this.
Adopted by
Most recently taken up by
- pjmuller/skillstheir own version, first seen Oct 23, 2026
- krodak/clickup-clitheir own version, first seen Oct 13, 2026
- chriswestt/claude-skillstheir own version, first seen Oct 9, 2026
- jholhewres/devclaw-skillstheir own version, first seen Oct 9, 2026
- civitai/civitaitheir own version, first seen Oct 8, 2026
- rcdelfin/agentkittheir own version, first seen Aug 28, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- civitai/civitai★ 7.3ksame name
- krodak/clickup-cli★ 123same name
- apideck-libraries/api-skills★ 4same name
- jholhewres/devclaw-skills★ 4same name
- pjmuller/skills★ 2same name
- rcdelfin/agentkit★ 2same name
- chriswestt/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- abacatepaySkill
- appsignalSkill
- cloudflareSkill
- cloudinarySkill
- datadogSkill
- digitaloceanSkill
- discordSkill
- firebaseSkill
- flyioSkill
- google-sheetsSkill
- herokuSkill
- honeybadgerSkill
- hostingerSkill
- hubspotSkill
- intercomSkill
- jiraSkill
- linearSkill
- mercadopagoSkill
- n8nSkill
- notionSkill
- openaiSkill
- planetscaleSkill
- posthogSkill
- railwaySkill
- resendSkill
- rewriteSkill
- sentrySkill
- shopifySkill
- slackSkill
- stripeSkill
- supabaseSkill
- trelloSkill
- twilioSkill
- vercelSkill
- xSkill
- zendeskSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 51
If the output is OK, proceed to the Flow section.
- Very specific: line 53
If the output is SETUP_NEEDED, guide the user step by step.
- Distinctive: line 68
If the script outputs an error, the token is invalid.
- Distinctive: line 120
Ask the user to confirm the task name, list, and details before creating.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/clickup
Connect to ClickUp to manage workspaces, tasks, time tracking, comments and more. Pure Ruby, zero gems — stdlib only.
Structure
scripts/
├── auth.rb # Token auth + clickup_request helper (required by all scripts)
├── check_setup.rb # Check if token exists (outputs OK or SETUP_NEEDED)
├── save_token.rb # Save and validate a personal API token
├── teams.rb # List workspaces (teams)
├── spaces.rb # List spaces in a workspace
├── folders.rb # List folders in a space
├── lists.rb # List lists in a folder or space
├── tasks.rb # List tasks in a list (with pagination)
├── task.rb # Get task details
├── search_tasks.rb # Search tasks by name across a workspace
├── create_task.rb # Create a task
├── update_task.rb # Update a task
├── delete_task.rb # Delete a task
├── comments.rb # List comments on a task
├── add_comment.rb # Add a comment to a task
├── time_entries.rb # List time entries
├── start_timer.rb # Start a timer for a task
├── stop_timer.rb # Stop the running timer
└── tags.rb # List tags in a spaceClickUp Hierarchy
Workspace (Team) → Space → Folder (optional) → List → Task → SubtaskIn API v2, "Team" = Workspace and "Project" = Folder.
Setup (check before using)
ruby ~/.claude/skills/clickup/scripts/check_setup.rbIf the output is OK, proceed to the Flow section.
If the output is SETUP_NEEDED, guide the user step by step. Present ONE step at a time, wait for the user to confirm before moving to the next.
Step 1 — Ask the user to get their personal API token:
Go to ClickUp > Settings > Apps > API Token and generate a personal token. Or open: https://app.clickup.com/settings/apps
Copy the token and paste it here.
Step 2 — When the user pastes the token, save it:
ruby ~/.claude/skills/clickup/scripts/save_token.rb 'PASTED_TOKEN'If the script outputs an error, the token is invalid. Ask the user to double-check and try again.
If setup is not complete, DO NOT proceed to the Flow. Complete all steps first.
Flow
The argument $ARGUMENTS may contain a task name or workspace reference.
Step 1: List workspaces
ruby ~/.claude/skills/clickup/scripts/teams.rbPresent the workspaces. If there is only one, use it automatically. Otherwise ask which workspace to work with.
Step 2: Discover hierarchy
ruby ~/.claude/skills/clickup/scripts/spaces.rb TEAM_IDThen drill into spaces, folders, and lists as needed:
ruby ~/.claude/skills/clickup/scripts/folders.rb SPACE_ID
ruby ~/.claude/skills/clickup/scripts/lists.rb FOLDER_ID
ruby ~/.claude/skills/clickup/scripts/lists.rb SPACE_ID --spaceStep 3: Actions
List tasks in a list:
ruby ~/.claude/skills/clickup/scripts/tasks.rb LIST_ID
ruby ~/.claude/skills/clickup/scripts/tasks.rb LIST_ID --page 1
ruby ~/.claude/skills/clickup/scripts/tasks.rb LIST_ID --include-closedGet task details:
ruby ~/.claude/skills/clickup/scripts/task.rb TASK_IDSearch tasks by name:
ruby ~/.claude/skills/clickup/scripts/search_tasks.rb TEAM_ID "search query"
ruby ~/.claude/skills/clickup/scripts/search_tasks.rb TEAM_ID "query" --include-closedCreate a task (requires user confirmation):
Ask the user to confirm the task name, list, and details before creating.
ruby ~/.claude/skills/clickup/scripts/create_task.rb LIST_ID "Task Name"
ruby ~/.claude/skills/clickup/scripts/create_task.rb LIST_ID "Task Name" --description "Details" --status "to do" --priority 3Priority: 1=Urgent, 2=High, 3=Normal, 4=Low
Update a task (requires user confirmation):
Show current task details first, then ask what to change.
ruby ~/.claude/skills/clickup/scripts/update_task.rb TASK_ID '{"status":"in progress","priority":2}'Delete a task (requires user confirmation):
Show the task details first, then ask: "Do you want to delete this task?" Only execute after a "yes".
ruby ~/.claude/skills/clickup/scripts/delete_task.rb TASK_IDList comments:
ruby ~/.claude/skills/clickup/scripts/comments.rb TASK_IDAdd a comment (requires user confirmation):
Show the comment text first, then ask to confirm.
ruby ~/.claude/skills/clickup/scripts/add_comment.rb TASK_ID "Comment text here"List time entries:
ruby ~/.claude/skills/clickup/scripts/time_entries.rb TEAM_ID
ruby ~/.claude/skills/clickup/scripts/time_entries.rb TEAM_ID --start 1700000000000 --end 1710000000000Start a timer (requires user confirmation):
ruby ~/.claude/skills/clickup/scripts/start_timer.rb TEAM_ID TASK_IDStop a timer:
ruby ~/.claude/skills/clickup/scripts/stop_timer.rb TEAM_IDList tags:
ruby ~/.claude/skills/clickup/scripts/tags.rb SPACE_IDNotes
- Pure Ruby, zero gems — stdlib only (json, net/http, uri, fileutils)
- Auth via personal API token (no Bearer prefix — ClickUp uses the raw token)
- Token file:
~/.config/clickup/token(outside the repo, never commit) - Creating, updating, and deleting tasks require explicit user confirmation
- Adding comments and starting timers require user confirmation
- Timestamps are in milliseconds (Unix epoch x 1000)
- Pagination: max 100 tasks per page, use
--page N(0-indexed) - Rate limit: 100 requests/minute per token
- Base URL:
https://api.clickup.com/api/v2
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

