Personal Task Tracking

Query and manage ClickUp via REST API and the local `scripts/query.sh` helper. Use when listing open or completed tasks, counting due work, looking up spaces...

Security Scan

The skill's code, required binaries, and environment variables are consistent with its stated ClickUp task-management purpose — nothing in the files indicates unrelated or hidden behavior.

Purpose & Capability

Name/description (ClickUp task querying/manipulation) align with the required binaries (bash, curl, jq), the declared env vars (CLICKUP_API_KEY, CLICKUP_TEAM_ID, CLICKUP_ASSIGNEE_ID), and the included helper script which calls ClickUp's API.

Instruction Scope

SKILL.md and scripts only call ClickUp's API endpoints and reference the three declared env vars. The README suggests echoing env values to verify them (echo $CLICKUP_API_KEY) — which is a user-operated action that can expose secrets in shell history or terminal output; recommend avoiding echoing secrets. The instructions do not read other system files nor contact unexpected remote endpoints.

Install Mechanism

Install spec is a single brew formula to install jq, a standard, known package manager and package. No arbitrary downloads or extracted archives are present.

Credentials

The three required env vars map directly to ClickUp usage: API token, team id, and assignee id. The declared primary credential is the ClickUp API key. There are no unrelated credentials requested.

Persistence & Privilege

The skill does not request always:true, does not modify other skills or system-wide settings, and has no install steps that persist beyond installing jq. It runs as an invoked helper script and requires explicit invocation.

Assessment

This skill appears coherent for ClickUp task management, but you should only provide a ClickUp API token with the minimum necessary scope. Avoid echoing the API key (the SKILL.md suggests echoing it) because that may expose it in terminal history — instead set env vars securely (for example via a shell profile read step or a secrets manager). Review and run the script in a controlled environment if you have sensitive data in ClickUp, since the helper fetches all tasks and could return large amounts of private data. If you install, consider using a short-lived or scoped token you can revoke if needed, and verify network traffic or token usage in your ClickUp account after first use.

ClickUp Skill

Interact with ClickUp's REST API for task management, reporting, and workflow automation.

Configuration

Before using this skill, ensure the following are configured:

• API Token: CLICKUP_API_KEY
• Team/Workspace ID: CLICKUP_TEAM_ID
• Task Assignee ID: CLICKUP_ASSIGNEE_ID

Check if they are available as environment variables:

echo $CLICKUP_API_KEY
echo $CLICKUP_TEAM_ID
echo $CLICKUP_ASSIGNEE_ID

If not available, export them as environment variables.

export CLICKUP_API_KEY={value}
export CLICKUP_TEAM_ID={value}
export CLICKUP_ASSIGNEE_ID={value}

Quick Start

Using the Helper Script

The fastest way to query ClickUp:

# Set environment variables
export CLICKUP_API_KEY="pk_..."
export CLICKUP_TEAM_ID="..."
export CLICKUP_ASSIGNEE_ID="..."

# Get open tasks due or overdue by a given end time
./scripts/clickup-query.sh tasks --end "2026-03-28 17:00"

# Get task counts for open tasks due or overdue by a given end time
./scripts/clickup-query.sh task-count --end "2026-03-28 17:00"

# Get tasks completed during a time window
./scripts/clickup-query.sh completed-tasks --start "2026-03-24" --end "2026-03-28 17:00"

# Get spaces under the team 
./scripts/clickup-query.sh spaces

# Get lists under a space_id
./scripts/clickup-query.sh lists 123456

# Create a task with given title and due date, assign to CLICKUP_ASSIGNEE_ID, under a list_id 
./scripts/clickup-query.sh create-task {list_id} "Follow up with customer" "2026-03-28 17:00"

# Close a task with task_id 
./scripts/clickup-query.sh close-task 86e0jmdfe

Direct API Calls

For custom queries or operations not covered by the helper script. Example:

# Get all open tasks (with subtasks and pagination)
curl "https://api.clickup.com/api/v2/team/{team_id}/task?include_closed=false&subtasks=true" \
  -H "Authorization: {api_key}"

Common Operations

Get open tasks due or overdue by a given end time

# Using helper script 
./scripts/clickup-query.sh tasks --end "2026-03-28 17:00"

Get Task Counts due or overdue by a given end time

# Using helper script 
./scripts/clickup-query.sh task-count --end "2026-03-28 17:00"

Create a Task with given title and due date

step 1. Get all list

# Using helper script 
./scripts/clickup-query.sh spaces
./scripts/clickup-query.sh lists {space_id}

Step 2: Choose a list that's most relevant to the task Step 3: Create the task

# Using helper script 
./scripts/clickup-query.sh create-task {list_id} "Follow up with customer" "2026-03-28 17:00"

Close a Task

# Using helper script 
./scripts/clickup-query.sh close-task {task_id}