Agent skill · software engineering · jeremylongshore
clari-prod-checklist
Analyze and gate a Clari integration for production with evidence for access, correctness, resilience, privacy, rollback, and ownership. Use when approving a launch or material change. Trigger with: "review Clari readiness", "approve Clari production", "run the Clari launch checklist".
Why this skill is useful
Adds a validation script for Clari API readiness checks and detailed production readiness criteria specific to Clari integrations.
What it needs
Requires bash installed locally. Requires clari account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clari Integration Production Readiness Overview Convert production readiness into a fail-closed evidence bundle. A green decision requires proof of provider access, contract compatibility, data correctness, quota behavior, observability, security, recovery, and operator ownership. Prerequisites Versioned release candidate and endpoint inventory Completed non-production happy-path and failure-path tests Change owner, business owner, security owner, and rollback authority Instructions Step 1: Verify identity and contracts Confirm surface-specific credentials, effective scope, base URL, API version, schema fingerprint, and entitlement. Step 2: Verify data correctness Reconcile counts, identifiers, time periods, totals, pagination, and empty-result behavior against an approved source. Step 3: Verify resilience Exercise timeout, 429, provider 5xx, aborted job, partial load, schema drift, and restart from checkpoint. Step 4: Verify security and privacy Prove secret redaction, least privilege, encryption, retention, deletion, mutation gates, and sensitive-content minimization. Step 5: Verify operations Confirm dashboards, alerts, service-status dependency, runbook, support bundle, capacity headroom, and on-call ownership. Step 6: Approve or reject Record exact artifact hashes and approvers. Launch only when rollback is rehearsed and no required evidence is missing. Authentication Production secrets must be injected from the approved manager into the matching client and never copied into release artifacts. Verify rotation and emergency revocation before launch. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clari-prod-checklist--52538e