clickup-agent-cli 0.4.2 → 0.5.1

package/skills/clickup-release-notes/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: clickup-release-notes
+description: Generates release notes or a changelog from ClickUp tasks completed in a period, grouped by type and written for the chosen audience. Use when the user asks for release notes, a changelog, a "what shipped" summary, or wants completed work written up for customers or stakeholders.
+license: MIT
+disable-model-invocation: true
+context: fork
+agent: general-purpose
+argument-hint: "[period and scope - e.g. 'last sprint for the mobile space', 'June, customer-facing']"
+allowed-tools: Bash(clickup *), Write, Read
+---
+
+# Release Notes
+
+Turn completed tasks into a changelog worth reading.
+
+## Understanding the Scope
+
+From `$ARGUMENTS` determine: the period (default: since the last tag/release the user mentions, else last 14 days), the scope (workspace, space, or list), and the audience. Audience changes the writing: customer-facing notes describe benefits; internal notes can name tasks and people.
+
+## Workflow
+
+### Step 1: Pull completed tasks
+
+```bash
+clickup task search --workspace-id <id> \
+    --include-closed \
+    --status "complete" --status "closed" --status "done" \
+    --date-updated-gt <period-start-ms> --date-updated-lt <period-end-ms> \
+    [--space-id <id>] --format json
+```
+
+`--date-updated-*` filters take Unix ms; compute them from the period.
+
+### Step 2: Classify
+
+Group by tags and task names into: **Features**, **Improvements**, **Fixes**, and **Internal** (refactors, chores - omit for customer-facing notes). Tags like `bug`, `feature`, `enhancement` decide the bucket; otherwise judge from the task name and description.
+
+### Step 3: Write the notes
+
+Rewrite task names for the audience - "Fix login redirect on Safari" becomes "Fixed an issue where Safari users could be redirected to the wrong page after logging in." Never paste raw task IDs into customer-facing notes.
+
+Copy the exact structure from `assets/report-template.md` in this skill's directory (`clickup skill path clickup-release-notes` prints it). Fill every placeholder; drop sections with no content.
+
+For internal notes append task IDs and assignees for traceability.
+
+### Step 4: Deliver
+
+Present the notes in chat. Offer to also:
+
+```bash
+# Publish into a ClickUp Doc
+clickup doc page-create --workspace-id <id> --doc-id <id> \
+    --name "Release Notes <date>" --content "$(cat notes.md)"
+
+# Or save locally
+```
+
+## Tips
+
+- If several statuses mean "done" in this workspace, check `clickup list statuses` conventions first rather than guessing.
+- Exclude subtasks whose parent is already listed to avoid duplicate lines.
+- A count line ("12 improvements shipped by 5 people") makes stakeholder notes land better.

package/skills/clickup-release-notes/assets/report-template.md

@@ -0,0 +1,12 @@
+# Release Notes - <period>
+
+## New
+- <benefit-focused line for each shipped feature>
+
+## Improved
+- <what got better and for whom>
+
+## Fixed
+- <user-visible bug fixes, written as outcomes>
+
+<!-- Internal variant: append task IDs and assignees per line -->

package/skills/clickup-rollout/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-rollout
 description: Rolls out a saved process template in ClickUp by applying it to a target location, then configuring assignees, due dates, and custom fields. Use when the user says "start a new [project/process/sprint/onboarding]" or wants to kick off a repeatable workflow from a template.
+license: MIT
 disable-model-invocation: true
 context: fork
 agent: general-purpose
@@ -12,6 +13,8 @@ allowed-tools: Bash(clickup *)
 
 Apply a saved ClickUp template and configure the resulting task, list, or folder for a new instance of the process.
 
+Interpret `$ARGUMENTS` as the scope (workspace, space, list, person, or time period as the sections below expect); when it is empty, ask or fall back to the configured workspace.
+
 ## Workflow
 
 ### Step 1: Find the template

package/skills/clickup-spaces/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-spaces
 description: Navigates and manages the ClickUp hierarchy including workspaces, spaces, folders, and lists. Use when the user asks about project structure, wants to create spaces or lists, navigate the hierarchy, or find where tasks live.
+license: MIT
 allowed-tools: Bash(clickup workspace *), Bash(clickup space *), Bash(clickup folder *), Bash(clickup list *), Bash(clickup schema workspace*), Bash(clickup schema space*), Bash(clickup schema folder*), Bash(clickup schema list*)
 ---
 

