clari-local-dev-loop
/clari-local-dev-loop
Buduje i testuje integrację z Clari lokalnie na zanonimizowanych fixture'ach i deterministycznym symulatorze zadań, bez zużywania limitu i bez ujawniania danych klientów.
- 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
- 2
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
Buduje i testuje integrację z Clari lokalnie na zanonimizowanych fixture'ach i deterministycznym symulatorze zadań, bez zużywania limitu i bez ujawniania danych klientów.
Wyzwalacze z opisu
Argumenty
/clari-local-dev-loop [surface-contract-and-fixture-set]
Oryginalny opis (EN)
Build and test a Clari integration locally with redacted fixtures and a deterministic job simulator. Use when developing without spending quota or exposing customer data. Trigger with: "mock Clari locally", "build Clari fixtures", "test Clari offline".
Jak działa
- Overview
- Prerequisites
- Instructions
- Authentication
- Tool Discipline
- Output
- Examples
- Error Handling
- Resources
Podgląd SKILL.md
--- name: clari-local-dev-loop description: >- Build and test a Clari integration locally with redacted fixtures and a deterministic job simulator. Use when developing without spending quota or exposing customer data. Trigger with: "mock Clari locally", "build Clari fixtures", "test Clari offline". allowed-tools: Read, Grep, Write, Edit version: 2.0.0 argument-hint: '[surface-contract-and-fixture-set]' model: inherit effort: high license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io> tags: - saas - clari - local-development - fixtures - contract-testing compatibility: 'Requires a local test runner, approved synthetic or irreversibly redacted fixtures, and a pinned provider contract snapshot.' --- # Clari Offline Contract Development Loop ## Overview Make offline development the default and live provider calls an explicit integration stage. Model the provider’s authentication headers, job transitions, pagination, error objects, and schema drift without storing secrets or production records. ## Prerequisites - Chosen Clari surface and pinned contract version or fingerprint - Synthetic fixtures covering success, empty, partial, and failure responses - Local secret scanning and test-data classification rules ## Instructions ### Step 1: Define the contract boundary List endpoints, headers, request fields, response fields, job states, and pagination semantics used by the integration. ### Step 2: Build synthetic fixtures Create minimal payloads that preserve shapes and identifiers while containing no real people, accounts, calls, forecasts, or deal values. ### Step 3: Simulate state transitions Make the test server move deterministically through queued, running, completed, aborted, rate-limited, and timed-out paths. ### Step 4: Exercise adapters Run parser, schema, retry, pagination, idempotency, and redaction tests against the simulator with network access disabled. ### Step 5: Add one gated live smoke test Use a dedicated non-production identity and the smallest read-only request; skip it unless credentials and explicit integration-test approval are present. ### Step 6: Refresh deliberately When the provider contract changes, review the diff, update fixtures and assertions together, and retain the old failing fixture as migration evidence. ## Authentication Offline tests must use obvious dummy values. A gated live test may read credentials from the approved secret manager at runtime, but must never serialize headers or provider payloads into test output. ## Tool Discipline Use Read and Grep to inspect configuration, provider contracts, fixtures, logs, schemas, and existing tests before proposing a change. Use Write or Edit only for the approved plan, implementation, test, or redacted receipt; do not issue, rotate, revoke, create, update, cancel, delete, export, ingest, or publish provider data without explicit operator approval. ## Output - Pinned endpoint and schema contract manifest - Synthetic fixture set with provenance and data-classification receipt - Offline test report plus separately identified live-smoke result Return the exact surface, environment, resource or job identifiers, contract fingerprint, evidence, unresolved risks, and final decision without exposing credentials or sensitive customer data. ## Examples A local export client receives synthetic `SCHEDULED`, `STARTED`, and `DONE` responses, then a 429 and an `ABORTED` job. CI proves bounded retry and redaction without consuming a Clari export. ## Error Handling | Failure | Response | | --- | --- | | Fixture contains real customer data | Quarantine and remove it, rotate any exposed credential, and replace it with generated values. | | Mock diverges from the provider contract | Pin the current contract fingerprint and add a regression fixture for the observed delta. | | Live smoke runs unexpectedly | Fail closed unless an explicit environment gate and non-production credential are both present. | ## Resources - [First-party source notes](references/official-docs.md) - [Clari Revenue API reference](https://developer.clari.com/default/documentation/external_spec) - [Clari Copilot API reference](https://api-doc.copilot.clari.com/)
Pliki w paczce (2)
- SKILL.md 4 KB
- references/official-docs.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie clari-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 baa5109bf387 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100clari-common-errors
Analizuje i rozwiązuje błędy uwierzytelniania, autoryzacji, zadań, ingestii, schematów i pustych wyników Clari na podstawie zanonimizowanych dowodów. - 100clari-ci-integration
Waliduje integrację z Clari w CI przez offline'owe kontrakty z OpenAPI, syntetyczne cykle zadań, kontrolę dryfu schematów i skanowanie sekretów, jako bramkę wydań. - 100customerio-local-dev-loop
Konfiguruje lokalny przebieg pracy z Customer.io: testy lokalne, środowisko deweloperskie i pracę offline nad integracjami.