@krodak/clickup-cli 0.21.0 → 1.1.0
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/.claude-plugin/plugin.json +1 -1
- package/README.md +22 -18
- package/dist/index.js +482 -117
- package/package.json +1 -2
- package/skills/clickup-cli/SKILL.md +97 -72
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "clickup-cli",
|
|
3
3
|
"description": "ClickUp CLI skills for managing tasks, sprints, comments, checklists, custom fields, tags, and time tracking via the cup command",
|
|
4
|
-
"version": "
|
|
4
|
+
"version": "1.1.0",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Krzysztof Rodak"
|
|
7
7
|
},
|
package/README.md
CHANGED
|
@@ -29,6 +29,10 @@ Install the CLI, add the skill file to your agent, and it works with ClickUp. No
|
|
|
29
29
|
|
|
30
30
|
The agent reads the skill file, picks the right `cup` commands, and handles everything. You don't need to learn the CLI - the agent does.
|
|
31
31
|
|
|
32
|
+
## Why a CLI and not MCP?
|
|
33
|
+
|
|
34
|
+
A CLI + skill file has fewer moving parts. No server process, no protocol layer. The agent already knows how to run shell commands - the skill file teaches it which ones exist. For tool-use with coding agents, CLI + instructions tends to work better than MCP in practice.
|
|
35
|
+
|
|
32
36
|
## Install
|
|
33
37
|
|
|
34
38
|
You need Node 22+ and a ClickUp personal API token (`pk_...` from [ClickUp Settings > Apps](https://app.clickup.com/settings/apps)).
|
|
@@ -162,14 +166,14 @@ Status: :white_check_mark: implemented | :construction: planned | :no_entry_sign
|
|
|
162
166
|
|
|
163
167
|
### Sprints & Planning
|
|
164
168
|
|
|
165
|
-
| Feature | Command
|
|
166
|
-
| ------------------------ |
|
|
167
|
-
| Active sprint tasks | `cup sprint`
|
|
168
|
-
| List all sprints | `cup sprints`
|
|
169
|
-
| Assigned tasks by status | `cup assigned`
|
|
170
|
-
| Standup summary | `cup summary`
|
|
171
|
-
| Overdue tasks | `cup overdue`
|
|
172
|
-
| Recently updated | `cup inbox`
|
|
169
|
+
| Feature | Command | Status |
|
|
170
|
+
| ------------------------ | ----------------------- | ------------------ |
|
|
171
|
+
| Active sprint tasks | `cup sprint [--folder]` | :white_check_mark: |
|
|
172
|
+
| List all sprints | `cup sprints` | :white_check_mark: |
|
|
173
|
+
| Assigned tasks by status | `cup assigned` | :white_check_mark: |
|
|
174
|
+
| Standup summary | `cup summary` | :white_check_mark: |
|
|
175
|
+
| Overdue tasks | `cup overdue` | :white_check_mark: |
|
|
176
|
+
| Recently updated | `cup inbox` | :white_check_mark: |
|
|
173
177
|
|
|
174
178
|
### Comments
|
|
175
179
|
|
|
@@ -241,10 +245,13 @@ Status: :white_check_mark: implemented | :construction: planned | :no_entry_sign
|
|
|
241
245
|
|
|
242
246
|
### Docs
|
|
243
247
|
|
|
244
|
-
| Feature | Command
|
|
245
|
-
| ----------------- |
|
|
246
|
-
| Search docs | `cup docs
|
|
247
|
-
| View page content | `cup doc <
|
|
248
|
+
| Feature | Command | Status |
|
|
249
|
+
| ----------------- | ------------------------------------ | ------------------ |
|
|
250
|
+
| Search docs | `cup docs [query]` | :white_check_mark: |
|
|
251
|
+
| View page content | `cup doc <docId> <pageId>` | :white_check_mark: |
|
|
252
|
+
| Create doc | `cup doc-create <title>` | :white_check_mark: |
|
|
253
|
+
| Create page | `cup doc-page-create <docId> <name>` | :white_check_mark: |
|
|
254
|
+
| Edit page | `cup doc-page-edit <docId> <pageId>` | :white_check_mark: |
|
|
248
255
|
|
|
249
256
|
### Attachments
|
|
250
257
|
|
|
@@ -299,12 +306,13 @@ Most commands scope to your assigned tasks by default - keeping output small and
|
|
|
299
306
|
|
|
300
307
|
### Config file
|
|
301
308
|
|
|
302
|
-
`~/.config/
|
|
309
|
+
`~/.config/cup/config.json` (or `$XDG_CONFIG_HOME/cup/config.json`):
|
|
303
310
|
|
|
304
311
|
```json
|
|
305
312
|
{
|
|
306
313
|
"apiToken": "pk_...",
|
|
307
|
-
"teamId": "12345678"
|
|
314
|
+
"teamId": "12345678",
|
|
315
|
+
"sprintFolderId": "optional - folder ID to skip auto-detection"
|
|
308
316
|
}
|
|
309
317
|
```
|
|
310
318
|
|
|
@@ -337,10 +345,6 @@ Custom ID resolution uses the `teamId` from your config, which is required (`cup
|
|
|
337
345
|
|
|
338
346
|
**Task links with custom IDs:** The `cup link` command passes both task IDs in a single API request. When both IDs are custom, this works correctly. However, mixing custom and native IDs in a single link command may not work as expected because the ClickUp API applies the `custom_task_ids` flag to all IDs in the request.
|
|
339
347
|
|
|
340
|
-
## Why a CLI and not MCP?
|
|
341
|
-
|
|
342
|
-
A CLI + skill file has fewer moving parts. No server process, no protocol layer. The agent already knows how to run shell commands - the skill file teaches it which ones exist. For tool-use with coding agents, CLI + instructions tends to work better than MCP in practice.
|
|
343
|
-
|
|
344
348
|
## Development
|
|
345
349
|
|
|
346
350
|
```bash
|