package/skills/clickup-sprint-closeout/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-sprint-closeout
 description: Closes out a sprint by summarizing completion, carrying over incomplete tasks, and preparing retrospective data. Use when the user wants to end a sprint, close out an iteration, move unfinished work, or prepare for a retro.
+license: MIT
 disable-model-invocation: true
 context: fork
 agent: general-purpose
@@ -12,6 +13,8 @@ allowed-tools: Bash(clickup *)
 
 End a sprint cleanly: summarize what was done, carry over incomplete work, and gather data for a retrospective.
 
+Interpret `$ARGUMENTS` as the scope (workspace, space, list, person, or time period as the sections below expect); when it is empty, ask or fall back to the configured workspace.
+
 ## Prerequisites
 
 - Sprint list ID

package/skills/clickup-sprint-planning/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-sprint-planning
 description: Plans a sprint by selecting tasks from backlog, assigning them, setting dates, and organizing into a sprint list. Use when the user wants to plan a sprint, set up an iteration, or pull work from backlog into a sprint.
+license: MIT
 disable-model-invocation: true
 context: fork
 agent: general-purpose
@@ -12,6 +13,8 @@ allowed-tools: Bash(clickup *)
 
 Set up a new sprint by pulling tasks from the backlog, estimating, assigning, and organizing.
 
+Interpret `$ARGUMENTS` as the scope (workspace, space, list, person, or time period as the sections below expect); when it is empty, ask or fall back to the configured workspace.
+
 ## Prerequisites
 
 - Workspace and space IDs known

package/skills/clickup-standup/SKILL.md

@@ -1,11 +1,12 @@
 ---
 name: clickup-standup
 description: Generates a daily standup summary from ClickUp covering what was done yesterday, what is planned today, and blockers. Use when the user asks for a standup report, daily update, or wants to know what they or their team worked on.
+license: MIT
 disable-model-invocation: true
 context: fork
 agent: general-purpose
 argument-hint: "[scope - e.g. 'my tasks', 'engineering team', user-id]"
-allowed-tools: Bash(clickup *)
+allowed-tools: Bash(clickup *), Read
 ---
 
 # Daily Standup
@@ -73,19 +74,7 @@ clickup time running --workspace-id <id> --assignee <user-id> --format json
 
 ### Step 6: Compile standup
 
-Format as:
-
-```
-**Yesterday:**
-- Completed: [list of finished tasks with names]
-
-**Today:**
-- Working on: [list of in-progress tasks]
-- Due today: [list of tasks due today]
-
-**Blockers:**
-- [list of blocked tasks, if any]
-```
+Copy the exact structure from `assets/report-template.md` in this skill's directory (`clickup skill path clickup-standup` prints it). Fill every placeholder; drop sections with no content.
 
 ## Tips
 

package/skills/clickup-standup/assets/report-template.md

@@ -0,0 +1,9 @@
+**Yesterday:**
+- Completed: <finished task names>
+
+**Today:**
+- Working on: <in-progress tasks>
+- Due today: <tasks due today>
+
+**Blockers:**
+- <blocked tasks, or "None">

package/skills/clickup-task-triage/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-task-triage
 description: Triages incoming ClickUp tasks by categorizing, prioritizing, assigning, and routing unprocessed tasks. Use when the user wants to triage tasks, sort through a backlog, prioritize incoming work, or clean up an inbox list.
+license: MIT
 disable-model-invocation: true
 context: fork
 agent: general-purpose
@@ -12,6 +13,8 @@ allowed-tools: Bash(clickup *)
 
 Sort through incoming/unprocessed tasks: prioritize, assign, add tags, and move to the right lists.
 
+Interpret `$ARGUMENTS` as the scope (workspace, space, list, person, or time period as the sections below expect); when it is empty, ask or fall back to the configured workspace.
+
 ## Prerequisites
 
 - Know the inbox/backlog list ID where new tasks land

package/skills/clickup-tasks/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-tasks
 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.
+license: MIT
 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*)
 ---
 

package/skills/clickup-team-report/SKILL.md

@@ -1,11 +1,12 @@
 ---
 name: clickup-team-report
 description: Generates a status report for any team, department, or area of the business in ClickUp. Covers task progress, workload distribution, upcoming deadlines, and highlights. Use when the user asks for a department rundown, team status, what marketing is doing, operations update, or any team/department-specific report.
