Agent skill · data analytics · jeremylongshore
clari-core-workflow-a
Build a Clari forecast-export pipeline with reconciliation, schema controls, and warehouse lineage. Use when loading forecasts, quotas, adjustments, or CRM totals. Trigger with: "export Clari forecasts", "load Clari into the warehouse", "build a forecast pipeline".
Why this skill is useful
Adds an executable pipeline script for exporting and transforming Clari data to Snowflake or BigQuery, which is not commonly found in public documentation.
What it needs
Requires python3, snowflake-connector-python 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 Forecast Warehouse Pipeline Overview Move forecast data through a three-stage pipeline: immutable landing, validated normalization, and reconciled publication. Preserve Clari identifiers and export context so every dashboard value can be traced back to one job and request. Prerequisites Forecast ID, hierarchy scope, fiscal-period convention, and requested data types Landing storage with encryption, retention, and access controls Warehouse schema owner and reconciliation tolerances Instructions Step 1: Define the snapshot key Use forecast ID, requested time period, scope, currency, data types, and export timestamp as the immutable business key. Step 2: Reserve export capacity Read organization limits and ensure the scheduler will not exceed concurrent or rolling quota constraints. Step 3: Run the asynchronous export Queue the forecast job, poll boundedly to a terminal state, and retrieve the result only after DONE. Step 4: Land before transforming Write the original approved result to immutable, access-controlled storage with job ID, content hash, contract fingerprint, and ingestion timestamp. Step 5: Normalize and reconcile Map fields into versioned tables, preserve raw identifiers, check row counts and totals, and quarantine unknown fields or malformed monetary values. Step 6: Publish atomically Expose the new snapshot only after reconciliation passes; otherwise keep the prior known-good snapshot and emit an actionable failure receipt. Authentication Use a dedicated Revenue API integration identity and apikey header. Warehouse credentials must be separate from the Clari token, and logs must exclude both secrets and raw forecast values. 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-core-workflow-a