Agent skill · software engineering · jeremylongshore

clari-debug-bundle

Analyze a Clari incident and collect a minimal support bundle with job timelines, contract fingerprints, and secret-safe evidence. Use when escalating a provider or pipeline failure. Trigger with: "collect Clari diagnostics", "build a Clari support bundle", "redact a Clari incident".

Why this skill is useful

Adds an executable script for collecting Clari API diagnostics that automates the support ticket preparation process.

What it needs

Requires curl, 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

Clari Redacted Support Bundle Overview A useful support bundle explains what happened without copying credentials or customer payloads. Collect identifiers, timing, states, hashes, schema summaries, and controlled samples under a manifest that is reviewable before sharing. Prerequisites Incident ID, owner, environment, surface, and affected window Exact endpoint and method inventory plus provider job IDs or cursors Approved redaction rules, retention, and sharing destination Instructions Step 1: Create the manifest Record collector version, contract fingerprint, host, endpoint names, request fingerprints, timestamps, and system versions. Step 2: Collect control-plane evidence Capture HTTP statuses, redacted response headers, error codes or IDs, job state transitions, attempts, waits, and scheduler ownership. Step 3: Collect data-plane summaries Record content type, byte and row counts, field names, schema hash, and reconciliation deltas without raw revenue, identity, transcript, or recording data. Step 4: Collect local health Include deployment version, checkpoint state, queue depth, destination health, and relevant redacted logs. Step 5: Scan and review Search for all credential header names, token patterns, emails, names, deal values, transcript text, and signed URLs; require human review before sharing. Step 6: Seal and expire Hash the bundle, encrypt it, record recipients and expiry, and delete working copies according to incident policy. Authentication Never collect values for apikey, partnerkey, X-Api-Key, or X-Api-Password. If a credential may have entered any artifact, stop distribution and rotate it before continuing. 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-debug-bundle

View the source on GitHub

Browse the @skills marketplace