Agent skill · software engineering · jeremylongshore
clickup-sdk-patterns
Build a typed ClickUp client from official OpenAPI contracts with explicit version routing, auth injection, error typing, pagination, and retry policy. Use when creating a reusable ClickUp adapter. Trigger with "ClickUp SDK", "ClickUp client wrapper", or "typed ClickUp API".
Why this skill is useful
Adds a complete TypeScript client wrapper for the ClickUp API with error handling and multi-tenant support, which the AI cannot generate on its own.
What it needs
Requires typescript 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 Typed Client Patterns Overview Keep application code independent of transport details without presenting an ungoverned third-party wrapper as an official SDK. Prerequisites Pinned official v2 and v3 OpenAPI documents or reviewed endpoint schemas A server-side HTTP runtime, validation library, and test framework Auth, Workspace, timeout, retry, redaction, and observability policies 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 ClickUp publishes v2 and v3 OpenAPI specifications suitable for generation. Route every operation to an explicit version/base path and preserve ClickUp field types, including nullable webhook fields. Inject personal or OAuth tokens at call time and never store them in client objects serialized to logs. Retry only idempotent transient operations by default; writes need durable application idempotency. 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. Inventory required operations and pin the matching official schema/version digest. 2. Generate or hand-write a narrow transport and wrap it behind domain-oriented interfaces. 3. Inject auth, Workspace allow-list, timeouts, content type, and redacted telemetry centrally. 4. Create endpoint-specific pagination helpers instead of one incorrect universal iterator. 5. Map statuses/error codes into typed retryable, authorization, plan, validation, and unknown classes. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-sdk-patterns