Agent skill · data analytics · jeremylongshore
clari-cost-tuning
Analyze and optimize Clari integration consumption across export quota, Copilot requests, transfer, storage, and warehouse work. Use when reducing unnecessary runs. Trigger with: "reduce Clari cost", "budget Clari exports", "tune Clari retention".
Why this skill is useful
Provides specific strategies and code snippets for optimizing Clari API usage and reducing costs that the AI wouldn't reliably generate on its own.
What it needs
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 Export and Data-Cost Governance Overview Optimize total integration consumption without inventing public Clari price claims. Provider request capacity, large result transfer, raw-data retention, repeated transformations, and warehouse scans are measurable levers even when commercial pricing is contract-specific. Prerequisites Export and Copilot request counts by workload and owner Result bytes, rows, retention, storage, and warehouse scan metrics Freshness, recovery, audit, and analytical requirements Instructions Step 1: Attribute consumption Tag every scheduled or ad hoc request with owner, business outcome, surface, window, selected data, and destination. Step 2: Measure the full path Track export quota, Copilot calls, result size, transfer, landing retention, transformation compute, warehouse storage, and query scans. Step 3: Remove redundant work Reuse immutable approved snapshots, coalesce identical requests, narrow history and fields, and resume from checkpoints instead of full reruns. Step 4: Set freshness tiers Give operational, analytical, audit, and backfill workloads explicit cadences and defer low-value work when quota or budget is constrained. Step 5: Tune retention and layout Keep raw data only as policy requires, compact normalized data, partition by access pattern, and preserve lineage even when payloads expire. Step 6: Review tradeoffs Compare consumption savings with freshness, recovery, correctness, and compliance impact before promoting a change. Authentication Consumption telemetry must contain credential references and workload identifiers, never secret values or sensitive payloads. Do not create additional tokens to bypass organization limits. 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-cost-tuning