clickup-local-dev-loop
/clickup-local-dev-loop
Rozwija adaptery ClickUp z fałszywym transportem, fixture'ami schematów, deterministycznymi zegarami i opcjonalną sondą live, bez zmian w prawdziwym Workspace.
- Autor
- jeremylongshore ↗
- Repozytorium
- tons-of-skills-marketplace ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 3
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Rozwija adaptery ClickUp z fałszywym transportem, fixture'ami schematów, deterministycznymi zegarami i opcjonalną sondą live, bez zmian w prawdziwym Workspace.
Wyzwalacze z opisu
Argumenty
/clickup-local-dev-loop [repository-path] [offline|live-probe]
Oryginalny opis (EN)
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".
Jak działa
- Overview
- Prerequisites
- Tool Discipline
- Current Contract
- Authentication
- Instructions
- Approval Boundaries
- Output
- Error Handling
- Examples
Podgląd SKILL.md
--- 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)
Pliki w paczce (2)
- SKILL.md 4 KB
- references/official-docs.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie clickup-local-dev-loop.
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 0295f8f10daf (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100together-local-dev-loop
Wspiera rozwój integracji Together AI z fałszywym transportem, nagranymi kształtami odpowiedzi i deterministycznymi asercjami, bez wydawania tokenów przy każdym teście. - 100testing-clickup-cli
Uruchamia testy clickup-cli: jednostkowe, e2e na prawdziwym workspace ClickUp i przygotowanie danych testowych. - 100clickup-webhooks
Odbiera i weryfikuje webhooki ClickUp, w tym podpis X-Signature i zdarzenia taskCreated, taskUpdated, taskStatusUpdated i taskCommentPosted. - 100clickup-ci-integration
Sprawdza adaptery ClickUp w CI za pomocą offline'owych kontraktów OpenAPI i chronionej sondy live tylko do odczytu. - 100clickup
Pobiera szczegóły zadań ClickUp, wyświetla komentarze oraz tworzy i zarządza zadaniami po adresach URL lub identyfikatorach. - 100clickup
Wywołuje natywne API ClickUp przez Proxy API Apideck z zarządzanym uwierzytelnianiem Vault, bez mapowania na ujednolicone zasoby.