Etl retry backoff simulator
Skill sisodiabhumca/agent-skills/skills/etl-retry-backoff-simulator
Production-Ready Agent Skills : product analytics, growth experiments, CRM, research synthesis, postmortems, data contracts, SaaS spend, compliance, architecture maps, and LLM eval and many more.
npx -y skills add sisodiabhumca/agent-skills --skill etl-retry-backoff-simulatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Simulate retry and exponential backoff strategies against a failure-rate model to estimate expected runtime and cost (vendor-neutral).
SKILL.md
1.5 KB, as published. Nobody here has run it
When to invoke
- You are tuning retries/backoff for ETL jobs, API ingestion, or batch pipelines.
- You need to compare strategies (fixed delay vs exponential + jitter).
- You want a quick estimate of expected runtime, attempts, and wasted work under failure.
Inputs needed
- A JSON config with:
attempts_maxbase_delay_secondsstrategy:fixed,exponential, orexponential_jitterfailure_probabilityper attempt (0..1)work_seconds_per_attempt(time spent before a failure/success)trialsfor Monte Carlo simulation
Workflow
- Validate config.
- Run Monte Carlo simulation across
trials:- For each trial, attempt the job up to
attempts_max. - Each attempt succeeds with probability \(1-p\).
- Add work time each attempt; add delay between failed attempts per strategy.
- For each trial, attempt the job up to
- Compute summary statistics:
- success rate
- expected attempts
- p50/p90 total duration
- expected backoff time
Output format
JSON to stdout:
success_rateexpected_attemptsduration_seconds: p50, p90, meanexpected_backoff_seconds
Guardrails
- Vendor-neutral: does not assume a specific orchestrator or cloud.
- Model is simplified; use for comparative tuning, not precise capacity planning.
Reference code
etl_retry_backoff_simulator.py