Agent skill · software engineering · jeremylongshore
clari-hello-world
Run one bounded Clari forecast export through request, status polling, and result retrieval. Use when proving Revenue API connectivity or learning the job lifecycle. Trigger with: "run my first Clari export", "test Clari connectivity", "export a forecast snapshot".
Why this skill is useful
Adds executable scripts for interacting with the Clari API, enabling forecast exports and job status checks that the AI cannot generate on its own.
What it needs
Requires jq, python3 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
First Clari Forecast Export Overview Prove the complete asynchronous export contract with one small, non-production forecast request. Success means retaining the forecast ID, job ID, terminal state, result format, and a redacted schema sample—not merely receiving an initial HTTP response. Prerequisites Forecast Tab ID copied from the entitled Clari Forecast view A scoped Revenue API token stored outside the repository A small time period, hierarchy scope, and approved output location Instructions Step 1: Freeze the request Record the forecast ID, time period, requested data types, scope ID, currency, history choice, and JSON or CSV format. Step 2: Check capacity Read /admin/limits and confirm both concurrent capacity and rolling monthly quota before consuming an export slot. Step 3: Queue the export Submit POST /export/forecast/{forecastId} against the documented Revenue API base and retain the returned job ID. Step 4: Poll deliberately Read /export/jobs/{jobId} with bounded backoff until DONE, ABORTED, or an operator-defined timeout. Do not treat SCHEDULED or STARTED as completion. Step 5: Retrieve once Only after DONE, fetch /export/jobs/{jobId}/results, validate content type and shape, and store the result in the approved temporary boundary. Step 6: Close the proof Record row count, schema fingerprint, status timeline, and cleanup result; delete temporary exported data according to policy. Authentication Use the Revenue API token only in the apikey header over HTTPS. Never include the header, raw response body, or revenue values in logs; authorization follows the token owner’s Clari access and hierarchy. 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-hello-world--4c3c4c