Agent skill · software engineering · jeremylongshore
clari-deploy-integration
Deploy a single-writer Clari scheduler with durable job state, atomic publication, observability, and rollback. Use when productionizing recurring Revenue or Copilot extraction. Trigger with: "deploy a Clari pipeline", "schedule Clari exports", "ship Clari integration".
Why this skill is useful
Adds executable scripts for deploying Clari export pipelines using Airflow, AWS Lambda, and Google Cloud Functions, which are not commonly found in public documentation.
What it needs
Requires aws-cli, gcloud installed locally. Requires aws, clari, google-cloud account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Deploy a Clari Scheduled Data Pipeline Overview Deploy orchestration rather than embedding long-running polling in ephemeral request handlers. Ensure one logical scheduler owns each workload, persists provider job IDs or cursors before waiting, and separates landing from publication. Prerequisites Versioned container or runtime artifact and infrastructure manifest Per-surface credential references and least-privilege identity Durable checkpoint store, encrypted landing zone, and atomic publish mechanism Instructions Step 1: Package the worker Pin dependencies and contract fingerprints, run as a non-root identity, and expose no inbound endpoint unless operationally required. Step 2: Inject configuration Supply base URLs, credential references, forecast or workspace scope, cadence, limits, destination, and retention through managed configuration. Step 3: Enforce single-writer scheduling Use a lease or platform concurrency rule so overlapping invocations cannot queue duplicate exports or replay mutations. Step 4: Persist before polling Write the request fingerprint and returned job ID or Copilot cursor durably before any wait, retry, or process exit. Step 5: Publish through gates Land, validate, reconcile, and atomically advance the destination only after the provider operation and local checks succeed. Step 6: Roll out and roll back Canary one bounded workload, compare service levels and data, then promote; retain the prior artifact and checkpoint reader for reversal. Authentication Mount only the credentials needed by the selected surface and environment. Prevent secret values and provider payloads from entering process arguments, deployment diffs, health endpoints, or logs. 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-deploy-integration