Automated summary
This skill provides reliability patterns for Replit integrations, including circuit breakers, idempotency keys, bulkheads, and graceful degradation.
Strengths
- Offers concrete TypeScript examples using opossum and p-queue libraries
- Covers multiple complementary patterns: circuit breaker, idempotency, bulkhead, timeout hierarchy
- Includes circuit breaker event handling (open, halfOpen, close) with alerting
- Addresses graceful degradation with fallback data and staleness levels
Limitations
- Assumes prerequisites already exist: DLQ queue and caching layer
- The code is partial (the graceful degradation example is truncated)
- Does not detail Replit-specific API or SDK integration
Use when you want to make a Replit integration fault-tolerant with circuit breakers and idempotency.
Avoid if you lack queue or cache infrastructure, or if you need patterns without TypeScript code.
Security analysis
SafeThe skill is purely instructional reference material consisting of TypeScript code examples for resilience patterns (circuit breakers, idempotency, bulkheads, timeouts, DLQ, health checks). It declares only Read/Write/Edit and contains no shell execution, network calls, credential access, obfuscated payloads, or destructive operations. There is no meaningful execution risk in listing it.
No concerns found
How this analysis is madeExamples
Add a circuit breaker around our Replit API calls using opossum so failing requests fail fast, with alerts when the circuit opens.Implement deterministic idempotency keys for our Replit payment operations so retries don't create duplicates.Add graceful degradation to our Replit integration so that when the service is down we serve cached fallback data and mark it as stale.name: replit-reliability-patterns description: | Implement Replit reliability patterns including circuit breakers, idempotency, and graceful degradation. Use when building fault-tolerant Replit integrations, implementing retry strategies, or adding resilience to production Replit services. Trigger with phrases like "replit reliability", "replit circuit breaker", "replit idempotent", "replit resilience", "replit fallback", "replit bulkhead". allowed-tools: Read, Write, Edit version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io
Replit Reliability Patterns
Overview
Production-grade reliability patterns for Replit integrations.
Prerequisites
- Understanding of circuit breaker pattern
- opossum or similar library installed
- Queue infrastructure for DLQ
- Caching layer for fallbacks
Circuit Breaker
import CircuitBreaker from 'opossum';
const replitBreaker = new CircuitBreaker(
async (operation: () => Promise<any>) => operation(),
{
timeout: 30000,
errorThresholdPercentage: 50,
resetTimeout: 30000,
volumeThreshold: 10,
}
);
// Events
replitBreaker.on('open', () => {
console.warn('Replit circuit OPEN - requests failing fast');
alertOps('Replit circuit breaker opened');
});
replitBreaker.on('halfOpen', () => {
console.info('Replit circuit HALF-OPEN - testing recovery');
});
replitBreaker.on('close', () => {
console.info('Replit circuit CLOSED - normal operation');
});
// Usage
async function safeReplitCall<T>(fn: () => Promise<T>): Promise<T> {
return replitBreaker.fire(fn);
}
Idempotency Keys
import { v4 as uuidv4 } from 'uuid';
import crypto from 'crypto';
// Generate deterministic idempotency key from input
function generateIdempotencyKey(
operation: string,
params: Record<string, any>
): string {
const data = JSON.stringify({ operation, params });
return crypto.createHash('sha256').update(data).digest('hex');
}
// Or use random key with storage
class IdempotencyManager {
private store: Map<string, { key: string; expiresAt: Date }> = new Map();
getOrCreate(operationId: string): string {
const existing = this.store.get(operationId);
if (existing && existing.expiresAt > new Date()) {
return existing.key;
}
const key = uuidv4();
this.store.set(operationId, {
key,
expiresAt: new Date(Date.now() + 24 * 60 * 60 * 1000),
});
return key;
}
}
Bulkhead Pattern
import PQueue from 'p-queue';
// Separate queues for different operations
const replitQueues = {
critical: new PQueue({ concurrency: 10 }),
normal: new PQueue({ concurrency: 5 }),
bulk: new PQueue({ concurrency: 2 }),
};
async function prioritizedReplitCall<T>(
priority: 'critical' | 'normal' | 'bulk',
fn: () => Promise<T>
): Promise<T> {
return replitQueues[priority].add(fn);
}
// Usage
await prioritizedReplitCall('critical', () =>
replitClient.processPayment(order)
);
await prioritizedReplitCall('bulk', () =>
replitClient.syncCatalog(products)
);
Timeout Hierarchy
const TIMEOUT_CONFIG = {
connect: 5000, // Initial connection
request: 30000, // Standard requests
upload: 120000, // File uploads
longPoll: 300000, // Webhook long-polling
};
async function timedoutReplitCall<T>(
operation: 'connect' | 'request' | 'upload' | 'longPoll',
fn: () => Promise<T>
): Promise<T> {
const timeout = TIMEOUT_CONFIG[operation];
return Promise.race([
fn(),
new Promise<never>((_, reject) =>
setTimeout(() => reject(new Error(`Replit ${operation} timeout`)), timeout)
),
]);
}
Graceful Degradation
interface ReplitFallback {
enabled: boolean;
data: any;
staleness: 'fresh' | 'stale' | 'very_stale';
}
async function withReplitFallback<T>(
fn: () => Promise<T>,
fallbackFn: () => Promise<T>
): Promise<{ data: T; fallback: boolean }> {
try {
const data = await fn();
// Update cache for future fallback
await updateFallbackCache(data);
return { data, fallback: false };
} catch (error) {
console.warn('Replit failed, using fallback:', error.message);
const data = await fallbackFn();
return { data, fallback: true };
}
}
Dead Letter Queue
interface DeadLetterEntry {
id: string;
operation: string;
payload: any;
error: string;
attempts: number;
lastAttempt: Date;
}
class ReplitDeadLetterQueue {
private queue: DeadLetterEntry[] = [];
add(entry: Omit<DeadLetterEntry, 'id' | 'lastAttempt'>): void {
this.queue.push({
...entry,
id: uuidv4(),
lastAttempt: new Date(),
});
}
async processOne(): Promise<boolean> {
const entry = this.queue.shift();
if (!entry) return false;
try {
await replitClient[entry.operation](entry.payload);
console.log(`DLQ: Successfully reprocessed ${entry.id}`);
return true;
} catch (error) {
entry.attempts++;
entry.lastAttempt = new Date();
if (entry.attempts < 5) {
this.queue.push(entry);
} else {
console.error(`DLQ: Giving up on ${entry.id} after 5 attempts`);
await alertOnPermanentFailure(entry);
}
return false;
}
}
}
Health Check with Degraded State
type HealthStatus = 'healthy' | 'degraded' | 'unhealthy';
async function replitHealthCheck(): Promise<{
status: HealthStatus;
details: Record<string, any>;
}> {
const checks = {
api: await checkApiConnectivity(),
circuitBreaker: replitBreaker.stats(),
dlqSize: deadLetterQueue.size(),
};
const status: HealthStatus =
!checks.api.connected ? 'unhealthy' :
checks.circuitBreaker.state === 'open' ? 'degraded' :
checks.dlqSize > 100 ? 'degraded' :
'healthy';
return { status, details: checks };
}
Instructions
Step 1: Implement Circuit Breaker
Wrap Replit calls with circuit breaker.
Step 2: Add Idempotency Keys
Generate deterministic keys for operations.
Step 3: Configure Bulkheads
Separate queues for different priorities.
Step 4: Set Up Dead Letter Queue
Handle permanent failures gracefully.
Output
- Circuit breaker protecting Replit calls
- Idempotency preventing duplicates
- Bulkhead isolation implemented
- DLQ for failed operations
Error Handling
| Issue | Cause | Solution | |-------|-------|----------| | Circuit stays open | Threshold too low | Adjust error percentage | | Duplicate operations | Missing idempotency | Add idempotency key | | Queue full | Rate too high | Increase concurrency | | DLQ growing | Persistent failures | Investigate root cause |
Examples
Quick Circuit Check
const state = replitBreaker.stats().state;
console.log('Replit circuit:', state);
Resources
Next Steps
For policy enforcement, see replit-policy-guardrails.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/replit-reliability-patterns-ms1aw58x' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/replit-reliability-patterns-ms1aw58x/download' --output '.skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md.part' && mv '.skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md.part' '.skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit
Original excerpt: Prerequisites
- Understanding of circuit breaker pattern
- opossum or similar library installed
- Queue infrastructure for DLQ
- Caching layer for fallbacks
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md' && test -s '.skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/replit-reliability-patterns' && cp -R '.skill-downloads/replit-reliability-patterns-ms1aw58x' '.claude/skills/replit-reliability-patterns'Cursor
test -f '.skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md' && test -s '.skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/replit-reliability-patterns' && cp -R '.skill-downloads/replit-reliability-patterns-ms1aw58x' '.cursor/skills/replit-reliability-patterns'Codex
test -f '.skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md' && test -s '.skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/replit-reliability-patterns' && cp -R '.skill-downloads/replit-reliability-patterns-ms1aw58x' '.agents/skills/replit-reliability-patterns'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/replit-reliability-patterns-ms1aw58x'openskills read 'replit-reliability-patterns-ms1aw58x'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/replit-reliability-patterns-ms1aw58x/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.