Agent skill · data analytics · jeremylongshore
salesloft-debug-bundle
Build a minimal redacted Salesloft escalation bundle with contract, auth-state, rate, timing, deployment, and API Logs evidence. Use when a failure needs support or engineering review. Trigger with "Salesloft debug bundle", "Salesloft support evidence", or "Salesloft diagnostics".
Why this skill is useful
Adds an executable script that automates the collection of diagnostic data for SalesLoft API issues, which the AI wouldn't generate on its own.
What it needs
Requires curl, jq installed locally. Requires salesloft account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesloft Redacted Debug Bundle Overview This skill produces a small evidence package that another engineer can use without receiving credentials or customer records. It separates observed facts from hypotheses. Prerequisites Incident ID, owner, timeframe, environment, and expected behavior Approved output directory and retention period Access to application logs and, when authorized, Salesloft API Logs A redaction review owner Tool Discipline Use Read, Glob, and Grep to locate bounded logs, configuration keys, and version files. Use WebFetch only for current official Salesloft documentation. Use Write or Edit only for the approved redacted artifact. Current Contract Capture method and path template, status, content type, latency, attempt count, and deployment revision. Capture auth type, expiry state, scope names, and team alias, never credential values. Capture x-ratelimit-endpoint-cost and x-ratelimit-remaining-minute when present. Salesloft API Logs can lag about five minutes and expose up to 10,000 calls or 14 days in the UI; absence is not immediate proof that no call occurred. Authentication Use existing approved access. The bundle must omit Authorization headers, refresh tokens, client secrets, API keys, callback tokens, cookies, raw bodies, and prospect fields. Instructions 1. Freeze incident scope, UTC window, environment, and affected operation. 2. Collect only bounded application events for that window and correlation key. 3. Add redacted configuration names, dependency versions, and deployment revision. 4. Add response-envelope shape and rate metadata without record contents. 5. If authorized, compare API Logs by integration, team, endpoint, time, and status after the documented lag. 6. Scan the artifact for credential patterns and CRM fields, then record checksums. 7. Require a second review before external sharing. Approval Boundaries Do not archive full environment dumps, databases, raw HTTP payloads, or unrestricted logs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesloft-debug-bundle