Agent skill · data analytics · jeremylongshore
clickup-debug-bundle
Collect a minimal redacted ClickUp connectivity and contract bundle without task bodies, tokens, or webhook secrets. Use when escalating a ClickUp API incident. Trigger with "ClickUp debug bundle", "ClickUp diagnostics", or "collect ClickUp evidence".
Why this skill is useful
Adds executable scripts for collecting and packaging ClickUp API diagnostics that aren't available in public documentation.
What it needs
Requires bash, curl, python3, tar installed locally. Requires clickup account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
ClickUp Redacted Diagnostic Bundle Overview Create supportable evidence while preventing a troubleshooting artifact from becoming a second sensitive-data store. Make every included field explainable to the named reviewer. Prerequisites An incident identifier, approved output directory, retention deadline, and named reviewer A scoped credential stored outside command history and artifact content An allow-list of read-only probes and fields 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 Useful evidence includes status, endpoint version, latency, response type, sanitized error code, and rate headers. GET /api/v2/user and GET /api/v2/team can prove identity and authorized Workspaces without reading task content. Provider status is separate from tenant authorization and application behavior. Authorization headers, response bodies, user emails, task names, comments, attachments, and webhook secrets are excluded. 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. Confirm incident scope, collection owner, field allow-list, output path, and deletion deadline. 2. Inspect local configuration names and versions without printing values. 3. Run bounded read-only identity/workspace and status probes; capture only approved metadata. 4. Record sanitized rate headers, status codes, timings, schema digests, and local adapter versions. 5. Scan the bundle for credential and content patterns; require human review before sharing. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-debug-bundle