Agent skill · software engineering · jeremylongshore
clari-local-dev-loop
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".
Why this skill is useful
Adds specific scripts and mock data structures for Clari API integration that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python3 installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clari-local-dev-loop