AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Project Clickup

skill-swapnildahiphale-opensre-project-clickup · by swapnildahiphale

ClickUp project management integration for incident tracking and task management

No reviews yet
0 installs
41 views
0.0% view→install

Install

$ agentstack add skill-swapnildahiphale-opensre-project-clickup

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access Used
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-swapnildahiphale-opensre-project-clickup)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Project Clickup? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

ClickUp Project Management

Query and manage tasks in ClickUp for incident tracking and project management.

Authentication

This skill uses credentials managed by the credential-proxy service. In production, credentials are injected automatically via JWT authentication.

For local development, set:

  • CLICKUP_API_TOKEN - Your ClickUp API token (Personal Access Token)
  • CLICKUP_TEAM_ID - Your workspace/team ID (optional, auto-detected if not set)

Available Scripts

list_spaces.py - Discover Workspace Structure

List all spaces, folders, and lists in the workspace:

# List spaces
python list_spaces.py

# Include lists and folders
python list_spaces.py --include-lists

# JSON output
python list_spaces.py --json

search_tasks.py - Search for Tasks

Search across all tasks in the workspace:

# Search by query
python search_tasks.py --query "payment error"

# Filter by status
python search_tasks.py --query "incident" --status "investigating"

# Recently updated
python search_tasks.py --updated-since 24h

# Combined filters
python search_tasks.py --query "api" --status "open" --updated-since 7d --json

Options:

  • --query, -q - Search text (matches name and description)
  • --status, -s - Filter by status (can repeat for multiple)
  • --assignee, -a - Filter by assignee ID
  • --list-id - Filter by list ID
  • --space-id - Filter by space ID
  • --updated-since - Tasks updated since (e.g., "1h", "24h", "7d")
  • --created-since - Tasks created since
  • --include-closed - Include closed tasks
  • --limit - Maximum results (default: 50)
  • --json - Output as JSON

get_task.py - Get Task Details

Retrieve full details for a specific task:

# Basic details
python get_task.py abc123

# Include comments
python get_task.py abc123 --include-comments

# Include subtasks
python get_task.py abc123 --include-subtasks

# Full details as JSON
python get_task.py abc123 --include-comments --include-subtasks --json

Options:

  • --include-comments, -c - Include task comments
  • --include-subtasks, -s - Include subtasks
  • --json - Output as JSON

add_comment.py - Add Task Comment

Add investigation findings to a task:

# Simple comment
python add_comment.py abc123 --message "Found root cause in logs"

# Markdown comment
python add_comment.py abc123 -m "## Investigation Summary\n- Error in payment service\n- Caused by config change"

Options:

  • --message, -m - Comment text (supports markdown)
  • --json - Output as JSON

ClickUp Hierarchy

Understanding ClickUp's structure helps with navigation:

Workspace (Team)
└── Space
    ├── Folder (optional)
    │   └── List
    │       └── Task
    │           └── Subtask
    └── List (folderless)
        └── Task

Investigation Workflow

1. Discover Structure

First, find where incidents are tracked:

python list_spaces.py --include-lists

Look for spaces/lists like "Incidents", "SRE", "On-Call", etc.

2. Search for Related Incidents

Search for incidents related to your investigation:

python search_tasks.py --query "payment" --status "investigating"

3. Get Incident Details

Review the full incident context:

python get_task.py abc123 --include-comments

4. Document Findings

Add your investigation findings:

python add_comment.py abc123 --message "Root cause: Database connection pool exhausted"

Task Properties

Status

Tasks have configurable statuses. Common incident statuses:

  • to do / open - New incident
  • investigating - Active investigation
  • in progress - Remediation underway
  • resolved / complete - Incident resolved
  • closed - Post-mortem complete

Priority

  • 1 = Urgent
  • 2 = High
  • 3 = Normal
  • 4 = Low

Custom Fields

Teams often use custom fields for:

  • Severity (P0, P1, P2, etc.)
  • Affected services
  • Impact scope
  • Customer impact
  • Root cause category

Integration with Other Skills

ClickUp integrates with the investigation workflow:

  1. Start: Check ClickUp for existing incident tickets
  2. Investigate: Use observability skills to find root cause
  3. Document: Add findings to ClickUp task as comments
  4. Correlate: Link with git log and curl $GITHUBBASEURL for change analysis

Tips

  • Use task IDs - Copy task IDs from ClickUp URLs (format: abc123)
  • Search broadly first - Start with general queries, then filter
  • Check comments - Previous investigation notes may have clues
  • Document as you go - Add comments with findings for team visibility

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.