[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M795G8T5G4KRYJS7B1N9ZJP7":3,"skill-same:01M795G8T5G4KRYJS7B1N9ZJP7":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M795G8T5G4KRYJS7B1N9ZJP7","salesforce-reliability-patterns",null,"Implement Salesforce reliability patterns including circuit breakers, idempotent upserts, and fallback caching.\nUse when building fault-tolerant Salesforce integrations, implementing retry strategies,\nor adding resilience to production Salesforce services.\nTrigger with phrases like \"salesforce reliability\", \"salesforce circuit breaker\",\n\"salesforce idempotent\", \"salesforce resilience\", \"salesforce fallback\", \"salesforce retry\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--salesforce-pack--salesforce-reliability-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: salesforce-reliability-patterns\ndescription: |\n  Implement Salesforce reliability patterns including circuit breakers, idempotent upserts, and fallback caching.\n  Use when building fault-tolerant Salesforce integrations, implementing retry strategies,\n  or adding resilience to production Salesforce services.\n  Trigger with phrases like \"salesforce reliability\", \"salesforce circuit breaker\",\n  \"salesforce idempotent\", \"salesforce resilience\", \"salesforce fallback\", \"salesforce retry\".\nallowed-tools: Read, Write, Edit\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, crm, salesforce]\ncompatible-with: claude-code\n---\n\n# Salesforce Reliability Patterns\n\n## Overview\nProduction-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.\n\n## Prerequisites\n- jsforce connection configured\n- Understanding of Salesforce error codes (see `salesforce-common-errors`)\n- Redis or database for state management (optional)\n- opossum or similar circuit breaker library\n\n## Instructions\n\n### Step 1: Circuit Breaker for Salesforce API\n\n```typescript\nimport CircuitBreaker from 'opossum';\nimport { getConnection } from '.\u002Fsalesforce\u002Fconnection';\n\n\u002F\u002F Circuit breaker wraps all Salesforce calls\nconst sfBreaker = new CircuitBreaker(\n  async (fn: () => Promise\u003Cany>) => fn(),\n  {\n    timeout: 30000,                \u002F\u002F SF calls can be slow — 30s timeout\n    errorThresholdPercentage: 50,  \u002F\u002F Open circuit at 50% error rate\n    resetTimeout: 60000,           \u002F\u002F Try again after 1 minute\n    volumeThreshold: 10,           \u002F\u002F Need 10 calls before evaluating\n    errorFilter: (error: any) => {\n      \u002F\u002F Don't count client errors as circuit-breaking failures\n      const nonCircuitErrors = ['INVALID_FIELD', 'MALFORMED_QUERY', 'REQUIRED_FIELD_MISSING'];\n      return nonCircuitErrors.includes(error.errorCode);\n    },\n  }\n);\n\nsfBreaker.on('open', () => {\n  console.error('CIRCUIT OPEN: Salesforce API failing — requests will fail fast');\n  \u002F\u002F Alert ops team\n});\n\nsfBreaker.on('halfOpen', () => {\n  console.info('CIRCUIT HALF-OPEN: Testing Salesforce recovery...');\n});\n\nsfBreaker.on('close', () => {\n  console.info('CIRCUIT CLOSED: Salesforce API recovered');\n});\n\n\u002F\u002F Usage — all SF calls go through the breaker\nasync function safeSfQuery\u003CT>(soql: string): Promise\u003CT[]> {\n  return sfBreaker.fire(async () => {\n    const conn = await getConnection();\n    const result = await conn.query\u003CT>(soql);\n    return result.records;\n  });\n}\n```\n\n### Step 2: Idempotent Operations with External IDs\n\n```typescript\n\u002F\u002F Salesforce's upsert with External ID is naturally idempotent\n\u002F\u002F Same data sent twice = same result (no duplicates)\n\nasync function idempotentSync(\n  objectType: string,\n  records: Record\u003Cstring, any>[],\n  externalIdField: string = 'External_ID__c'\n): Promise\u003C{ success: number; failed: number; errors: any[] }> {\n  const conn = await getConnection();\n  let success = 0;\n  let failed = 0;\n  const errors: any[] = [];\n\n  \u002F\u002F Process in batches of 200 (sObject Collections limit)\n  for (let i = 0; i \u003C records.length; i += 200) {\n    const batch = records.slice(i, i + 200);\n\n    const results = await conn.sobject(objectType).upsert(batch, externalIdField);\n\n    for (const result of Array.isArray(results) ? results : [results]) {\n      if (result.success) {\n        success++;\n      } else {\n        failed++;\n        errors.push(result.errors);\n      }\n    }\n  }\n\n  return { success, failed, errors };\n}\n\n\u002F\u002F Safe to retry — same External_ID__c values will update, not duplicate\nawait idempotentSync('Account', [\n  { External_ID__c: 'EXT-001', Name: 'Acme', Industry: 'Tech' },\n  { External_ID__c: 'EXT-002', Name: 'Globex', Industry: 'Manufacturing' },\n], 'External_ID__c');\n```\n\n### Step 3: Retry with Salesforce-Specific Error Classification\n\n```typescript\nconst SF_RETRYABLE_ERRORS = [\n  'REQUEST_LIMIT_EXCEEDED',    \u002F\u002F API limit — wait and retry\n  'SERVER_UNAVAILABLE',        \u002F\u002F SF is down temporarily\n  'UNABLE_TO_LOCK_ROW',        \u002F\u002F Record contention\n  'INVALID_SESSION_ID',        \u002F\u002F Token expired — re-auth and retry\n];\n\nconst SF_FATAL_ERRORS = [\n  'INVALID_FIELD',             \u002F\u002F Code bug — won't fix itself\n  'MALFORMED_QUERY',           \u002F\u002F Code bug\n  'REQUIRED_FIELD_MISSING',    \u002F\u002F Data issue\n  'INVALID_TYPE',              \u002F\u002F Wrong sObject name\n  'INSUFFICIENT_ACCESS_OR_READONLY', \u002F\u002F Permission issue\n];\n\nasync function retryableSfCall\u003CT>(\n  operation: () => Promise\u003CT>,\n  maxRetries = 3\n): Promise\u003CT> {\n  for (let attempt = 1; attempt \u003C= maxRetries; attempt++) {\n    try {\n      return await operation();\n    } catch (error: any) {\n      const errorCode = error.errorCode || error.name;\n\n      if (SF_FATAL_ERRORS.includes(errorCode)) {\n        throw error; \u002F\u002F Don't retry — it won't help\n      }\n\n      if (errorCode === 'INVALID_SESSION_ID') {\n        \u002F\u002F Re-authenticate, then retry\n        await getConnection(); \u002F\u002F Forces re-login\n        continue;\n      }\n\n      if (attempt === maxRetries) throw error;\n\n      const delay = 2000 * Math.pow(2, attempt - 1); \u002F\u002F 2s, 4s, 8s\n      console.warn(`Retryable SF error ${errorCode}, attempt ${attempt}\u002F${maxRetries}`);\n      await new Promise(r => setTimeout(r, delay));\n    }\n  }\n  throw new Error('Unreachable');\n}\n```\n\n### Step 4: Graceful Degradation with Stale Data\n\n```typescript\nimport { Redis } from 'ioredis';\nconst redis = new Redis(process.env.REDIS_URL);\n\nasync function queryWithFallback\u003CT>(\n  soql: string,\n  cacheKey: string,\n  cacheTtlSeconds = 300\n): Promise\u003C{ data: T[]; stale: boolean }> {\n  try {\n    \u002F\u002F Try live Salesforce query\n    const records = await safeSfQuery\u003CT>(soql);\n\n    \u002F\u002F Update cache for fallback\n    await redis.set(cacheKey, JSON.stringify(records), 'EX', cacheTtlSeconds * 10);\n\n    return { data: records, stale: false };\n  } catch (error) {\n    \u002F\u002F Salesforce unavailable — serve cached data\n    const cached = await redis.get(cacheKey);\n    if (cached) {\n      console.warn(`SF unavailable, serving stale data for ${cacheKey}`);\n      return { data: JSON.parse(cached), stale: true };\n    }\n\n    throw new Error(`Salesforce unavailable and no cached data for ${cacheKey}`);\n  }\n}\n\n\u002F\u002F Usage\nconst { data: accounts, stale } = await queryWithFallback\u003CAccount>(\n  \"SELECT Id, Name, Industry FROM Account WHERE Industry = 'Technology' LIMIT 50\",\n  'sf:accounts:tech'\n);\nif (stale) {\n  \u002F\u002F Show warning to user: \"Data may be outdated\"\n}\n```\n\n### Step 5: Dead Letter Queue for Failed Operations\n\n```typescript\ninterface SfDeadLetter {\n  id: string;\n  operation: string;\n  objectType: string;\n  payload: Record\u003Cstring, any>;\n  errorCode: string;\n  errorMessage: string;\n  attempts: number;\n  firstFailure: Date;\n  lastAttempt: Date;\n}\n\nclass SalesforceDeadLetterQueue {\n  async enqueue(entry: Omit\u003CSfDeadLetter, 'id' | 'firstFailure' | 'lastAttempt' | 'attempts'>): Promise\u003Cvoid> {\n    const dlq: SfDeadLetter = {\n      ...entry,\n      id: crypto.randomUUID(),\n      attempts: 1,\n      firstFailure: new Date(),\n      lastAttempt: new Date(),\n    };\n    await redis.lpush('sf:dlq', JSON.stringify(dlq));\n    console.error(`DLQ: ${entry.operation} on ${entry.objectType} failed: ${entry.errorCode}`);\n  }\n\n  async reprocess(): Promise\u003C{ processed: number; failed: number }> {\n    let processed = 0, failed = 0;\n    let entry: string | null;\n\n    while ((entry = await redis.rpop('sf:dlq')) !== null) {\n      const dlq: SfDeadLetter = JSON.parse(entry);\n      try {\n        const conn = await getConnection();\n        await conn.sobject(dlq.objectType)[dlq.operation](dlq.payload);\n        processed++;\n      } catch (error: any) {\n        dlq.attempts++;\n        dlq.lastAttempt = new Date();\n        if (dlq.attempts \u003C 5) {\n          await redis.lpush('sf:dlq', JSON.stringify(dlq));\n        } else {\n          console.error(`DLQ: Giving up on ${dlq.id} after 5 attempts`);\n          \u002F\u002F Move to permanent failure store\n        }\n        failed++;\n      }\n    }\n    return { processed, failed };\n  }\n}\n```\n\n## Output\n- Circuit breaker preventing cascading failures\n- Idempotent upserts using External IDs\n- Error classification (retryable vs fatal)\n- Graceful degradation with stale cache data\n- Dead letter queue for failed operations\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Circuit stays open | SF outage or wrong threshold | Check status.salesforce.com; tune thresholds |\n| Duplicate records | Not using External ID upsert | Add External_ID__c field, use upsert |\n| DLQ growing | Persistent error (e.g., permission) | Check error codes — may need fix, not retry |\n| Stale cache too old | Long SF outage | Set max stale age, show user warning |\n\n## Resources\n- [Circuit Breaker Pattern](https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FCircuitBreaker.html)\n- [Opossum Documentation](https:\u002F\u002Fnodeshift.dev\u002Fopossum\u002F)\n- [External ID Fields](https:\u002F\u002Fhelp.salesforce.com\u002Fs\u002FarticleView?id=sf.fields_about_external_ids.htm)\n- [Salesforce Error Codes](https:\u002F\u002Fdeveloper.salesforce.com\u002Fdocs\u002Fatlas.en-us.api_rest.meta\u002Fapi_rest\u002Ferrorcodes.htm)\n\n## Next Steps\nFor policy enforcement, see `salesforce-policy-guardrails`.\n","# Salesforce Reliability Patterns\n\n## Overview\nProduction-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.\n\n## Prerequisites\n- jsforce connection configured\n- Understanding of Salesforce error codes (see `salesforce-common-errors`)\n- Redis or database for state management (optional)\n- opossum or similar circuit breaker library\n\n## Instructions\n\n### Step 1: Circuit Breaker for Salesforce API\n\n```typescript\nimport CircuitBreaker from 'opossum';\nimport { getConnection } from '.\u002Fsalesforce\u002Fconnection';\n\n\u002F\u002F Circuit breaker wraps all Salesforce calls\nconst sfBreaker = new CircuitBreaker(\n  async (fn: () => Promise\u003Cany>) => fn(),\n  {\n    timeout: 30000,                \u002F\u002F SF calls can be slow — 30s timeout\n    errorThresholdPercentage: 50,  \u002F\u002F Open circuit at 50% error rate\n    resetTimeout: 60000,           \u002F\u002F Try again after 1 minute\n    volumeThreshold: 10,           \u002F\u002F Need 10 calls before evaluating\n    errorFilter: (error: any) => {\n      \u002F\u002F Don't count client errors as circuit-breaking failures\n      const nonCircuitErrors = ['INVALID_FIELD', 'MALFORMED_QUERY', 'REQUIRED_FIELD_MISSING'];\n      return nonCircuitErrors.includes(error.errorCode);\n    },\n  }\n);\n\nsfBreaker.on('open', () => {\n  console.error('CIRCUIT OPEN: Salesforce API failing — requests will fail fast');\n  \u002F\u002F Alert ops team\n});\n\nsfBreaker.on('halfOpen', () => {\n  console.info('CIRCUIT HALF-OPEN: Testing Salesforce recovery...');\n});\n\nsfBreaker.on('close', () => {\n  console.info('CIRCUIT CLOSED: Salesforce API recovered');\n});\n\n\u002F\u002F Usage — all SF calls go through the breaker\nasync function safeSfQuery\u003CT>(soql: string): Promise\u003CT[]> {\n  return sfBreaker.fire(async () => {\n    const conn = await getConnection();\n    const result = await conn.query\u003CT>(soql);\n    return result.records;\n  });\n}\n```\n\n### Step 2: Idempotent Operations with External IDs\n\n```typescript\n\u002F\u002F Salesforce's upsert with External ID is naturally idempotent\n\u002F\u002F Same data sent twice = same result (no duplicates)\n\nasync function idempotentSync(\n  objectType: string,\n  records: Record\u003Cstring, any>[],\n  externalIdField: string = 'External_ID__c'\n): Promise\u003C{ success: number; failed: number; errors: any[] }> {\n  const conn = await getConnection();\n  let success = 0;\n  let failed = 0;\n  const errors: any[] = [];\n\n  \u002F\u002F Process in batches of 200 (sObject Collections limit)\n  for (let i = 0; i \u003C records.length; i += 200) {\n    const batch = records.slice(i, i + 200);\n\n    const results = await conn.sobject(objectType).upsert(batch, externalIdField);\n\n    for (const result of Array.isArray(results) ? results : [results]) {\n      if (result.success) {\n        success++;\n      } else {\n        failed++;\n        errors.push(result.errors);\n      }\n    }\n  }\n\n  return { success, failed, errors };\n}\n\n\u002F\u002F Safe to retry — same External_ID__c values will update, not duplicate\nawait idempotentSync('Account', [\n  { External_ID__c: 'EXT-001', Name: 'Acme', Industry: 'Tech' },\n  { External_ID__c: 'EXT-002', Name: 'Globex', Industry: 'Manufacturing' },\n], 'External_ID__c');\n```\n\n### Step 3: Retry with Salesforce-Specific Error Classification\n\n```typescript\nconst SF_RETRYABLE_ERRORS = [\n  'REQUEST_LIMIT_EXCEEDED',    \u002F\u002F API limit — wait and retry\n  'SERVER_UNAVAILABLE',        \u002F\u002F SF is down temporarily\n  'UNABLE_TO_LOCK_ROW',        \u002F\u002F Record contention\n  'INVALID_SESSION_ID',        \u002F\u002F Token expired — re-auth and retry\n];\n\nconst SF_FATAL_ERRORS = [\n  'INVALID_FIELD',             \u002F\u002F Code bug — won't fix itself\n  'MALFORMED_QUERY',           \u002F\u002F Code bug\n  'REQUIRED_FIELD_MISSING',    \u002F\u002F Data issue\n  'INVALID_TYPE',              \u002F\u002F Wrong sObject name\n  'INSUFFICIENT_ACCESS_OR_READONLY', \u002F\u002F Permission issue\n];\n\nasync function retryableSfCall\u003CT>(\n  operation: () => Promise\u003CT>,\n  maxRetries = 3\n): Promise\u003CT> {\n  for (let attempt = 1; attempt \u003C= maxRetries; attempt++) {\n    try {\n      return await operation();\n    } catch (error: any) {\n      const errorCode = error.errorCode || error.name;\n\n      if (SF_FATAL_ERRORS.includes(errorCode)) {\n        throw error; \u002F\u002F Don't retry — it won't help\n      }\n\n      if (errorCode === 'INVALID_SESSION_ID') {\n        \u002F\u002F Re-authenticate, then retry\n        await getConnection(); \u002F\u002F Forces re-login\n        continue;\n      }\n\n      if (attempt === maxRetries) throw error;\n\n      const delay = 2000 * Math.pow(2, attempt - 1); \u002F\u002F 2s, 4s, 8s\n      console.warn(`Retryable SF error ${errorCode}, attempt ${attempt}\u002F${maxRetries}`);\n      await new Promise(r => setTimeout(r, delay));\n    }\n  }\n  throw new Error('Unreachable');\n}\n```\n\n### Step 4: Graceful Degradation with Stale Data\n\n```typescript\nimport { Redis } from 'ioredis';\nconst redis = new Redis(process.env.REDIS_URL);\n\nasync function queryWithFallback\u003CT>(\n  soql: string,\n  cacheKey: string,\n  cacheTtlSeconds = 300\n): Promise\u003C{ data: T[]; stale: boolean }> {\n  try {\n    \u002F\u002F Try live Salesforce query\n    const records = await safeSfQuery\u003CT>(soql);\n\n    \u002F\u002F Update cache for fallback\n    await redis.set(cacheKey, JSON.stringify(records), 'EX', cacheTtlSeconds * 10);\n\n    return { data: records, stale: false };\n  } catch (error) {\n    \u002F\u002F Salesforce unavailable — serve cached data\n    const cached = await redis.get(cacheKey);\n    if (cached) {\n      console.warn(`SF unavailable, serving stale data for ${cacheKey}`);\n      return { data: JSON.parse(cached), stale: true };\n    }\n\n    throw new Error(`Salesforce unavailable and no cached data for ${cacheKey}`);\n  }\n}\n\n\u002F\u002F Usage\nconst { data: accounts, stale } = await queryWithFallback\u003CAccount>(\n  \"SELECT Id, Name, Industry FROM Account WHERE Industry = 'Technology' LIMIT 50\",\n  'sf:accounts:tech'\n);\nif (stale) {\n  \u002F\u002F Show warning to user: \"Data may be outdated\"\n}\n```\n\n### Step 5: Dead Letter Queue for Failed Operations\n\n```typescript\ninterface SfDeadLetter {\n  id: string;\n  operation: string;\n  objectType: string;\n  payload: Record\u003Cstring, any>;\n  errorCode: string;\n  errorMessage: string;\n  attempts: number;\n  firstFailure: Date;\n  lastAttempt: Date;\n}\n\nclass SalesforceDeadLetterQueue {\n  async enqueue(entry: Omit\u003CSfDeadLetter, 'id' | 'firstFailure' | 'lastAttempt' | 'attempts'>): Promise\u003Cvoid> {\n    const dlq: SfDeadLetter = {\n      ...entry,\n      id: crypto.randomUUID(),\n      attempts: 1,\n      firstFailure: new Date(),\n      lastAttempt: new Date(),\n    };\n    await redis.lpush('sf:dlq', JSON.stringify(dlq));\n    console.error(`DLQ: ${entry.operation} on ${entry.objectType} failed: ${entry.errorCode}`);\n  }\n\n  async reprocess(): Promise\u003C{ processed: number; failed: number }> {\n    let processed = 0, failed = 0;\n    let entry: string | null;\n\n    while ((entry = await redis.rpop('sf:dlq')) !== null) {\n      const dlq: SfDeadLetter = JSON.parse(entry);\n      try {\n        const conn = await getConnection();\n        await conn.sobject(dlq.objectType)[dlq.operation](dlq.payload);\n        processed++;\n      } catch (error: any) {\n        dlq.attempts++;\n        dlq.lastAttempt = new Date();\n        if (dlq.attempts \u003C 5) {\n          await redis.lpush('sf:dlq', JSON.stringify(dlq));\n        } else {\n          console.error(`DLQ: Giving up on ${dlq.id} after 5 attempts`);\n          \u002F\u002F Move to permanent failure store\n        }\n        failed++;\n      }\n    }\n    return { processed, failed };\n  }\n}\n```\n\n## Output\n- Circuit breaker preventing cascading failures\n- Idempotent upserts using External IDs\n- Error classification (retryable vs fatal)\n- Graceful degradation with stale cache data\n- Dead letter queue for failed operations\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Circuit stays open | SF outage or wrong threshold | Check status.salesforce.com; tune thresholds |\n| Duplicate records | Not using External ID upsert | Add External_ID__c field, use upsert |\n| DLQ growing | Persistent error (e.g., permission) | Check error codes — may need fix, not retry |\n| Stale cache too old | Long SF outage | Set max stale age, show user warning |\n\n## Resources\n- [Circuit Breaker Pattern](https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FCircuitBreaker.html)\n- [Opossum Documentation](https:\u002F\u002Fnodeshift.dev\u002Fopossum\u002F)\n- [External ID Fields](https:\u002F\u002Fhelp.salesforce.com\u002Fs\u002FarticleView?id=sf.fields_about_external_ids.htm)\n- [Salesforce Error Codes](https:\u002F\u002Fdeveloper.salesforce.com\u002Fdocs\u002Fatlas.en-us.api_rest.meta\u002Fapi_rest\u002Ferrorcodes.htm)\n\n## Next Steps\nFor policy enforcement, see `salesforce-policy-guardrails`.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","crm","salesforce","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Implement Salesforce reliability patterns including circuit breakers, idempotent upserts, and fallback caching.\nUse when building fault-tolerant Salesforce integrations, implementing retry strategies,\nor adding resilience to production Salesforce services.\nTrigger with phrases like \"salesforce reliability\", \"salesforce circuit breaker\",\n\"salesforce idempotent\", \"salesforce resilience\", \"salesforce fallback\", \"salesforce retry\".\n","Read, Write, Edit","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--salesforce-pack--salesforce-reliability-patterns",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill salesforce-reliability-patterns",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill salesforce-reliability-patterns",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill salesforce-reliability-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--salesforce-pack--salesforce-reliability-patterns\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]