// ClickUp project management integration for incident tracking and task management
| name | project-clickup |
| description | ClickUp project management integration for incident tracking and task management |
| allowed-tools | ["Bash(python *)"] |
Query and manage tasks in ClickUp for incident tracking and project management.
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)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 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 JSONRetrieve 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 JSONAdd 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 JSONUnderstanding ClickUp's structure helps with navigation:
Workspace (Team)
└── Space
├── Folder (optional)
│ └── List
│ └── Task
│ └── Subtask
└── List (folderless)
└── Task
First, find where incidents are tracked:
python list_spaces.py --include-lists
Look for spaces/lists like "Incidents", "SRE", "On-Call", etc.
Search for incidents related to your investigation:
python search_tasks.py --query "payment" --status "investigating"
Review the full incident context:
python get_task.py abc123 --include-comments
Add your investigation findings:
python add_comment.py abc123 --message "Root cause: Database connection pool exhausted"
Tasks have configurable statuses. Common incident statuses:
to do / open - New incidentinvestigating - Active investigationin progress - Remediation underwayresolved / complete - Incident resolvedclosed - Post-mortem completeTeams often use custom fields for:
ClickUp integrates with the investigation workflow:
abc123)Kubernetes debugging methodology and scripts. Use for pod crashes, CrashLoopBackOff, OOMKilled, deployment issues, resource problems, or container failures.
GitLab project management, CI/CD pipelines, merge requests, and code review. Use when investigating GitLab projects, pipeline failures, merge requests, commits, or issues.
Slack integration for incident communication. Use when searching for context in incident channels, posting status updates, or finding discussions about issues.
AWS cloud infrastructure inspection. Use when investigating EC2 instances, ECS tasks/services, Lambda functions, CloudWatch logs/metrics, or AWS resource issues.
Infrastructure debugging for Kubernetes and AWS. Use when investigating pod crashes, deployment issues, resource problems, container failures, or cloud infrastructure issues.
Safe remediation actions for Kubernetes. Use when proposing or executing pod restarts, deployment scaling, or rollbacks. Always use dry-run first.