Agent skill · software engineering · jeremylongshore
clickup-performance-tuning
Analyze and improve ClickUp throughput and freshness with endpoint-aware pagination, bounded concurrency, caching, and webhook invalidation. Use when ClickUp syncs are slow or rate constrained. Trigger with "ClickUp performance", "speed up ClickUp sync", or "ClickUp pagination".
Why this skill is useful
Adds executable scripts for optimizing ClickUp API performance through caching, pagination, and connection pooling that aren't in public docs.
What it needs
Requires lru-cache, node:https, p-queue installed locally. Requires clickup account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
ClickUp Throughput and Freshness Tuning Overview Tune measured bottlenecks while preserving completeness, ordering, freshness, and rate safety. Reject optimizations that improve speed by dropping provider records. Prerequisites A baseline of request volume, p50/p95 latency, page counts, payload sizes, 429s, queue age, and reconciliation Completeness and freshness assertions plus synthetic load fixtures Known endpoint-specific pagination and current token limit Tool Discipline Use Read, Glob, and Grep to inspect the repository, adapters, configuration names, tests, and evidence. Use WebFetch only for current official ClickUp documentation. Use Write or Edit after confirming the target file, Workspace boundary, and requested mode. Current Contract Get Tasks returns 100 tasks per zero-based page and has explicit filters for closed tasks and subtasks; use includetiml for Tasks in Multiple Lists. Task comments use start plus startid after the first 25 newest comments. The v2 task surface does not offer a general fields-selection parameter; do not invent one. Webhook invalidation can reduce polling, but delivery must be signed, idempotent, and reconciled. Authentication Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in Authorization, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret. Instructions 1. Measure each endpoint and business operation before changing caching or concurrency. 2. Verify pagination termination, ordering, filters, and reconciliation on boundary fixtures. 3. Coalesce duplicate reads and cache stable hierarchy metadata with explicit invalidation. 4. Set concurrency from the token's current remaining/reset headers and downstream queue capacity. 5. Use webhooks to invalidate or enqueue targeted reads while retaining a reconciliation sweep. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-performance-tuning