Agent skill · software engineering · jeremylongshore
clickup-multi-env-setup
Separate ClickUp development, staging, and production identities, Workspaces, callbacks, queues, and data with fail-closed guards. Use when one integration spans multiple environments. Trigger with "ClickUp environments", "ClickUp staging setup", or "ClickUp tenant isolation".
Why this skill is useful
Provides specific configuration patterns and environment management for ClickUp API that the AI wouldn't reliably generate on its own.
What it needs
Requires aws, gcloud, vault 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 Multi-Environment Isolation Overview Prevent a development process or callback from crossing into production merely because a shared token can access multiple Workspaces. Prerequisites An environment matrix of OAuth apps or personal tokens, allowed Workspace IDs, callback URLs, queues, and secret references Separate non-production data and synthetic verification records Deployment and incident owners for every environment 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 OAuth users can authorize one or more Workspaces, so the application must enforce its own environment allow-list. Redirect URIs and webhook endpoints are environment-specific and HTTPS. Rate limits are per token; sharing a token also shares its budget and blast radius. v2 team IDs and v3 Workspace IDs must resolve to the same intended environment boundary. 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 every environment's credentials, app IDs, redirects, webhooks, queues, storage, and Workspace IDs. 2. Remove shared credentials and assign an accountable owner and rotation path to each secret. 3. Implement startup and per-request guards that compare environment and Workspace allow-lists. 4. Namespace reconciliation keys, queues, metrics, and callback secrets by environment. 5. Run offline cross-environment denial tests and bounded live identity/Workspace probes. 6. Publish the matrix and fail deployment if any production boundary is ambiguous. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-multi-env-setup