Agent skill · software engineering · jeremylongshore
clickup-upgrade-migration
Migrate ClickUp endpoints, schemas, clients, and terminology with version inventory, dual contracts, canaries, and rollback. Use when adopting selected API v3 surfaces or provider changes. Trigger with "upgrade ClickUp API", "ClickUp v3 migration", or "ClickUp schema change".
Why this skill is useful
Adds executable scripts and a migration strategy for adapting ClickUp API calls between versions, which the AI wouldn't generate on its own.
What it needs
Requires bash 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 API Evolution Migration Overview Evolve endpoint-by-endpoint because ClickUp v2 remains the primary surface while selected capabilities use v3. Never infer a platform-wide cutover from one migrated endpoint. Prerequisites An inventory of every endpoint, version, field assumption, pagination loop, and webhook dependency Pinned current/target OpenAPI schemas and representative sanitized fixtures Feature flags, canary environment, reconciliation, and rollback ownership 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 There is no general v2-to-v3 cutover contract; preserve explicit version routing for unchanged v2 operations. v2 uses Team for Workspace while v3 uses Workspace; Groups remain user groups. Different endpoints can have different pagination and response types, so a base-path swap is unsafe. Preview or experimental surfaces require tighter pins and rollback. 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 current operations and label each v2, v3, deprecated, preview, or unknown. 2. Diff official schemas and docs for path, auth, plan, parameter, field, pagination, and error changes. 3. Update typed adapters behind a feature flag while preserving the current path. 4. Run offline dual-contract fixtures and migration tests, including nulls and partial failures. 5. Canary read-only traffic, then separately approved synthetic writes, and compare normalized results. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-upgrade-migration