Skip to content
Skills Library
Programming · Analysis

salesloft-debug-bundle

/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".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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".

Triggers from the description

Salesloft debug bundleSalesloft support evidenceSalesloft diagnostics

Arguments

/salesloft-debug-bundle [repository-path] [incident-id]
Original author description

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".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 69 lines, 434 words
SKILL.md preview
---
name: salesloft-debug-bundle
description: >-
  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".
argument-hint: "[repository-path] [incident-id]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.6.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- saas
- salesloft
- diagnostics
model: inherit
effort: medium
compatibility: Designed for Claude Code
---
# 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. External sharing requires named reviewer approval and an expiry date.

## Output

Return bundle path, file inventory, redactions, checksums, evidence timeline, hypotheses, missing evidence, reviewer, and deletion date.

## Error Handling

| Condition | Response |
|---|---|
| Secret scanner matches | Quarantine, remove the value, rotate if exposure is possible, and rebuild. |
| API Logs empty | Wait for documented lag and verify filters; do not infer no request. |
| Customer data present | Remove or aggregate it before the bundle leaves the system. |
| Evidence conflicts | Preserve both observations and label the discrepancy. |

## Examples

The example below shows the minimum redacted evidence expected from a successful invocation of this operator workflow.

```text
incident=SL-204; files=4; secret-findings=0; pii-findings=0; reviewer=pending
```

## Resources

- [Skill-specific official documentation](references/official-docs.md)
- [Salesloft API Logs](https://developers.salesloft.com/docs/platform/guides/api-logs/)
- [Request and response format](https://developers.salesloft.com/docs/platform/api-basics/request-response-format/)
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 3 KB

Versions

The database has no other skills named salesloft-debug-bundle.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 270462ca900d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100salesloft-common-errors
    Classify Salesloft API failures from status, documented error envelopes, auth context, visibility, and rate metadata without exposing customer data. Use when an integration returns 401, 403, 404, 422, 429, or 5xx. Trigger with "Salesloft error", "Salesloft request failed", or "debug Salesloft API".
  • 100salesloft-upgrade-migration
    Migrate an existing Salesloft integration through an evidence-backed endpoint, auth, schema, scope, and behavior diff with shadow validation and rollback. Use when current contracts or application assumptions change. Trigger with "Salesloft migration", "upgrade Salesloft…
  • 100salesloft-webhooks
    Receive and verify Salesloft webhooks. Use when setting up a Salesloft webhook endpoint, verifying the x-salesloft-signature header (HMAC-SHA1 hex keyed with the subscription's callback_token), debugging Salesloft signature verification failures, or handling events like…
  • 90salesloft-cadences
    Builds and optimizes Salesloft cadences: Rhythm, Conversations, multi-channel orchestration, and analytics. Use when the user is setting up or improving cadences in Salesloft. Triggers on: "Salesloft", "Salesloft cadence", "Rhythm", "Salesloft automation".
  • 100customerio-debug-bundle
    Collect Customer.io debug evidence for support. Use when creating support tickets, reporting issues, or documenting integration problems. Trigger with phrases like "customer.io debug", "customer.io support ticket", "collect customer.io logs", "customer.io diagnostics".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.