Agent skill · data analytics · jeremylongshore
salesforce-observability
Build Salesforce integration observability across application traces, platform status, limits, async jobs, events, logs, and business reconciliation. Use when designing monitoring. Trigger with "monitor Salesforce integration".
Why this skill is useful
Adds executable scripts for monitoring Salesforce API limits and error tracking that are not commonly found in public documentation.
What it needs
Requires prom-client 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
Salesforce Integration Observability and Reconciliation Overview Connect technical telemetry to Salesforce platform state and business correctness without exporting sensitive records into monitoring systems. Prerequisites System context, service and business objectives, APIs, jobs, event channels, orgs, and owners Current Salesforce Status, Limits, EventLogFile or entitled Event Monitoring, async-job, and event-usage surfaces Telemetry data classification, redaction, retention, alert routing, incident, and reconciliation policies 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 Status, REST limits, response headers, async jobs, platform-event usage, debug logs, and Event Monitoring expose different signals with different entitlements and delays. Limits resource values can lag recent consumption. Authentication Use separate read-only monitoring access with minimum permissions. Never emit access tokens, session IDs, authorization headers, raw SOQL results, record payloads, or unrestricted user and org identifiers as telemetry. Instructions 1. Define availability, latency, throughput, error, freshness, completeness, duplicate, limit, job, event-lag, and business-invariant objectives. 2. Instrument the adapter with redacted request IDs, operation class, API version, timing, outcome, retry, and reconciliation state. 3. Collect Salesforce platform status, relevant limit and header values, async job summaries, event metrics, and entitled logs. 4. Normalize timestamps, org and environment aliases, deployment IDs, and correlation IDs without exposing customer record data. 5. Build dashboards by environment and workload with freshness labels and separate technical from business-correctness views. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-observability