clickup-agent-cli 0.2.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/marketplace.json +20 -0
- package/.claude-plugin/plugin.json +12 -0
- package/README.md +228 -0
- package/dist/clickup.js +4034 -0
- package/package.json +49 -0
- package/skills/clickup/SKILL.md +125 -0
- package/skills/clickup-blocker-report/SKILL.md +93 -0
- package/skills/clickup-capacity-check/SKILL.md +75 -0
- package/skills/clickup-chat/SKILL.md +58 -0
- package/skills/clickup-comments/SKILL.md +67 -0
- package/skills/clickup-custom-report/SKILL.md +125 -0
- package/skills/clickup-fields/SKILL.md +77 -0
- package/skills/clickup-goal-progress/SKILL.md +74 -0
- package/skills/clickup-goals/SKILL.md +71 -0
- package/skills/clickup-project-setup/SKILL.md +102 -0
- package/skills/clickup-spaces/SKILL.md +88 -0
- package/skills/clickup-sprint-closeout/SKILL.md +91 -0
- package/skills/clickup-sprint-planning/SKILL.md +94 -0
- package/skills/clickup-standup/SKILL.md +94 -0
- package/skills/clickup-task-triage/SKILL.md +86 -0
- package/skills/clickup-tasks/SKILL.md +125 -0
- package/skills/clickup-team-report/SKILL.md +131 -0
- package/skills/clickup-time/SKILL.md +87 -0
- package/skills/clickup-time-audit/SKILL.md +85 -0
- package/skills/clickup-users/SKILL.md +122 -0
- package/skills/clickup-views/SKILL.md +65 -0
- package/skills/clickup-webhooks/SKILL.md +61 -0
- package/skills/clickup-weekly-review/SKILL.md +105 -0
|
@@ -0,0 +1,105 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: clickup-weekly-review
|
|
3
|
+
description: Generates a weekly progress report from ClickUp, scoped to any team, department, space, or workspace. Summarizes completed tasks, in-progress work, blockers, and time logged. Use when the user asks for a weekly update, progress report, team summary, department rundown, or wants to know what happened this week.
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
context: fork
|
|
6
|
+
agent: general-purpose
|
|
7
|
+
argument-hint: "[scope - e.g. 'marketing team', space-id, or workspace-id]"
|
|
8
|
+
allowed-tools: Bash(clickup *)
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
# Weekly Review
|
|
12
|
+
|
|
13
|
+
Generate a weekly progress report scoped to whatever the user asks about.
|
|
14
|
+
|
|
15
|
+
## Understanding the Scope
|
|
16
|
+
|
|
17
|
+
The user's request determines what to report on. Interpret `$ARGUMENTS` to figure out the right filters:
|
|
18
|
+
|
|
19
|
+
- **Workspace-wide**: Use `--workspace-id` only
|
|
20
|
+
- **A specific space** (e.g. "marketing", "engineering"): Find the space ID first with `clickup space list`, then filter with `--space-id`
|
|
21
|
+
- **A specific list or folder**: Filter by `--list-id` or `--folder-id`
|
|
22
|
+
- **A specific person**: Filter with `--assignee`
|
|
23
|
+
- **A department or team name**: Search spaces/folders for matching names, then scope to those IDs
|
|
24
|
+
|
|
25
|
+
If no scope is provided, report on the full workspace.
|
|
26
|
+
|
|
27
|
+
## Workflow
|
|
28
|
+
|
|
29
|
+
### Step 1: Resolve the scope
|
|
30
|
+
|
|
31
|
+
```bash
|
|
32
|
+
# If user gave a name (e.g. "marketing"), find the matching space/folder/list
|
|
33
|
+
clickup space list --format json
|
|
34
|
+
|
|
35
|
+
# If user gave an ID, use it directly
|
|
36
|
+
# If no scope, use the configured workspace
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
### Step 2: Gather completed tasks this week
|
|
40
|
+
|
|
41
|
+
```bash
|
|
42
|
+
# Find tasks completed this week (adjust timestamps for current week)
|
|
43
|
+
clickup task search --workspace-id <id> \
|
|
44
|
+
--date-updated-gt <monday-timestamp-ms> \
|
|
45
|
+
--status "complete" --status "closed" \
|
|
46
|
+
--format json
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Add `--space-id`, `--list-id`, or `--assignee` filters based on the resolved scope.
|
|
50
|
+
|
|
51
|
+
### Step 3: Gather in-progress tasks
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
clickup task search --workspace-id <id> \
|
|
55
|
+
--status "in progress" --status "in review" \
|
|
56
|
+
--format json
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
### Step 4: Find overdue tasks
|
|
60
|
+
|
|
61
|
+
```bash
|
|
62
|
+
clickup task search --workspace-id <id> \
|
|
63
|
+
--due-date-lt <now-timestamp-ms> \
|
|
64
|
+
--include-closed false \
|
|
65
|
+
--format json
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
### Step 5: Gather time logged this week
|
|
69
|
+
|
|
70
|
+
```bash
|
|
71
|
+
clickup time list --workspace-id <id> \
|
|
72
|
+
--start <monday-timestamp-ms> --end <friday-timestamp-ms> \
|
|
73
|
+
--format json
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
### Step 6: Check goal progress (if applicable)
|
|
77
|
+
|
|
78
|
+
```bash
|
|
79
|
+
clickup goal list --workspace-id <id> --format json
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
### Step 7: Compile the report
|
|
83
|
+
|
|
84
|
+
Summarize the data into a clear report with sections:
|
|
85
|
+
- **Completed this week**: Count and highlights of finished tasks
|
|
86
|
+
- **In progress**: Tasks actively being worked on
|
|
87
|
+
- **Overdue / Blocked**: Tasks past due or stuck
|
|
88
|
+
- **Time logged**: Total hours, broken down by person if available
|
|
89
|
+
- **Goal progress**: Key result updates (if goals exist for this scope)
|
|
90
|
+
|
|
91
|
+
## Customization
|
|
92
|
+
|
|
93
|
+
The user can refine the report with natural language:
|
|
94
|
+
- "Weekly review for the marketing space" -> filter by marketing space ID
|
|
95
|
+
- "What did Sarah do this week?" -> filter by assignee
|
|
96
|
+
- "Engineering team weekly update" -> find engineering space, filter
|
|
97
|
+
- "Weekly review for list 12345" -> filter by specific list
|
|
98
|
+
- "Give me last week's review" -> adjust date range to previous week
|
|
99
|
+
|
|
100
|
+
## Tips
|
|
101
|
+
|
|
102
|
+
- Use `--format json` for all data gathering, then format the summary as markdown
|
|
103
|
+
- Timestamps are Unix milliseconds. Monday at midnight = start of week
|
|
104
|
+
- If a team/department name doesn't match a space, check folder names too
|
|
105
|
+
- Combine with `clickup comment create` to post the summary back to a task or list
|