agentleFS
ulises-jeremiasulises-jeremias/agent-toolkit/skills/integrations/clickup-cli/SKILL.md

clickup-cli

Skill20 starsChanged 3 months agoMITView on GitHub

ClickUp CLI for managing tasks, sprints, comments, statuses, and Docs. Use when the user

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the clickup CLI instead of raw ClickUp API calls.

    line 11
  2. Distinctive:

    Create, edit, view, or search ClickUp tasks

    line 16
  3. Distinctive:

    Check sprint status or recent tasks

    line 17
  4. Distinctive:

    Add comments, link PRs/branches, or manage statuses

    line 18
  5. Distinctive:

    Does NOT replace project management decisions — confirm scope with user first

    line 23
  6. Very specific:

    Does NOT push code or create PRs — delegate to github-cli-workflow

    line 24
  7. Distinctive:

    Fill ALL fields: when creating tasks (name, description, status, priority, assignee, tags, due-date)

    line 38
  8. Very specific:

    Check clickup tag list: before using tags — reuse existing ones

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

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

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

FlagDescription
--jsonJSON output
--jq <expr>Filter with jq
--raw, -rRaw 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

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"

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.