clickup-observability
Monitor ClickUp API integrations with metrics, tracing, structured logging, and alerting using Prometheus, OpenTelemetry, and Grafana. "monitor clickup", "clickup alerts", "clickup tracing", "clickup dashboard". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-observability --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ClickUp Observability ## Overview Monitor ClickUp API v2 integrations with metrics (request rate, latency, errors, rate limit usage), distributed tracing, and alerting. ## Key Metrics | Metric | Type | Labels | Description | |--------|------|--------|-------------| | `clickup_requests_total` | Counter | method, endpoint, status | Total API requests | | `clickup_request_duration_seconds` | Histog
What does the clickup-observability skill do?
Monitor ClickUp API integrations with metrics, tracing, structured logging, and alerting using Prometheus, OpenTelemetry, and Grafana. "monitor clickup", "clickup alerts", "clickup tracing", "clickup dashboard". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-observability --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.