clickup-upgrade-migration
Migrate between ClickUp API versions (v2 to v3) and handle breaking changes. Use when upgrading API versions, adapting to endpoint changes, or migrating between ClickUp plan tiers. "clickup API migration", "clickup deprecation". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-upgrade-migration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ClickUp Upgrade & Migration ## Overview Guide for migrating between ClickUp API versions. API v2 is the current stable version (`/api/v2/`). API v3 endpoints are gradually being introduced with terminology and structural changes. ## Key v2 vs v3 Terminology Changes | Concept | API v2 Term | API v3 Term | |---------|-------------|-------------| | Workspace | Team (`team_id`) | Workspace (`workspa
What does the clickup-upgrade-migration skill do?
Migrate between ClickUp API versions (v2 to v3) and handle breaking changes. Use when upgrading API versions, adapting to endpoint changes, or migrating between ClickUp plan tiers. "clickup API migration", "clickup deprecation". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-upgrade-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
