More screenshots
Works with the AI Agents you already use
Repair Nginx Reverse Proxy WebSocket Idle Close Drift
Find premature WebSocket disconnects caused by reverse proxy timeout layering
$1
Repair Nginx Reverse Proxy WebSocket Idle Close Drift
Example session with this skill installed
A dashboard socket drops every 60 seconds though application heartbeat is configured.
Available sources: Nginx proxy settings, upstream keepalive config (partial excerpts only). Additional evidence requested: WebSocket ping frames, disconnect logs. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.
- Read your context and instructions
- Compiled the repair nginx reverse
Repair Nginx Reverse Proxy WebSocket Idle Close Drift — EVIDENCE-LIMITED REVIEW
Scenario received
A dashboard socket drops every 60 seconds though application heartbeat is configured.
Source register
- S1: Nginx proxy settings — partial extract available.
- S2: upstream keepalive config — partial extract available.
- S3: WebSocket ping frames — NOT PROVIDED; REQUIRED FOR VERIFICATION.
- S4: disconnect logs — NOT PROVIDED; REQUIRED FOR VERIFICATION.
Concrete findings and verification
compare proxy_read_timeout with heartbeat — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
2.
inspect upgrade and connection headers — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
3. isolate intermediary close origin — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
4. design canary keepalive tests — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
Deliverables and review gates
- timeout layer map: DRAFT ONLY; do not infer unsupported outcomes.
- disconnect reproduction notes: DRAFT ONLY; do not infer unsupported outcomes.
- proxy configuration patch: DRAFT ONLY; do not infer unsupported outcomes.
Preliminary conclusion
INCOMPLETE / REVIEW REQUIRED. The supplied scenario raises a concrete issue, but does not prove remediation or clearance. Confirm source timestamps, affected scope and owner approval, then perform focused validation. No external system was accessed or changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair Nginx Reverse Proxy WebSocket Idle Close Drift is a ToolForge Labs Cursor Skill workflow. Find premature WebSocket disconnects caused by reverse proxy timeout layering.
What this skill checks
- compare proxy_read_timeout with heartbeat.
- inspect upgrade and connection headers.
- isolate intermediary close origin.
- design canary keepalive tests.
What to provide
- Nginx proxy settings.
- upstream keepalive config.
- WebSocket ping frames.
- disconnect logs.
Deliverables
- timeout layer map.
- disconnect reproduction notes.
- proxy configuration patch.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions, reports missing inputs, and never claims an unperformed live test, compliance approval, or production change.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Cannot verify inaccessible systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.
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 24 days ago
Permissions
Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.