Agent skill · data analytics · jeremylongshore
clari-common-errors
Analyze and resolve Clari authentication, authorization, job, ingestion, schema, and empty-result failures from redacted evidence. Use when an integration fails or returns incomplete data. Trigger with: "debug Clari", "triage a Clari error", "fix an empty Clari export".
Why this skill is useful
Provides specific diagnostic commands and error handling patterns for the Clari API that the AI wouldn't reliably generate on its own.
What it needs
Requires jq 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 API Failure Triage Overview Classify the failure before retrying it. Separate transport, authentication, authorization, entitlement, quota, job-state, request-shape, schema, and data-scope failures so recovery does not create duplicate jobs or leak sensitive payloads. Prerequisites Surface, base URL, endpoint, method, timestamp, and environment Redacted status, headers, error code or ID, and job ID when present Expected hierarchy, forecast, workspace, entity, and time-window scope Instructions Step 1: Reconstruct the boundary Confirm host, API version, method, headers by name, request shape, and the identity used without revealing credential values. Step 2: Classify HTTP and provider state Distinguish 401, 403, 428, 429, 5xx, empty success, schema rejection, and non-terminal or aborted job states. Step 3: Check authorization and entitlement Verify Forecast Tab access, hierarchy opt-in, product entitlement, workspace membership, partner enablement, and entity configuration. Step 4: Check quota and duplication risk Read available limits when supported, inspect existing jobs, and avoid re-queuing a request whose outcome is merely unknown. Step 5: Reduce to a safe reproduction Use the smallest read-only or synthetic request that preserves the failure and remove customer values from the artifact. Step 6: Choose recovery and prove it Rotate or re-scope credentials, repair the request, wait for capacity, migrate schema, or escalate with a redacted receipt; then rerun exactly one bounded verification. Authentication Never print apikey, partnerkey, X-Api-Key, or X-Api-Password. A 200 response with empty data is not proof of correct authorization; validate the effective hierarchy and workspace separately. 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-common-errors