clickup skillsDOCS

The workflow your agent follows.#

This reference is generated from the actual skill files and MCP tool definitions at build time. Tool names and required inputs are not maintained in a separate hand-written list.

Shared skills#

| Skill | What it guides |

| --- | --- |

| clickup-bind-project | Bind a Git repository, project objective, ClickUp workspace/list, and one or more root tasks. Use for project setup, switching projects, linking a repository to ClickUp, or choosing the task all later agent work should use. |

| clickup-github | Link ClickUp tasks and subtasks with GitHub repos, issues, PRs, comments, checks, and completion evidence through CLI or MCP. Use to create missing issue targets, synchronize discussions, link implementation PRs, configure native integration, or coordinate work across both systems. |

| clickup-handoff | Resume a bound ClickUp project, review operation receipts, reconcile uncertain updates, and prepare a concise task handoff. Use at session start/end, after a failed update, or when handing work to a teammate or another coding agent. |

| clickup-route | Choose an efficient available CLI or free MCP for a ClickUp/GitHub operation. Use whenever a bound project needs ClickUp tools, a backend lacks a capability, a rate limit occurs, or a choice among cup, community MCP, official ClickUp MCP, gh, and GitHub MCP is needed. |

| clickup-setup | Install, configure, verify, or update ClickUp Skills in an agent environment. Use when a teammate asks to install ClickUp Skills, finish Vercel skills CLI installation, set up Python/Krodak CLI/MCP, or resolve installation conflicts. |

| clickup-work-task | Implement work tied to an active ClickUp task, create scoped subtasks, record meaningful progress, and keep a project objective attached to coding or research work. Use when asked to work on a ClickUp ticket or when a repository contains a ClickUp project binding. |

Scoped workflow tools#

All tools require an absolute project_dir pointing to the working Git worktree. Optional task IDs use local focus where supported; agents should pass explicit IDs for parallel work. The local helper checks scope and keeps receipts. Host MCP calls enforce the same rules through the skills, outside that journal.

project_context#

Read the binding and active task; does not verify remote scope.

Required: project_dir.

Input schema for agents
{
  "type": "object",
  "properties": {
    "project_dir": {
      "type": "string",
      "description": "Absolute path to the target Git worktree"
    }
  },
  "required": [
    "project_dir"
  ],
  "additionalProperties": false
}

route_operation#

Choose among backends actually available to the host; does not execute a tool.

Required: project_dir, operation, available.

Input schema for agents
{
  "type": "object",
  "properties": {
    "project_dir": {
      "type": "string",
      "description": "Absolute path to the target Git worktree"
    },
    "operation": {
      "type": "string",
      "enum": [
        "task.get",
        "task.context",
        "task.subtask",
        "task.comment",
        "task.status",
        "task.search",
        "task.custom-field",
        "task.dependency",
        "docs.search",
        "chat.send",
        "github.pr",
        "github.issue",
        "github.comment",
        "github.checks"
      ]
    },
    "available": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "project_dir",
    "operation",
    "available"
  ],
  "additionalProperties": false
}

get_bound_task#

Fetch and verify a task belongs to the bound workspace, list, and roots.

Required: project_dir.

Input schema for agents
{
  "type": "object",
  "properties": {
    "project_dir": {
      "type": "string",
      "description": "Absolute path to the target Git worktree"
    },
    "task_id": {
      "type": "string"
    }
  },
  "required": [
    "project_dir"
  ],
  "additionalProperties": false
}

create_bound_subtask#

Create a GitHub-associated subtask. Default creates/reuses an issue first. Requires gh.

Required: project_dir, key, title, description.

Input schema for agents
{
  "type": "object",
  "properties": {
    "project_dir": {
      "type": "string",
      "description": "Absolute path to the target Git worktree"
    },
    "task_id": {
      "type": "string"
    },
    "key": {
      "type": "string"
    },
    "title": {
      "type": "string"
    },
    "description": {
      "type": "string"
    },
    "github_target": {
      "type": "string"
    }
  },
  "required": [
    "project_dir",
    "key",
    "title",
    "description"
  ],
  "additionalProperties": false
}

record_progress#

Post linked progress and mirror to associated issues/PRs with resumable receipts.

Required: project_dir, key, text.

Input schema for agents
{
  "type": "object",
  "properties": {
    "project_dir": {
      "type": "string",
      "description": "Absolute path to the target Git worktree"
    },
    "task_id": {
      "type": "string"
    },
    "key": {
      "type": "string"
    },
    "text": {
      "type": "string"
    }
  },
  "required": [
    "project_dir",
    "key",
    "text"
  ],
  "additionalProperties": false
}

Preserve PR content and link both systems. Requires gh; no status changes.

Required: project_dir, key, pr_number.

Input schema for agents
{
  "type": "object",
  "properties": {
    "project_dir": {
      "type": "string",
      "description": "Absolute path to the target Git worktree"
    },
    "task_id": {
      "type": "string"
    },
    "key": {
      "type": "string"
    },
    "pr_number": {
      "type": "integer",
      "minimum": 1
    }
  },
  "required": [
    "project_dir",
    "key",
    "pr_number"
  ],
  "additionalProperties": false
}

Link a bound repo/issue/PR or create/reuse new-issue. Requires gh; preserves body text.

Required: project_dir, key, target.

Input schema for agents
{
  "type": "object",
  "properties": {
    "project_dir": {
      "type": "string",
      "description": "Absolute path to the target Git worktree"
    },
    "task_id": {
      "type": "string"
    },
    "key": {
      "type": "string"
    },
    "target": {
      "type": "string"
    },
    "title": {
      "type": "string"
    },
    "description": {
      "type": "string"
    }
  },
  "required": [
    "project_dir",
    "key",
    "target"
  ],
  "additionalProperties": false
}

sync_task_comments#

Reconcile top-level ClickUp comments and GitHub issue/PR discussions; no background worker.

Required: project_dir.

Input schema for agents
{
  "type": "object",
  "properties": {
    "project_dir": {
      "type": "string",
      "description": "Absolute path to the target Git worktree"
    },
    "task_id": {
      "type": "string"
    },
    "direction": {
      "type": "string",
      "enum": [
        "both",
        "to-clickup",
        "to-github"
      ]
    }
  },
  "required": [
    "project_dir"
  ],
  "additionalProperties": false
}

set_task_phase#

Set a mapped status. Done requires a merged PR, successful CI, and verification text.

Required: project_dir, key, phase.

Input schema for agents
{
  "type": "object",
  "properties": {
    "project_dir": {
      "type": "string",
      "description": "Absolute path to the target Git worktree"
    },
    "task_id": {
      "type": "string"
    },
    "key": {
      "type": "string"
    },
    "phase": {
      "type": "string",
      "enum": [
        "in_progress",
        "review",
        "done"
      ]
    },
    "pr_number": {
      "type": "integer",
      "minimum": 1
    },
    "verification": {
      "type": "string"
    }
  },
  "required": [
    "project_dir",
    "key",
    "phase"
  ],
  "additionalProperties": false
}

Search by task, client, tool or setup step.