Skip to content
Skills Library
Management & product · Tool integration

clickup-cli

/clickup-cli

ClickUp CLI for managing tasks, sprints, comments, statuses, and Docs. Use when the user needs to interact with ClickUp — creating/editing tasks, checking sprint status, adding comments, linking PRs, managing Docs and pages, or searching tasks. Prefer this CLI over raw API calls.

Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

ClickUp CLI for managing tasks, sprints, comments, statuses, and Docs. Use when the user needs to interact with ClickUp — creating/editing tasks, checking sprint status, adding comments, linking PRs, managing Docs and pages, or searching tasks. Prefer this CLI over raw API calls.

Original author description

ClickUp CLI for managing tasks, sprints, comments, statuses, and Docs. Use when the user needs to interact with ClickUp — creating/editing tasks, checking sprint status, adding comments, linking PRs, managing Docs and pages, or searching tasks. Prefer this CLI over raw API calls.

How it works

  1. When to use
  2. Out of scope
  3. Authentication
  4. Key rules
  5. Quick commands
  6. Common flags
  7. References
  8. Other commands
Original SKILL.md headings · 71 lines, 329 words
SKILL.md preview
---
name: clickup-cli
description: ClickUp CLI for managing tasks, sprints, comments, statuses, and Docs. Use when the user
  needs to interact with ClickUp — creating/editing tasks, checking sprint status, adding comments, linking
  PRs, managing Docs and pages, or searching tasks. Prefer this CLI over raw API calls.
origin:
  type: first-party
---
# ClickUp CLI (`clickup`)

Use the `clickup` CLI instead of raw ClickUp API calls. Handles authentication, git integration,
fuzzy status matching, and custom fields automatically.

## When to use

- Create, edit, view, or search ClickUp tasks
- Check sprint status or recent tasks
- Add comments, link PRs/branches, or manage statuses
- Task IDs: `CU-abc123` or `86abc123`

## Out of scope

- Does NOT replace project management decisions — confirm scope with user first
- Does NOT push code or create PRs — delegate to **`github-cli-workflow`**

## Authentication

```bash
clickup auth login    # store API token
clickup auth status   # verify
```

Config: `~/.config/clickup/config.yml`. Supports per-directory defaults.

## Key rules

1. **Always `--current`** for sprint lists — IDs change every sprint, never hardcode them
2. **Fill ALL fields** when creating tasks (name, description, status, priority, assignee, tags, due-date)
3. **Check `clickup tag list`** before using tags — reuse existing ones
4. **Naming:** `[Work Type] Context — Action (Platform/Scope)` — see `references/task-management.md`
5. **Bulk ops:** pass multiple IDs as positional args; for subtasks view parent with `--json` first

## Quick commands

```bash
clickup task view                     # auto-detects from git branch
clickup task search "query"
clickup task recent --sprint
clickup task create --current --name "[Bug] Auth — Fix X (API)" --priority 2
clickup task edit CU-abc123 --status "in progress"
clickup status list                   # check valid statuses before setting
clickup sprint current
clickup inbox
```

## Common flags

| Flag | Description |
|------|-------------|
| `--json` | JSON output |
| `--jq <expr>` | Filter with jq |
| `--raw`, `-r` | Raw strings with `--jq` |

## References

- `references/task-management.md` — full task view/search/create/edit, naming conventions, multi-list, checklists, git integration
- `references/time-tracking.md` — log, list, timesheet commands
- `references/docs-management.md` — Docs and Pages management

## Other commands

```bash
clickup member list
clickup space list && clickup space select
clickup folder list && clickup folder select
clickup list list --folder 12345 && clickup list select
clickup chat send <channel-id> "message"
```
Files in this package (4)
  • SKILL.md 3 KB
  • references/docs-management.md 2 KB
  • references/task-management.md 4 KB
  • references/time-tracking.md 1 KB

Versions

The database has no other skills named clickup-cli.

Identical content appears in 3 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 916836234f86 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100clickup
    Interact with ClickUp tasks - get task details, view comments, create and manage tasks. Use when working with ClickUp task URLs or IDs.
  • 90clickup
    Use when reading or changing anything in ClickUp via the `cup` CLI - tasks, sprints, comments, Docs, Chat, views, webhooks, or workspace structure. Triggers: task queries, status updates, sprint tracking, creating subtasks, posting comments, threaded replies, standup summaries,…
  • 100sprint-planning
    Use when the user asks about sprint planning, syncing plan docs to ClickUp, managing stories/tasks in bulk, or checking sprint status. Triggers on mentions of sprint, sync, stories, ClickUp bulk operations, or epic planning.
  • 100clickup-core-workflow-a
    Create, reconcile, update, and retire ClickUp tasks with schema validation, durable source identity, and explicit destructive approval. Use when automating task lifecycle work through ClickUp API v2. Trigger with "ClickUp task sync", "create ClickUp tasks", or "ClickUp task CRUD".
  • 100testing-clickup-cli
    Run and manage tests for clickup-cli. Covers unit tests, e2e tests against a real ClickUp workspace, and the test data setup. Use when running tests, adding test coverage, debugging test failures, or setting up test fixtures.
  • 100clickup-core-workflow-b
    Analyze, inventory, and change ClickUp Spaces, Folders, Lists, tags, and views with parent-aware plans and reversible boundaries. Use when managing ClickUp hierarchy through API v2. Trigger with "ClickUp hierarchy", "ClickUp Lists", or "ClickUp views".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.