Agent skill · data analytics · jeremylongshore
clari-reference-architecture
Design a Clari architecture that separates Revenue exports, v2 ingestion, Copilot, control state, landing, validation, and publication. Use when defining or reviewing a platform boundary. Trigger with: "design Clari architecture", "review a Clari topology", "map Clari data flow".
Why this skill is useful
Provides specific integration patterns and data warehouse schema for Clari revenue intelligence that the AI wouldn't reliably generate on its own.
What it needs
Requires airflow, grafana, snowflake 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 Governed Integration Architecture Overview Separate control-plane state from sensitive data and isolate each provider surface behind its own adapter. The architecture should make job identity, cursor state, source lineage, schema versions, mutations, and published datasets independently auditable. Prerequisites Business flows and read/write endpoint inventory Data-classification, retention, residency, and access requirements Recovery point, recovery time, freshness, and reconciliation objectives Instructions Step 1: Draw trust boundaries Place Revenue, ingestion, Copilot, secrets, scheduler, state store, landing zone, validator, warehouse, and consumers in explicit zones. Step 2: Separate provider adapters Use distinct hosts, credential types, schemas, limiters, and mutation policies for each surface. Step 3: Design durable control state Persist request fingerprints, provider job IDs, cursors, terminal states, contract fingerprints, and retry decisions outside ephemeral workers. Step 4: Design the data path Land immutable results, validate and reconcile in quarantine, normalize with lineage, then atomically publish approved versions. Step 5: Design failure containment Prevent provider failure, schema drift, partial load, or unauthorized mutation from advancing consumer-facing data. Step 6: Prove operability Walk happy path, provider outage, quota exhaustion, credential rotation, schema drift, rollback, deletion, and support escalation. Authentication Keep credential issuance and rotation in a dedicated secrets boundary. Adapters receive references for only one surface and environment, while downstream processors receive data but no provider credentials. 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-reference-architecture