---
name: clickup-data-handling
description: >-
  Analyze, map, minimize, redact, retain, export, and delete ClickUp-derived work data under an application-owned governance policy. Use when ClickUp tasks, comments, attachments, or member data enter another system. Trigger with "ClickUp data handling", "ClickUp PII", or "ClickUp retention".
argument-hint: "[data-flow-or-repository] [assessment|remediation]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - saas
  - clickup
  - data-governance
model: inherit
effort: high
compatibility: Designed for Claude Code; legal retention and data-subject decisions require authorized owners
title: clickup-data-handling
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/clickup-data-handling
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/clickup-data-handling/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/clickup-data-handling`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/clickup-data-handling`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/clickup-data-handling) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/clickup-data-handling`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/clickup-data-handling --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/clickup-data-handling --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# ClickUp Work-Data Governance

## Overview

Treat ClickUp content as potentially sensitive and keep compliance obligations separate from unsupported API assumptions.

## Prerequisites

- A data-flow inventory covering tasks, descriptions, comments, attachments, members, webhooks, logs, and backups
- Authorized legal/security retention, deletion, residency, and access rules
- A scoped credential plus test fixtures that contain no real personal or confidential data

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect the repository, adapters, configuration names, tests, and evidence. Use `WebFetch` only for current official ClickUp documentation. Use `Write` or `Edit` after confirming the target file, Workspace boundary, and requested mode.

## Current Contract

- API responses reflect what the authenticated user can access; access is not proof that downstream storage is permitted.
- Webhook payloads can include user and before/after data and must be classified before persistence.
- Do not invent a universal ClickUp GDPR export/delete endpoint; map each application copy and authorized API action.
- Evidence can retain counts, hashes, classifications, and deletion receipts without retaining work content.

## Authentication

Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in `Authorization`, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret.

## Instructions

1. Trace every ClickUp field from collection through processing, storage, logs, analytics, backups, and deletion.
2. Classify direct identifiers, free text, attachments, secrets, regulated content, and business metadata.
3. Minimize fields and scopes, redact telemetry, encrypt approved storage, and set retention by class.
4. Define subject/access/deletion workflows across ClickUp and each downstream copy with legal ownership.
5. Test export and deletion on synthetic records, including backups, queues, and failed jobs.
6. Produce a gap register and implement only owner-approved remediation.

## Approval Boundaries

Do not export, bulk delete, alter retention, scan private content, or claim legal compliance without the data owner and applicable legal/security approval.

## Output

Return the data map, field classifications, auth boundary, retention/deletion controls, test receipts, gaps, and accountable owners.

## Error Handling

| Condition | Response |
|---|---|
| Data owner or lawful basis is unknown | Stop collection or expansion and escalate. |
| Logs contain task text or tokens | Quarantine artifacts, rotate exposed secrets, and remediate logging. |
| Deletion cannot reach a downstream copy | Record the exception and block a false completion claim. |
| API access exceeds purpose | Reduce scope and revoke unnecessary copies. |

## Examples

The example below is a redacted operator receipt; it contains no task text, member data, credential, or webhook secret.

```text
flows=9; sensitive-fields=6; logs-redacted=yes; retention-mapped=8/9; deletion-test=partial; compliance-claim=no
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/clickup-data-handling/references/official-docs.md)
- [Authentication and access model](https://developer.clickup.com/docs/authentication)
- [Authentication](https://developer.clickup.com/docs/authentication)
- [Rate limits](https://developer.clickup.com/docs/rate-limits)