+license: MIT
 disable-model-invocation: true
 context: fork
 agent: general-purpose
 argument-hint: "[team or department name, e.g. 'marketing', 'engineering', 'operations']"
-allowed-tools: Bash(clickup *)
+allowed-tools: Bash(clickup *), Read
 ---
 
 # Team / Department Report
@@ -101,6 +102,8 @@ Filter time entries to those related to the team's tasks.
 
 ### Step 7: Compile the report
 
+Copy the exact structure from `assets/report-template.md` in this skill's directory (`clickup skill path clickup-team-report` prints it). Fill every placeholder; drop sections with no content.
+
 Structure the report as:
 
 - **Team/Department**: Name and scope of what is covered

package/skills/clickup-team-report/assets/report-template.md

@@ -0,0 +1,24 @@
+# <Team> Status Report (<date>)
+
+**Scope:** <spaces/folders/lists covered>
+**Summary:** <2-3 sentences on where things stand>
+
+## By the numbers
+| To do | In progress | Done this week | Overdue |
+|-------|-------------|----------------|---------|
+| <n> | <n> | <n> | <n> |
+
+## Key accomplishments
+- <completed task worth naming> (<assignee>)
+
+## Currently working on
+- <task> - <assignee>, due <date>
+
+## Upcoming deadlines (next 7 days)
+- <task> - due <date>, <assignee>
+
+## Risks and blockers
+- <overdue or blocked item> - <what unblocks it>
+
+## Time invested
+<n> hours logged this period (<top contributors>)

package/skills/clickup-templates/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-templates
 description: Lists and applies ClickUp templates to create tasks, lists, and folders from saved process templates. Use when the user wants to roll out a repeatable process, create items from a template, or find what templates are available in the workspace.
+license: MIT
 allowed-tools: Bash(clickup template *), Bash(clickup schema template*)
 ---
 

package/skills/clickup-time/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-time
 description: Tracks time in ClickUp including logging entries, managing running timers, tagging time, and querying reports. Use when the user asks about time tracking, wants to start or stop a timer, log hours, check who is working on what, or audit time entries.
+license: MIT
 allowed-tools: Bash(clickup time *), Bash(clickup schema time*)
 ---
 

package/skills/clickup-time-audit/SKILL.md

@@ -1,17 +1,20 @@
 ---
 name: clickup-time-audit
 description: Audits time tracking entries by checking utilization, finding missing entries, and comparing logged vs. estimated time. Use when the user wants to audit time, check billable hours, find unlogged work, or review team utilization.
+license: MIT
 disable-model-invocation: true
 context: fork
 agent: general-purpose
 argument-hint: "[workspace-id] [start-date] [end-date]"
-allowed-tools: Bash(clickup *)
+allowed-tools: Bash(clickup *), Read
 ---
 
 # Time Audit
 
 Audit time tracking data for accuracy, utilization, and completeness.
 
+Interpret `$ARGUMENTS` as the scope (workspace, space, list, person, or time period as the sections below expect); when it is empty, ask or fall back to the configured workspace.
+
 ## Prerequisites
 
 - Workspace ID
