Agent skill · software engineering · jeremylongshore
salesloft-reference-architecture
Design a multi-team Salesloft integration with explicit tenant, auth, client, scheduler, cursor, webhook, queue, reconciliation, and ownership boundaries. Use when reviewing or creating production architecture. Trigger with "Salesloft architecture", "design Salesloft integration", or "Salesloft multi-tenant system".
Why this skill is useful
Adds a complete production architecture for SalesLoft API integrations, including specific service layer patterns and executable code examples that enhance integration capabilities.
What it needs
Requires axios, bullmq, pg, prometheus, redis 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 Integration Reference Architecture Overview This skill maps Salesloft integration responsibilities into inspectable components and data flows. It treats tenant isolation, rate sharing, and reconciliation as architectural requirements rather than library details. Prerequisites Business workflows, team topology, data classes, and service objectives Auth-flow and endpoint/scope inventory Hosting, queue, database, secret-store, and observability constraints Named service, security, data, and incident owners Tool Discipline Use Read, Glob, and Grep to inspect repository topology, boundaries, schemas, and deployment files. Use WebFetch only for official Salesloft contracts. Use Write or Edit after confirming the intended architecture artifact. Current Contract Every request carries an explicit team context and tenant-bound Bearer credential. The client preserves endpoint-specific requests, response envelopes, pagination, and rate metadata. A scheduler coordinates the team-wide cost budget across workers and integrations. Incremental readers persist microsecond updatedat cursors with overlap and deduplication. Webhook ingress preserves raw bytes, verifies SHA-1 HMAC and callback token, then queues durable idempotent work. Authentication Model separate authorization-code, customer API-key, and private client-credentials lifecycles. Keep encrypted credentials and refresh state keyed by immutable Salesloft team identity. Instructions 1. Map actors, Salesloft teams, trust zones, data classes, and all read/write flows. 2. Define tenant context at ingress and carry it through client, queue, cache, database, and logs. 3. Place auth resolution and refresh behind a serialized tenant-bound service. 4. Place request shaping, envelopes, paging, errors, and rate headers behind a narrow client. 5. Separate webhook receipt from processing and pair it with cursor-based reconciliation. 6. Define mutation ownership, idempotency, read-after-write, and repair workflows. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesloft-reference-architecture