Agent skill · software engineering · jeremylongshore
clari-install-auth
Configure a least-privilege Clari identity and validate Revenue API or Copilot credentials without exposing secrets. Use when starting an integration or rotating access. Trigger with: "set up Clari auth", "configure a Clari token", "test Copilot credentials".
Why this skill is useful
Adds specific commands and procedures for configuring Clari API authentication and exporting data that the AI wouldn't reliably generate on its own.
What it needs
Requires jq installed locally. Requires clari account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clari Integration Identity and Token Setup Overview Establish a dedicated integration identity before building any data flow. Treat Revenue API tokens, ingestion partner keys, and Copilot key/password pairs as separate credentials with separate rotation and revocation paths. Prerequisites Named business owner and technical owner for the integration Target surface: Revenue API, v2 ingestion, or Copilot API Approved secret manager and a non-production validation boundary Instructions Step 1: Choose the surface Record the exact base URL and authentication contract: Revenue API uses the apikey header, v2 ingestion additionally requires partnerkey, and Copilot uses both X-Api-Key and X-Api-Password. Step 2: Create a dedicated identity Use a service or integration user whose hierarchy and forecast access match the intended export scope. Do not reuse a personal administrator credential. Step 3: Issue and escrow credentials Generate the credential in the Clari settings exposed for the entitled product, capture it once into the approved secret manager, and record owner and rotation metadata without copying the value into tickets or logs. Step 4: Validate the smallest read For Revenue API, call the administrative limits read or another entitled read-only endpoint. For Copilot, list a narrowly scoped resource such as users; do not create or update CRM records during authentication testing. Step 5: Prove effective access Confirm the identity can see only the expected organization, forecast hierarchy, workspace, and object set. Treat an empty result separately from successful authorization. Step 6: Document rotation and revocation Define overlap, rollback, dependent-job restart, and emergency revocation procedures before production use. Authentication Send credentials only in the provider-documented headers over HTTPS. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clari-install-auth