Agent skill · data analytics · jeremylongshore
clickup-common-errors
Analyze and diagnose ClickUp authentication, authorization, plan, request, pagination, throttling, webhook, and provider failures from redacted evidence. Use when a ClickUp integration fails or behaves inconsistently. Trigger with "ClickUp error", "ClickUp 429", or "diagnose ClickUp API".
Why this skill is useful
Provides specific diagnostic scripts and error handling patterns for ClickUp API v2 that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq 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 Error Diagnosis Overview Classify the failure before changing code so authentication, workspace scope, plan gates, schema drift, and transient provider faults receive different remedies. Prerequisites A redacted status code, ClickUp error code/message, endpoint version, and request shape The authorized Workspace ID, auth mode, and current plan facts from an owner Access to current ClickUp docs and status information 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 OAUTH017 can indicate a missing Authorization header; workspace authorization and revoked-token families have distinct codes. Browser-side CORS failures require a server-side boundary, not a permissive token-bearing frontend workaround. A 429 is per token; inspect X-RateLimit-Limit, X-RateLimit-Remaining, and Unix X-RateLimit-Reset. Retry only bounded transient failures; do not retry malformed requests or permission denials. 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. Capture the method, versioned path, status, ClickUp error code, response type, and sanitized headers. 2. Confirm whether the caller uses a personal token or OAuth and whether the Workspace was authorized. 3. Validate path parameters, JSON content type, endpoint version, pagination cursor/page, and plan eligibility. 4. Separate 401/403, 404, 409-style state conflicts, 429, timeout, and 5xx classes. 5. Reproduce with the smallest read-only request and compare against the official reference. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-common-errors