clickup-agent-cli 0.3.0 → 0.4.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,10 +1,10 @@
1
1
  {
2
2
  "name": "clickup-agent-cli",
3
- "version": "0.3.0",
3
+ "version": "0.4.1",
4
4
  "description": "CLI covering the entire ClickUp API v2 surface",
5
5
  "type": "module",
6
6
  "bin": {
7
- "clickup": "./dist/bin/clickup.js"
7
+ "clickup": "dist/clickup.js"
8
8
  },
9
9
  "files": [
10
10
  "dist",
@@ -46,5 +46,13 @@
46
46
  "tsx": "^4.0.0",
47
47
  "typescript": "^5.9.0",
48
48
  "vitest": "^3.0.0"
49
- }
49
+ },
50
+ "repository": {
51
+ "type": "git",
52
+ "url": "https://github.com/henryreith/clickup-cli"
53
+ },
54
+ "bugs": {
55
+ "url": "https://github.com/henryreith/clickup-cli/issues"
56
+ },
57
+ "homepage": "https://github.com/henryreith/clickup-cli#readme"
50
58
  }
@@ -27,6 +27,13 @@ clickup schema <resource>.<action> # Show required/optional fields
27
27
  clickup <resource> <action> --help # Full help text
28
28
  ```
29
29
 
30
+ Agents without a skill-loading system (any platform other than Claude Code) can read every skill in this table directly from the CLI:
31
+
32
+ ```bash
33
+ clickup skill list # All available skills
34
+ clickup skill show <name> # Print a skill's full contents (e.g. clickup-tasks)
35
+ ```
36
+
30
37
  ## Sub-Skills (load when needed)
31
38
 
32
39
  | Skill | What it covers |
@@ -120,6 +120,6 @@ These all work with this recipe:
120
120
  ## Tips
121
121
 
122
122
  - Combine multiple searches if a single query can't capture everything
123
- - Use `clickup schema tasks.search` to discover available filter flags
123
+ - Use `clickup schema task.search` to discover available filter flags
124
124
  - For complex comparisons, run separate searches and merge the results
125
125
  - If the user asks for something the CLI can't filter directly, fetch a broader set and filter in post-processing
@@ -13,7 +13,7 @@ Custom fields are defined at the list level and set on individual tasks.
13
13
  ```bash
14
14
  clickup field list --list-id <id> # List field definitions
15
15
  clickup field set --task-id <id> --field-id <fid> --value <v> # Set a field value
16
- clickup field remove --task-id <id> --field-id <fid> # Clear a field value
16
+ clickup field remove --task-id <id> --field-id <fid> --confirm # Clear a field value
17
17
  ```
18
18
 
19
19
  ### Value formats by field type
@@ -74,10 +74,10 @@ clickup field list --list-id 998877 --format md
74
74
  ```bash
75
75
  clickup attachment upload --task-id <id> --file <path> [--filename <name>]
76
76
  clickup attachment list --task-id <id>
77
- clickup attachment download --task-id <id> --attachment-id <id> [--output <path>]
77
+ clickup attachment download --task-id <id> --attachment-id <id> [--output <path>] [--force]
78
78
  ```
79
79
 
80
- `attachment download` fetches the file with the auth header and writes to `--output` (default: `./attachment-<id>-<title>`). Shows a spinner during download.
80
+ `attachment download` fetches the file with the auth header and writes to `--output` (default: `./attachment-<id>-<title>`). Refuses to overwrite an existing file unless `--force` is passed. Shows a spinner during download.
81
81
 
82
82
  ## Discovery
83
83
 
@@ -76,8 +76,8 @@ For a task template result, set assignees, dates, and custom fields:
76
76
  # Assign team members
77
77
  clickup task update "$TASK_ID" --assignee-add <user-id>
78
78
 
79
- # Set start and due dates (Unix milliseconds)
80
- clickup task update "$TASK_ID" --start-date <ms> --due-date <ms>
79
+ # Set start and due dates (Unix ms, ISO 8601, or relative like "3d", "friday")
80
+ clickup task update "$TASK_ID" --start-date <date> --due-date <date>
81
81
 
82
82
  # Fill in custom fields
83
83
  clickup field set --task-id "$TASK_ID" --field-id <field-id> --value "<value>"
@@ -45,7 +45,7 @@ clickup task update <task-id> --priority 2 --assignee-add 112233 --status "to do
45
45
  clickup tag add --task-id <task-id> --name "bug"
46
46
 
47
47
  # Set a due date if time-sensitive
48
- clickup task update <task-id> --due-date <timestamp-ms>
48
+ clickup task update <task-id> --due-date <date> # Unix ms, ISO 8601, or relative like "3d", "friday"
49
49
  ```
