Agent skill · software engineering · jeremylongshore
clari-ci-integration
Validate a Clari integration in CI with offline OpenAPI-derived contracts, synthetic job lifecycles, schema drift checks, and secret scanning. Use when adding release gates. Trigger with: "add Clari CI", "test the Clari contract", "gate a Clari release".
Why this skill is useful
Adds a complete GitHub Actions workflow for testing Clari integrations, including API connectivity and schema validation scripts.
What it needs
Requires pip, python installed locally. Requires github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clari Contract Validation in CI Overview Keep the required CI lane deterministic and credential-free. Test only owned endpoints and transformations offline, while running any provider-connected smoke test as an explicit, non-blocking or separately authorized environment gate. Prerequisites Pinned endpoint and schema manifest for each used surface Synthetic fixtures for success, empty, throttled, aborted, malformed, and drifted responses Secret scanner and artifact-retention policy Instructions Step 1: Pin the contract evidence Record provider URL, contract version, content fingerprint, extraction date, and the subset of operations the integration owns. Step 2: Test request construction Assert exact hosts, methods, paths, headers by name, payload schemas, timeouts, and prohibited mutation defaults. Step 3: Test lifecycle behavior Simulate queue, poll, terminal result, cancellation, pagination, 429, timeout, and restart from durable state. Step 4: Test data gates Assert schema validation, reconciliation, unknown-field quarantine, redaction, and atomic publication behavior. Step 5: Scan outputs Fail on credential patterns, real customer fixtures, unredacted headers, or sensitive payloads in logs and snapshots. Step 6: Separate live smoke testing If authorized, run one minimal non-production read with a short timeout and store only a redacted receipt outside the deterministic required lane. Authentication Required CI must use dummy credentials and no provider network access. Any live smoke credential comes from protected environment secrets, is restricted to non-production reads, and is never available to forked or untrusted jobs. 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-ci-integration