- Home
- Skills
- Agents & Orchestration
- Repair Timeout Budget Drift
Works with the AI Agents you already use
Repair Timeout Budget Drift
Align end-to-end request deadlines, retries, cancellation, database work, and side-effect ownership so server work stops when its budget is gone.
$1
Repair Timeout Budget Drift
Example session with this skill installed
Our checkout API has an 8-second caller deadline. The browser aborts at 8s, the gateway waits 15s, the Node service gives the inventory service 12s per attempt and retries twice, PostgreSQL has no statement timeout, and an email side effect can continue after the HTTP request has already been cancelled. We are seeing requests return 504 while server work continues and later logs show a second retry finishing after the client is gone. Repair the timeout-budget contract in the repository. Propagate cancellation, keep retries inside the supplied 8-second budget, add deterministic tests and observability hooks, and do not deploy or change production infrastructure.
- Read your context and instructions
- Compiled the repair timeout budget
Timeout-budget drift found. The 8-second caller budget is exceeded by downstream attempt limits, retries, uncancelled database work, and detached email work. The repair introduces one absolute deadline, remaining-budget propagation, retry gating, cancellation-aware database handling, durable side-effect handoff, deterministic tests, and timeout reason metrics. Production gateway and provider behavior remain unverified.
Connects securely to your tools. The creator never sees your data.
About this skill
Timeout bugs often come from disagreement between layers rather than one bad constant. A client may give up at 8 seconds while a gateway waits 15, a downstream call gets 12 seconds per attempt, a database query has no request-scoped limit, and detached work continues after cancellation.
Repair Timeout Budget Drift gives an AI coding agent a repository workflow for tracing one end-to-end deadline through HTTP/RPC clients, services, retries, circuit breakers, database wrappers, queues, and child tasks. It repairs remaining-budget propagation, retry gating, structured cancellation, durable side-effect handoff, deterministic fake-clock tests, and timeout observability.
It does not change production infrastructure, invent SLOs, or assume irreversible side effects are safe to cancel or retry.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Repairs repository-level deadline, retry, and cancellation contracts only. It does not change live gateway/load-balancer/database/provider settings, invent SLOs, prove SDK cancellation under production load, or authorize retry/cancellation semantics for irreversible side effects.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Permissions
Install under ~/.openclaw/skills/repair-timeout-budget-drift/SKILL.md for OpenClaw. Use local/disposable fixtures only. Do not provide production credentials, environment secrets, private keys, or customer request payloads.