50
50
 
51
51
  ### Step 4: Route to appropriate lists (optional)
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: clickup-tasks
3
3
  description: Creates, updates, searches, and manages ClickUp tasks, subtasks, checklists, dependencies, and attachments. Use when the user asks about tasks, wants to create or find work items, manage subtasks, add checklists, set dependencies, or upload files to tasks.
4
- allowed-tools: Bash(clickup task *), Bash(clickup checklist *), Bash(clickup dependency *), Bash(clickup relation *), Bash(clickup attachment *), Bash(clickup schema tasks*), Bash(clickup schema checklist*)
4
+ allowed-tools: Bash(clickup task *), Bash(clickup checklist *), Bash(clickup dependency *), Bash(clickup relation *), Bash(clickup attachment *), Bash(clickup schema task*), Bash(clickup schema checklist*)
5
5
  ---
6
6
 
7
7
  # ClickUp Tasks
@@ -47,6 +47,8 @@ clickup task update <task-id> [--name <name>] [--description <text>]
47
47
 
48
48
  Priority accepts both integers (`1`-`4`) and strings (`urgent`, `high`, `normal`, `low`). Mapping: urgent=1, high=2, normal=3, low=4.
49
49
 
50
+ `--due-date` and `--start-date` accept Unix timestamps (ms or seconds), ISO 8601 dates (`2026-07-10`), or relative dates (`tomorrow`, `3d`, `friday`, `next monday`).
51
+
50
52
  ### Delete a task
51
53
  ```bash
52
54
  clickup task delete <task-id> --confirm
@@ -104,8 +106,12 @@ clickup relation remove --task-id <id> --links-to <id>
104
106
 
105
107
  ```bash
106
108
  clickup attachment upload --task-id <id> --file <path> [--filename <name>]
109
+ clickup attachment list --task-id <id>
110
+ clickup attachment download --task-id <id> --attachment-id <id> [--output <path>] [--force]
107
111
  ```
108
112
 
113
+ `attachment download` refuses to overwrite an existing file unless `--force` is passed.
114
+
109
115
  ## Common Patterns
110
116
 
111
117
  ```bash
@@ -132,7 +138,7 @@ clickup chat send --channel-id <id> --message "$(clickup task list --list-id <id
132
138
  ## Discovery
133
139
 
134
140
  ```bash
135
- clickup schema tasks # List all task actions
136
- clickup schema tasks.create # Show create fields
137
- clickup schema tasks.list # Show list filter flags
141
+ clickup schema task # List all task actions
142
+ clickup schema task.create # Show create fields
143
+ clickup schema task.list # Show list filter flags
138
144
  ```
@@ -25,7 +25,7 @@ clickup time update <timer-id> --workspace-id <id>
25
25
  [--description <text>] [--duration <ms>] [--start <ts>]
26
26
  [--tag-action <add|remove>] [--tag <name>...] [--billable <bool>]
27
27
 
28
- clickup time delete <timer-id> --workspace-id <id>
28
+ clickup time delete <timer-id> --workspace-id <id> --confirm
29
29
  ```
30
30
 
31
31
  ### Get / History
@@ -77,7 +77,8 @@ clickup time list --workspace-id 9876543 --format md
77
77
 
78
78
  - Duration is always in **milliseconds** (1 hour = 3600000, 1 minute = 60000)
79
79
  - Start timestamps are Unix milliseconds
80
- - `time delete` does **not** require `--confirm` (unlike most delete commands)
80
+ - `time delete` requires `--confirm` in non-interactive mode (like all delete commands)
81
+ - `--billable` accepts only `true` or `false`; anything else errors (exit 2)
81
82
 
82
83
  ## Discovery
83
84