clickup-core-workflow-a
Manage ClickUp tasks via API v2: create, read, update, delete tasks with assignees, priorities, due dates, subtasks, and statuses. "manage clickup tasks", "clickup CRUD", "clickup task management". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-core-workflow-a --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 Core Workflow A — Task Management ## Overview CRUD operations on ClickUp tasks via API v2. Tasks live in Lists and support assignees, priorities (1-4), statuses, due dates, tags, checklists, and custom fields. ## Endpoints | Operation | Method | Endpoint | |-----------|--------|----------| | Create task | POST | `/api/v2/list/{list_id}/task` | | Get task | GET | `/api/v2/task/{task_id}`
What does the clickup-core-workflow-a skill do?
Manage ClickUp tasks via API v2: create, read, update, delete tasks with assignees, priorities, due dates, subtasks, and statuses. "manage clickup tasks", "clickup CRUD", "clickup task management". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-core-workflow-a --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.