Agent skill · software engineering · jeremylongshore
clickup-core-workflow-b
Analyze, inventory, and change ClickUp Spaces, Folders, Lists, tags, and views with parent-aware plans and reversible boundaries. Use when managing ClickUp hierarchy through API v2. Trigger with "ClickUp hierarchy", "ClickUp Lists", or "ClickUp views".
Why this skill is useful
Adds executable scripts for managing ClickUp workspaces, spaces, folders, and lists via API that aren't in public docs.
What it needs
Requires curl 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 Hierarchy and Views Overview Manage structural objects only after resolving their actual parent chain and downstream task impact. Keep discovery, planning, and mutation as separately reviewable phases. Prerequisites An allow-listed Workspace and authorized hierarchy administrator A current inventory of Spaces, optional Folders, Lists, tags, views, and referenced tasks A reviewed desired-state plan and rollback or recreation evidence 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 In v2, teamid is a Workspace ID; user groups are separate group resources. Lists may be folderless under a Space or nested under a Folder, so the parent endpoint matters. Views can exist at Workspace, Space, Folder, or List scope; use the matching endpoint. Hierarchy deletion can orphan assumptions in integrations even when the API accepts it. 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 Workspace, Space, Folder, List, tag, and view IDs with parent relationships. 2. Map every desired change to its exact v2 endpoint and current object version. 3. Check task counts, automations, webhooks, views, and external references affected by the change. 4. Produce a create/update/delete plan with dependency order and rollback evidence. 5. Apply creates before dependent updates; isolate destructive actions behind approval. 6. Re-read the hierarchy and verify names, parents, privacy, views, and downstream references. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-core-workflow-b