@@ -78,6 +81,10 @@ Look for:
 clickup time running --workspace-id <id> --format json
 ```
 
+### Compile the report
+
+Copy the exact structure from `assets/report-template.md` in this skill's directory (`clickup skill path clickup-time-audit` prints it). Fill every placeholder; drop sections with no content.
+
 ## Tips
 
 - Duration is in milliseconds. Divide by 3600000 for hours.

package/skills/clickup-time-audit/assets/report-template.md

@@ -0,0 +1,19 @@
+## Time Audit: <scope> (<period>)
+
+Total logged: <n>h (<m>h billable / <k>h non-billable)
+
+### By person
+| Person | Hours | Billable | Entries |
+|--------|-------|----------|---------|
+| <name> | <n>h | <n>h | <n> |
+
+### Estimate accuracy (actual / estimated)
+- <task>: <actual>h vs <estimated>h (<ratio>)
+
+### Anomalies
+- <entry over 8h - forgot to stop timer?>
+- <entries with no description>
+- <running timers active for days>
+
+### Missing time
+- <tasks that changed status with zero time logged>

package/skills/clickup-timesheet-export/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: clickup-timesheet-export
+description: Exports ClickUp time entries for a period into a timesheet - CSV or markdown - with per-person and per-task totals and billable breakdowns. Use when the user asks for a timesheet, billable hours export, invoice backup, or wants hours summed for payroll or a client.
+license: MIT
+disable-model-invocation: true
+context: fork
+agent: general-purpose
+argument-hint: "[period and scope - e.g. 'last week', 'June for Sarah', 'this month billable only']"
+allowed-tools: Bash(clickup *), Bash(node *), Write, Read
+---
+
+# Timesheet Export
+
+Turn raw time entries into a clean timesheet with totals.
+
+## Understanding the Scope
+
+From `$ARGUMENTS` determine: the period (default: last 7 days), who (default: everyone), and whether to include only billable time. Resolve people via `clickup member list --format json`.
+
+## Workflow
+
+### Step 1: Pull time entries
+
+```bash
+clickup time list --workspace-id <id> \
+    --start <period-start> --end <period-end> \
+    [--assignee <user-id>] --format json
+```
+
+`--start`/`--end` accept ISO dates (`2026-06-01`), relative forms (`-30d`), or Unix timestamps. Entry durations are milliseconds.
+
+### Step 2: Aggregate deterministically
+
+Never sum hours yourself. Pipe the entries through the bundled script; the math comes out exact:
+
+```bash
+SKILL_DIR=$(clickup skill path clickup-timesheet-export)
+
+# JSON summary: totals, byPerson, byTask, flagged entries
+clickup time list --workspace-id <id> --start <start> --end <end> --format json \
+    | node "$SKILL_DIR/scripts/aggregate.mjs"
+
+# CSV rows for the export file
+clickup time list --workspace-id <id> --start <start> --end <end> --format json \
+    | node "$SKILL_DIR/scripts/aggregate.mjs" --csv
+```
+
+The summary's `flags` field lists running timers (excluded from totals), entries with no task, and entries over 12h.
+
+### Step 3: Write the export
+
+CSV for spreadsheets (default when the user says export/invoice):
+
+Copy the exact structure from `assets/report-template.md` in this skill's directory (`clickup skill path clickup-timesheet-export` prints it). Fill every placeholder; drop sections with no content.
+
+Save with the Write tool as `timesheet-<start>-<end>.csv` and tell the user the path. For a chat answer, use a markdown table plus totals instead.
+
+### Step 4: Summarize
+
+Use the summary block from the same template.
+
+## Tips
+
+- Cross-check suspicious days (over 12h per person) rather than silently exporting them.
+- For a recurring client invoice, filter to the client's space via the task IDs' locations.

package/skills/clickup-timesheet-export/assets/report-template.md

@@ -0,0 +1,9 @@
+date,person,task,description,hours,billable
+2026-06-30,Sarah,Login bug fix,Safari redirect,2.50,true
+
+<!-- Summary block to accompany the CSV: -->
+Timesheet <start> to <end>
+- Total: <n> hours (<m> billable / <k> non-billable)
+- By person: <name> <n>h, ...
+- Top tasks: <task> <n>h, ...
+Flagged: <entries with no task, running timers still open>

package/skills/clickup-timesheet-export/scripts/aggregate.mjs

@@ -0,0 +1,73 @@
+#!/usr/bin/env node
+// Deterministic timesheet aggregation. Pipe `clickup time list ... --format json`
+// into this script; totals come out exact so no arithmetic is done by the agent.
+//
+//   clickup time list --workspace-id X --start -7d --end today --format json \
+//     | node scripts/aggregate.mjs [--csv]
+//
+// Default output: JSON summary (totals, byPerson, byTask, flags).
+// --csv: timesheet rows (date,person,task,description,hours,billable) on stdout.
+
+import { readFileSync } from 'node:fs'
+
+const wantCsv = process.argv.includes('--csv')
+const raw = readFileSync(0, 'utf-8')
+let entries = JSON.parse(raw)
+if (!Array.isArray(entries)) entries = entries.data ?? [entries]
+
+const MS_PER_HOUR = 3_600_000
+const hours = (ms) => Math.round((ms / MS_PER_HOUR) * 100) / 100
+const rows = []
+const flags = { runningTimers: [], noTask: [], over12h: [] }
+const byPerson = {}
+const byTask = {}
+let totalMs = 0
+let billableMs = 0
+
+for (const e of entries) {
+  const duration = Number(e.duration)
+  const person = e.user_name || e.user?.username || 'unknown'
+  const task = e.task?.name || e.task_id || e.task?.id || ''
+  const desc = e.description || ''
+  const billable = e.billable === true || e.billable === 'true'
+
+  if (!e.end || duration < 0) {
+    flags.runningTimers.push({ id: e.id, person, task })
+    continue
+  }
+  if (!task) flags.noTask.push({ id: e.id, person, hours: hours(duration) })
+  if (duration > 12 * MS_PER_HOUR) flags.over12h.push({ id: e.id, person, task, hours: hours(duration) })
+
+  totalMs += duration
+  if (billable) billableMs += duration
+  byPerson[person] = (byPerson[person] ?? 0) + duration
+  byTask[task || '(no task)'] = (byTask[task || '(no task)'] ?? 0) + duration
+
+  const date = new Date(Number(e.start)).toISOString().slice(0, 10)
+  rows.push({ date, person, task, desc, hours: hours(duration), billable })
+}
+
+if (wantCsv) {
+  const esc = (v) => (/[",\n]/.test(String(v)) ? `"${String(v).replace(/"/g, '""')}"` : String(v))
+  process.stdout.write('date,person,task,description,hours,billable\n')
+  for (const r of rows.sort((a, b) => a.date.localeCompare(b.date) || a.person.localeCompare(b.person))) {
+    process.stdout.write([r.date, r.person, r.task, r.desc, r.hours.toFixed(2), r.billable].map(esc).join(',') + '\n')
+  }
+} else {
+  const toHours = (o) => Object.fromEntries(Object.entries(o).sort((a, b) => b[1] - a[1]).map(([k, v]) => [k, hours(v)]))
+  process.stdout.write(
+    JSON.stringify(
+      {
+        entries: rows.length,
+        totalHours: hours(totalMs),
+        billableHours: hours(billableMs),
+        nonBillableHours: hours(totalMs - billableMs),
+        byPerson: toHours(byPerson),
+        byTask: toHours(byTask),
+        flags,
+      },
+      null,
+      2,
+    ) + '\n',
+  )
+}

