Get a weekly ClickUp status report for every list your team works in

SKILL.md---
name: clickup-weekly-status-report
description: "Every Friday: tasks completed, in progress and blocked in each ClickUp list, and what is due next week, ready for the weekly update. Use when the user asks for this, or when it runs on a schedule."
---

# ClickUp weekly status report

Every Friday: tasks completed, in progress and blocked in each ClickUp list, and what is due next week, ready for the weekly update.

Friday's status update in ClickUp usually means switching between list views, counting what closed and copying blockers into a doc. Project managers do it from memory when the week was busy, and the blocked task that matters most gets left out.

The agent reads each list you name, counts what was completed this week, what is in progress and what is blocked, and lists the tasks due next week. Each blocked task comes with its assignee and what it is waiting on, so the update says what is needed, not only what is late.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- The official ClickUp MCP server (`https://mcp.clickup.com/mcp`, OAuth), or a personal API token in `CLICKUP_API_TOKEN` for API v2.
- The list IDs to cover, and the status name your team uses for blocked work.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Count what was completed** (ClickUp): For each list call `GET /api/v2/list/{list_id}/task` with `include_closed=true`, `subtasks=true` and `date_done_gt` set to Monday 00:00 in Unix milliseconds, paging with `page` (100 tasks per page).
2. **Read the open work** (ClickUp): Call the same endpoint without `include_closed` and read each task's `status.status`, `assignees` and `dependencies`. A task is blocked when its status is your blocked status (Blocked by default) or it waits on another open task.
3. **Find next week's due dates** (ClickUp): Call it once more with `due_date_gt` next Monday and `due_date_lt` the Sunday after, in milliseconds, and mark the ones that are already blocked.
4. **Write the report**: One row per list with done, in progress, blocked and due next week; then the blocked tasks with assignee and what they wait on; then next week's due tasks. Save the done count so next Friday can compare.

## Route B: the browser

### What you need

- Signed in to ClickUp as a member or guest with view access to each List; the Dependencies column needs the ClickApp enabled in the Space.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://app.clickup.com. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Open each list**: Open `https://app.clickup.com`, which opens your Workspace. In the sidebar open the first List you report on, in **List** view, grouped by **Status**.
2. **Count the week's completions**: Turn on **Show closed** (the **Closed** toggle in the view bar) and add a filter **Date closed** is **This week**. Count the closed tasks, then remove that filter.
3. **Read open and blocked work**: With closed tasks hidden again, count tasks in your in-progress statuses and in **Blocked**. Show the **Dependencies** column: a task that is "waiting on" another open task counts as blocked too. Note each blocked task's assignee and what it waits on.
4. **Find next week's due dates**: Add a filter **Due date** is **Next week** and note the tasks, marking the ones that are already blocked. Repeat the three filters for each List.
5. **Write the report**: One row per list with done, in progress, blocked and due next week, then the blocked tasks with assignee and what they wait on, then next week's due tasks and the blocker to clear first.

Note: Filters you add to a shared view are saved for everyone unless you discard them; use the filter bar's temporary filters or a personal view. For more than five or six Lists, a ClickUp Dashboard with status and closed-this-week cards is quicker than filtering each List.

## The report

- **Per list**: done this week, in progress, blocked, and due next week.
- **Blocked tasks**: task, list, assignee and what it waits on.
- **Due next week**, with the blocked ones marked.
- One line on the blocker to clear first.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "clickup-weekly-status-report/<date of this run, e.g. 2026-10-16>",
  "item_key": "clickup-weekly-status-report",
  "project": "Acme",
  "source": "ClickUp weekly status report skill",
  "kind": "update",
  "title": "38 tasks done this week across 4 lists",
  "summary": "**38 done**, **27 in progress** and **5 blocked** across Web, Mobile, Content and Ops. **14 tasks** are due next week, and 3 of them are already blocked.",
  "widget": [
    {
      "type": "Table",
      "props": {
        "columns": [
          "List",
          "Done",
          "In progress",
          "Blocked",
          "Due next week"
        ],
        "align": [
          "left",
          "right",
          "right",
          "right",
          "right"
        ],
        "rows": [
          [
            "Web",
            14,
            9,
            2,
            5
          ],
          [
            "Mobile",
            9,
            8,
            1,
            4
          ],
          [
            "Content",
            11,
            6,
            0,
            3
          ],
          [
            "Ops",
            4,
            4,
            2,
            2
          ]
        ]
      }
    },
    {
      "type": "Table",
      "props": {
        "columns": [
          "Blocked task",
          "List",
          "Assignee",
          "Waiting on"
        ],
        "align": [
          "left",
          "left",
          "left",
          "left"
        ],
        "rows": [
          [
            "Checkout redesign QA",
            "Web",
            "Sam",
            "Payment sandbox access"
          ],
          [
            "Pricing page copy",
            "Web",
            "Dana",
            "Final prices"
          ],
          [
            "Push notification opt-in",
            "Mobile",
            "Lena",
            "Legal review"
          ],
          [
            "Status page migration",
            "Ops",
            "Theo",
            "DNS change approval"
          ],
          [
            "Backup restore drill",
            "Ops",
            "Marco",
            "Maintenance window"
          ]
        ]
      }
    },
    {
      "type": "Callout",
      "props": {
        "text": "3 of next week's 14 due tasks are blocked: checkout redesign QA, push notification opt-in and the status page migration.",
        "tone": "warn"
      }
    }
  ]
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

## Run it on a schedule

Suggested: Fridays at 15:00 (`0 15 * * 5`). From cron, with the agent signed in on that machine:

```bash
0 15 * * 5 claude -p "Run the clickup-weekly-status-report skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/clickup-weekly-status-report#schedule

Source: https://briefkin.dev/skills/clickup-weekly-status-report