← ClaudeAtlas

clickup-browserlisted

Drives the parts of ClickUp the public API does not reach: workspace task templates, Task-created automations, dashboards, space statuses, Workload capacity and a view's pinned description. Use when a ClickUp job has no API, when templates or automations must be created or changed, or when the cu CLI has no command for what is asked. Everything else belongs to clickup-cli, clickup-ops or clickup-data-manager.
heyramzi/ai-agency · ★ 0 · AI & Automation · score 75
Install: claude install-skill heyramzi/ai-agency
# ClickUp in the browser ClickUp's PUBLIC API covers tasks, lists, fields, docs and views and nothing else. Templates, automations, agents, dashboards, statuses and Workload have no public endpoint, and that is what this skill is for. It no longer means clicking: most of them are now `cu` commands built on the private frontdoor API, and the rest can be recorded and replayed. Reach for a click path last, because it breaks on a redesign and an API call does not. Announce at start: "I'm using the clickup-browser skill." ## Check the CLI before you open a browser Nine surfaces the public API never reached are now plain `cu` commands, built on ClickUp's private frontdoor API (list/get automations re-verified 1 Sep 2026): cu template center # every saved template, by kind cu dashboards # every dashboard in the workspace cu statuses # every status defined anywhere cu agents # every Super Agent cu agents get <id> # one agent, agent_config included cu automations --list|--folder|--space <id> # rules on that level (--active ACTIVE|INACTIVE|ALL) cu automations get <uuid> # one rule in full, every action's input included cu automations count <listId> cu automations catalog # everything automations can trigger on and do A space-level rule is invisible in the list-level listing, and no endpoint writes an action: `PUT /automation/workflow/{uuid}` returns 200 and