Agent skill · data analytics · jeremylongshore
clickup-observability
Instrument ClickUp requests, queues, webhooks, and reconciliation with content-free metrics, traces, alerts, and health evidence. Use when operating a ClickUp integration in production. Trigger with "ClickUp observability", "ClickUp metrics", or "monitor ClickUp webhooks".
Why this skill is useful
Adds executable scripts for monitoring ClickUp API integrations with Prometheus and OpenTelemetry, which are not commonly known.
What it needs
Requires @opentelemetry/api, prom-client 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 Integration Observability Overview Expose reliability, rate pressure, delivery health, and business reconciliation without exporting task or member content. Prerequisites A typed ClickUp transport and durable webhook/job queues Approved telemetry fields, retention, access, sampling, and alert ownership Service-level objectives for request success, latency, queue age, freshness, and reconciliation 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 Capture X-RateLimit- values as bounded numeric telemetry without capturing the Authorization header. Webhook objects expose health/failure state; over-seven-second or unsuccessful delivery contributes to failure behavior. ClickUp retries an event up to five times, but failed events are not later resent after those attempts. Task names, descriptions, comments, attachments, emails, raw bodies, tokens, and webhook secrets are not telemetry. 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. Inventory request, queue, webhook, reconciliation, and deployment signals plus current data exposure. 2. Define low-cardinality metrics by endpoint family, version, status class, environment, and Workspace alias. 3. Add trace spans around the transport and queue without request/response content. 4. Monitor rate remaining/reset, 429s, webhook latency/status/fail count, queue age, and duplicate suppression. 5. Create actionable alerts with runbook links, owners, and tested thresholds from baseline data. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-observability