Skip to content
Skills Library
Programming · Testing

clickup-local-dev-loop

/clickup-local-dev-loop

Develop ClickUp adapters with a fake transport, schema fixtures, deterministic clocks, and an opt-in bounded live probe. Use when iterating without mutating a real Workspace. Trigger with "ClickUp local dev", "mock ClickUp API", or "ClickUp fixtures".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Develop ClickUp adapters with a fake transport, schema fixtures, deterministic clocks, and an opt-in bounded live probe. Use when iterating without mutating a real Workspace. Trigger with "ClickUp local dev", "mock ClickUp API", or "ClickUp fixtures".

Triggers from the description

ClickUp local devmock ClickUp APIClickUp fixtures

Arguments

/clickup-local-dev-loop [repository-path] [offline|live-probe]
Original author description

Develop ClickUp adapters with a fake transport, schema fixtures, deterministic clocks, and an opt-in bounded live probe. Use when iterating without mutating a real Workspace. Trigger with "ClickUp local dev", "mock ClickUp API", or "ClickUp fixtures".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 68 lines, 438 words
SKILL.md preview
---
name: clickup-local-dev-loop
description: >-
  Develop ClickUp adapters with a fake transport, schema fixtures, deterministic clocks, and an opt-in bounded live probe. Use when iterating without mutating a real Workspace. Trigger with "ClickUp local dev", "mock ClickUp API", or "ClickUp fixtures".
argument-hint: "[repository-path] [offline|live-probe]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- saas
- clickup
- development
model: inherit
effort: high
compatibility: Designed for Claude Code; ordinary tests are offline and the live probe needs a non-production credential
---
# ClickUp Deterministic Local Development

## Overview

Keep the fast loop offline while preserving exact provider shapes and a deliberate path to detect real API drift.

## Prerequisites

- A transport interface around all ClickUp HTTP calls
- Sanitized fixtures derived from documented v2/v3 schemas, including nulls and errors
- A deterministic clock, fake queue, and optional isolated Workspace for a live read

## 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

- Fixtures preserve string/number/null differences in task and webhook payloads.
- Separate base paths and schemas for v2 and selected v3 operations.
- Mock 429 headers, zero-based task pages, comment cursors, auth codes, and webhook delivery retries.
- No ordinary unit test reads a developer token or creates a ClickUp object.

## 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 direct HTTP calls and route them through an injectable transport.
2. Create fixtures for identity, Workspace, tasks, pages, Custom Fields, webhooks, errors, and rate headers.
3. Freeze time and IDs; make request order, retry jitter, and queue outcomes deterministic.
4. Test raw-body HMAC verification, redaction, Workspace guards, and partial-write recovery.
5. Add an explicit live-probe command limited to read-only identity/Workspace calls.
6. Run offline tests by default and record any provider drift found by the live probe.

## Approval Boundaries

Do not record production responses, use personal work data as fixtures, or enable writes in the default local/test path.

## Output

Return fixture provenance, offline coverage, direct-call violations, deterministic test result, live-probe result, and drift. Distinguish simulated success from provider-confirmed evidence.

## Error Handling

| Condition | Response |
|---|---|
| Fixture contains personal or task content | Delete/quarantine it and replace with synthetic data. |
| Direct HTTP call bypasses transport | Fail the test and refactor the boundary. |
| Live credential is absent | Skip the probe without weakening offline tests. |
| Live response drifts | Update contracts only after official-source review. |

## Examples

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

```text
mode=offline; fixtures=14; network-calls=0; clocks=frozen; hmac-tests=pass; live-probe=skipped
```

## Resources

- [Skill-specific official documentation](references/official-docs.md)
- [OpenAPI specifications](https://developer.clickup.com/docs/open-api-spec)
- [Authentication](https://developer.clickup.com/docs/authentication)
- [Rate limits](https://developer.clickup.com/docs/rate-limits)
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 2 KB

Versions

The database has no other skills named clickup-local-dev-loop.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 0295f8f10daf (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100together-local-dev-loop
    Develop Together AI integrations with a fake transport, recorded response shapes, deterministic assertions, and an opt-in bounded live probe. Use when iterating without spending tokens on every test. Trigger with "Together local dev", "mock Together API", or "test Together client".
  • 100testing-clickup-cli
    Run and manage tests for clickup-cli. Covers unit tests, e2e tests against a real ClickUp workspace, and the test data setup. Use when running tests, adding test coverage, debugging test failures, or setting up test fixtures.
  • 100clickup-webhooks
    Receive and verify ClickUp webhooks. Use when setting up ClickUp webhook handlers, debugging X-Signature verification, or handling ClickUp events like taskCreated, taskUpdated, taskStatusUpdated, or taskCommentPosted.
  • 100clickup-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".
  • 100clickup
    Interact with ClickUp tasks - get task details, view comments, create and manage tasks. Use when working with ClickUp task URLs or IDs.
  • 100clickup
    ClickUp via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to ClickUp's native API. Use when the user wants to call ClickUp (no unified API resource mapping). Routes through Apideck with serviceId "clickup".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.