package/skills/clickup-users/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-users
 description: Manages ClickUp workspace users, groups, guests, roles, and members. Use when the user asks about team members, wants to invite users, manage groups, grant guest access, check permissions, resolve names to IDs, or see who is assigned to what.
+license: MIT
 allowed-tools: Bash(clickup user *), Bash(clickup group *), Bash(clickup guest *), Bash(clickup role *), Bash(clickup member *), Bash(clickup workspace members), Bash(clickup schema user*), Bash(clickup schema group*), Bash(clickup schema guest*), Bash(clickup schema member*)
 ---
 

package/skills/clickup-views/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-views
 description: Creates and manages ClickUp views including board, list, Gantt, calendar, and workload views. Use when the user asks about views, wants to create a kanban board, see tasks through a specific view, or configure view settings.
+license: MIT
 allowed-tools: Bash(clickup view *), Bash(clickup schema view*)
 ---
 

package/skills/clickup-webhooks/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: clickup-webhooks
 description: Registers and manages ClickUp webhooks for real-time event notifications. Use when the user asks about webhooks, wants to set up notifications for task changes, or needs to integrate ClickUp events with external services.
+license: MIT
 allowed-tools: Bash(clickup webhook *), Bash(clickup schema webhook*)
 ---
 

package/skills/clickup-weekly-review/SKILL.md

@@ -1,11 +1,12 @@
 ---
 name: clickup-weekly-review
 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.
+license: MIT
 disable-model-invocation: true
 context: fork
 agent: general-purpose
 argument-hint: "[scope - e.g. 'marketing team', space-id, or workspace-id]"
-allowed-tools: Bash(clickup *)
+allowed-tools: Bash(clickup *), Read
 ---
 
 # Weekly Review
@@ -81,6 +82,8 @@ clickup goal list --workspace-id <id> --format json
 
 ### Step 7: Compile the report
 
+Copy the exact structure from `assets/report-template.md` in this skill's directory (`clickup skill path clickup-weekly-review` prints it). Fill every placeholder; drop sections with no content.
+
 Summarize the data into a clear report with sections:
 - **Completed this week**: Count and highlights of finished tasks
 - **In progress**: Tasks actively being worked on

package/skills/clickup-weekly-review/assets/report-template.md

