clickup-performance-tuning
Optimize ClickUp API v2 performance with caching, pagination, connection pooling, and request batching patterns. "clickup caching", "clickup slow", "clickup batch requests", "clickup pagination". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-performance-tuning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ClickUp Performance Tuning ## Overview Optimize ClickUp API v2 throughput and latency. Key strategies: cache hierarchy data, paginate efficiently, pool connections, and batch where possible. ## Baseline Latency (ClickUp API v2) | Endpoint | Typical P50 | Typical P95 | |----------|-------------|-------------| | `GET /user` | 80ms | 200ms | | `GET /team` | 100ms | 300ms | | `GET /list/{id}/task` |
What does the clickup-performance-tuning skill do?
Optimize ClickUp API v2 performance with caching, pagination, connection pooling, and request batching patterns. "clickup caching", "clickup slow", "clickup batch requests", "clickup pagination". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-performance-tuning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.