magdramazz

Clickup Report Skill — Development skill for Claude Code

Development community

Claude Code skill: turn your ClickUp tickets into a meeting-ready sprint report (by sprint → status, with ticket summaries, risks and talking points).

How to install Clickup Report Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open magdramazz/clickup-report-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Clickup Report Skill does

Claude Code skill: turn your ClickUp tickets into a meeting-ready sprint report (by sprint → status, with ticket summaries, risks and talking points).

Alternatives in Development

Book To Skill — Turn any technical book PDF into a Claude Code skill — ready to study, reference, and use while you work 25.9k ★
/report — Generate a submission-ready bug bounty report 1.8k ★
Governance Review Agent — Chains adoption-report, drift detection scoped to at-risk teams, and stakeholder-brief into a periodic governa 194 ★

README

clickup-report — a Claude Code skill

Turn your ClickUp tickets into a **meeting-ready Markdown report** in one sentence:

make my clickup report for my meeting with my manager

Claude reads every ticket you are assigned in the **latest sprint**: the full description and the latest comments. It then writes a report organized **by sprint → by status**, with a short summary of each ticket, the risks, and talking points you can say out loud.

It works for any developer, whatever language or framework you use: the skill only talks to ClickUp.

What you get

# Sprint report — Jane Doe
Sprint: Sprint 12 (2026-03-02 → 2026-03-15) · Where: Web App / Sprints

## Executive summary          ← 3–5 bullets: outcomes, counts, biggest risk, what's next
## At a glance                ← counts per status + key metrics
   | Sprint    | to do | in progress | in review | done | Total |
   | Sprint 12 |   2   |      3      |     1     |  4   |  10   |
## Blocked / at risk          ← overdue, blocked, stale, QA send-backs, "can't test" comments
## Talking points             ← sentences you can say in the meeting
## Tasks by sprint / list
### Sprint 12 (10)
#### To do (2)
##### [Add CSV export to the orders page](https://app.clickup.com/t/…)
Status: to do · Priority: high · Due: 2026-03-12
Admins need to export filtered orders to CSV for the finance team. Work has not started;
the product owner confirmed the column list in a comment on 03-04.
#### In progress (3)
…
#### In review (1)
…
#### Done (4)
…
## Data notes                 ← anything the data could not show (e.g. no time tracking)

Statuses use **your workspace's own names and order** ("ready for qa", "in review", "blocked" and so on).

Features

First-run setup: Claude asks for your ClickUp user id, workspace id and API token. It checks them against the ClickUp API and saves them. If you don't know your user id, it looks it up from the token and asks you to confirm.
Latest sprint by date: i