Agent skill

salesforce-reliability-patterns

Implement Salesforce reliability patterns including circuit breakers, idempotent upserts, and fallback caching. Use when building fault-tolerant Salesforce integrations, implementing retry strategies, or adding resilience to production Salesforce services. Trigger with phrases like "salesforce reliability", "salesforce circuit breaker", "salesforce idempotent", "salesforce resilience", "salesforce fallback", "salesforce retry". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesforce-reliability-patterns --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Version: 1.7.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEdit
Requires: Designed for Claude Code
Path: plugins/saas-packs/salesforce-pack/skills/salesforce-reliability-patterns/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Salesforce Reliability Patterns ## Overview Production-grade reliability patterns for Salesforce integrations: circuit breakers for API outages, idempotent operations using External IDs, graceful degradation with cached data, and dead letter queues for failed operations. ## Prerequisites - jsforce connection configured - Understanding of Salesforce error codes (see `salesforce-common-errors`) - Redis or database for state management (optional) - opossum or similar circuit breaker library ## Instructions ### Step 1: Circuit Breaker for Salesforce API ```typescript import CircuitBreaker from 'opossum'; import { getConnection } from './salesforce/connection'; // Circuit breaker wraps all Salesforce calls const sfBreaker = new CircuitBreaker( async (fn: () => Promise<any>) => fn(), { timeout: 30000, // SF calls can be slow — 30s timeout errorThresholdPercentage: 50, // Open circuit at 50% error rate resetTimeout: 60000, // Try again after 1 minute volumeThreshold: 10, // Need 10 calls before evaluating errorFilter: (error: any) => { // Don't count client errors as circuit-breaking failures const nonCircuitErrors = ['INVALID_FIELD', 'MALFORMED_QUERY', 'REQUIRED_FIELD_MISSING']; return

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Step 1: Circuit Breaker for Salesforce API
  5. Step 2: Idempotent Operations with External IDs
  6. Step 3: Retry with Salesforce-Specific Error Classification
  7. Step 4: Graceful Degradation with Stale Data
  8. Step 5: Dead Letter Queue for Failed Operations
  9. Output
  10. Error Handling
  11. Resources
  12. Next Steps
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the salesforce-reliability-patterns skill do?

Implement Salesforce reliability patterns including circuit breakers, idempotent upserts, and fallback caching. Use when building fault-tolerant Salesforce integrations, implementing retry strategies, or adding resilience to production Salesforce services. Trigger with phrases like "salesforce reliability", "salesforce circuit breaker", "salesforce idempotent", "salesforce resilience", "salesforce fallback", "salesforce retry". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesforce-reliability-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going