clickup-multi-env-setup
Configure ClickUp API access across dev, staging, and production environments with per-environment tokens and workspace isolation. "clickup environment setup", "clickup config by env", "clickup multi-env". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-multi-env-setup --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 Multi-Environment Setup ## Overview Configure separate ClickUp workspaces and API tokens for development, staging, and production. ClickUp does not have sandbox environments, so the recommended approach is separate workspaces with separate tokens per environment. ## Environment Strategy | Environment | Workspace | Token | Rate Limit | Purpose | |-------------|-----------|-------|--------
What does the clickup-multi-env-setup skill do?
Configure ClickUp API access across dev, staging, and production environments with per-environment tokens and workspace isolation. "clickup environment setup", "clickup config by env", "clickup multi-env". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-multi-env-setup --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.