@@ -0,0 +1,26 @@
+# Weekly Review: <scope> (<week-start> to <week-end>)
+
+**Summary:** <2-3 sentences: overall trajectory, the one thing to know>
+
+## By the numbers
+| Metric | This week |
+|--------|-----------|
+| Completed | <n> |
+| In progress | <n> |
+| Overdue | <n> |
+| Hours logged | <n> |
+
+## Completed this week
+- <task name> (<assignee>)
+
+## In progress
+- <task name> - <assignee>, due <date>
+
+## Overdue / Blocked
+- <task name> - due <date>, <why it matters>
+
+## Goal progress
+- <goal>: <current>/<target> (<status>)
+
+## Next week
+- <what is due or planned>

package/skills/clickup-workspace-audit/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: clickup-workspace-audit
+description: Runs a hygiene audit over a ClickUp workspace or space finding unassigned tasks, missing due dates, stale in-progress work, overdue items, and overloaded assignees. Use when the user asks to audit, clean up, or health-check their workspace, or asks what is falling through the cracks.
+license: MIT
+disable-model-invocation: true
+context: fork
+agent: general-purpose
+argument-hint: "[scope - workspace, space name, or list name; optionally 'and fix']"
+allowed-tools: Bash(clickup *), Bash(node *), Read
+---
+
+# Workspace Audit
+
+Find hygiene problems across active tasks and report them with recommended fixes.
+
+## Understanding the Scope
+
+Interpret `$ARGUMENTS`: no scope means the whole workspace; a space or list name narrows the sweep (`--space-id` / `--list-id` filters on `task search`). If the user said "and fix" (or similar), offer to apply the recommended fixes after the report; never modify tasks without that instruction.
+
+## Workflow
+
+### Step 1: Pull the active task set
+
+```bash
+clickup task search --workspace-id <id> --format json
+```
+
+Server-side filters cannot express "no assignee" or "no due date", so fetch active tasks and inspect the JSON client-side. For large workspaces sweep one space at a time (`--space-id`).
+
+### Step 2: Classify deterministically
+
+Pipe the tasks through the bundled script so every task is bucketed by rule, not judgment:
+
+```bash
+SKILL_DIR=$(clickup skill path clickup-workspace-audit)
+clickup task search --workspace-id <id> --format json \
+    | node "$SKILL_DIR/scripts/classify.mjs" [--stale-days 14]
+```
+
+The output contains `activeTasks`, `flaggedTasks`, per-bucket lists, and per-person `load`. The buckets:
+
+| Check | Condition |
+|-------|-----------|
+| Unassigned | `assignees` is empty |
+| No due date | `due_date` is null |
+| Overdue | `due_date` in the past, status not closed |
+| Stale | status is in progress but `date_updated` older than 14 days |
+| Overloaded assignee | one person holds a disproportionate share of open tasks (flag the top offenders) |
+
+### Step 3: Check for blocked chains (optional, if dependencies are used)
+
+Tasks with `blocked` or `waiting` status whose blockers are themselves overdue deserve a callout.
+
+### Step 4: Report
+
+Copy the exact structure from `assets/report-template.md` in this skill's directory (`clickup skill path clickup-workspace-audit` prints it). Fill every placeholder; drop sections with no content.
+
+### Step 5: Apply fixes (only when asked)
+
+```bash
+clickup task update <id> --assignee-add <user-id>      # assign
+clickup task update <id> --due-date friday             # set due date
+clickup task update <id> --status "backlog"            # demote stale work honestly
+```
+
+Confirm the fix list with the user before running it; report each change as it lands.
+
+## Tips
+
+- `--include-closed` stays off: the audit is about active work.
+- Dates accept relative forms (`friday`, `+1w`) so fixes read naturally.
+- Re-run after fixes and show the before/after flagged counts.

package/skills/clickup-workspace-audit/assets/report-template.md

@@ -0,0 +1,21 @@
+## Workspace Audit: <scope> (<date>)
+
+Overall: <n> active tasks, <m> flagged (<x>%)
+
+### Overdue (worst first)
+- <task> - due <date>, assignee <name> (<id>)
+
+### Unassigned
+- <task> (<list>)
+
+### No due date
+- <task> (<list>)
+
+### Stale (in progress, untouched 14+ days)
+- <task> - last touched <date>
+
+### Load
+- <name>: <n> open tasks (team median: <m>)
+
+### Recommended fixes
+1. <specific action with the command to run>