Agent skill · software engineering · jeremylongshore
clickup-ci-integration
Gate ClickUp adapters with offline OpenAPI contracts and a protected read-only live probe. Use when adding CI for a ClickUp-backed repository. Trigger with "ClickUp CI", "test ClickUp integration", or "ClickUp contract tests".
Why this skill is useful
Adds a GitHub Actions CI/CD pipeline for ClickUp API integrations with specific testing and task management patterns not commonly known.
What it needs
Requires gh 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 Continuous Integration Overview Keep ordinary pull-request checks deterministic and secretless while retaining a separately protected probe for provider-contract drift. Prerequisites The repository's test runner, ClickUp transport boundary, and CI platform Sanitized fixtures for v2 and any selected v3 response shapes A protected non-production credential and strict request ceiling for the optional live lane 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 Pin the official v2 and v3 OpenAPI inputs separately; do not model v3 as a complete replacement. Offline tests cover authentication, plan denial, pagination, rate headers, webhook typing, and redaction. The live lane uses GET /api/v2/user or GET /api/v2/team; it does not create or update work. Fork code never receives ClickUp credentials. 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 every endpoint, version, fixture, secret reference, and network-bearing test. 2. Generate or validate transport types against pinned official OpenAPI inputs. 3. Add fixtures for success, common OAuth errors, 429 responses, null webhook fields, and page boundaries. 4. Test redaction, retry eligibility, version routing, and workspace allow-list enforcement. 5. Place the bounded live probe behind a trusted event and protected environment. 6. Publish status, schema versions, request count, and redacted drift evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-ci-integration