Agent skill · data analytics · jeremylongshore
salesforce-debug-bundle
Build a privacy-safe Salesforce support bundle with request, limits, metadata, job, event, and change evidence. Use when escalating an integration defect. Trigger with "build a Salesforce debug bundle".
Why this skill is useful
Adds a comprehensive script for collecting Salesforce diagnostic data, including API limits and debug logs, which the AI cannot generate on its own.
What it needs
Requires salesforce-cli installed locally. Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Privacy-Safe Salesforce Support Evidence Bundle Overview Collect the smallest reproducible evidence set while excluding credentials, raw business records, personal data, and unrelated org configuration. Prerequisites Incident identifier, time window, environment, affected operation, and support destination Approved evidence classes, redaction policy, retention period, and transfer channel Read-only access to the specific limits, metadata, job, event, or log evidence required Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Salesforce diagnostic surfaces vary by product, edition, permission, and entitlement. Limits can be read through the versioned REST resource, while debug logs, Event Monitoring, async jobs, and event metrics require separate access and interpretation. Authentication Use a dedicated read-only diagnostic principal where possible. Never include access or refresh tokens, session IDs, cookies, authorization headers, client secrets, private keys, usernames, org IDs unless approved, or raw record payloads. Instructions 1. Create a manifest naming incident, time window, environment class, components, evidence owners, retention, and recipient. 2. Collect application version, dependency lock, API version, redacted request ID, status, timing, retry history, and recent deployment IDs. 3. Add only relevant limits, object metadata fingerprints, async job summaries, event channel metrics, and log excerpts. 4. Replace record IDs, user IDs, org IDs, domains, field values, queries, and payloads with stable redaction tokens where required. 5. Scan the bundle for credentials, authorization material, personal data, customer names, and unrelated records. 6. Generate hashes and a manifest, then have the incident and data owners review the exact archive. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-debug-bundle--747b05