Agent skill · marketing growth · jeremylongshore
clickup-cost-tuning
Reduce ClickUp integration cost and request load using measured traffic, pagination, cache policy, webhooks, and current plan facts. Use when forecasting or optimizing ClickUp operations. Trigger with "ClickUp cost", "reduce ClickUp requests", or "ClickUp plan sizing".
Why this skill is useful
Provides specific strategies and code snippets for optimizing ClickUp API usage that the AI wouldn't reliably generate on its own.
What it needs
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 Integration Cost and Request Tuning Overview Optimize from observed request and feature usage without inventing prices or treating a plan upgrade as the default remedy. Prerequisites Per-endpoint request counts, latency, 429s, page depth, polling intervals, and cache hit rates Current Workspace plan and feature-use facts supplied by an authorized owner Freshness objectives and an approved data-retention policy 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 Rate limits are per token and currently vary by Workspace plan. Get Tasks returns at most 100 tasks per page; wasteful full scans multiply requests. Webhook delivery can replace polling but requires secure, durable event processing. Some features and parameters are plan-gated; current commercial price must come from the account owner. 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 requests by endpoint, token boundary, caller, result size, and business operation. 2. Identify duplicate reads, empty pages, overbroad polling, retry storms, and unnecessary writes. 3. Model pagination, conditional caching, webhook invalidation, and schedule consolidation. 4. Quantify custom-field uses and plan-gated operations separately from API request volume. 5. Compare alternatives against freshness, failure recovery, security, and owner-provided commercial facts. 6. Implement one bounded change and verify request, latency, error, and staleness deltas. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-cost-tuning