Fix My Broken Claude Code & Claude Cowork Setup, Skill Files Not Running, Webhook Errors

Description: I paid a developer to set up Claude Code and Claude Cowork for my SaaS automation system three months ago. On the surface it looked like it worked. Then I started using it daily and things started falling apart — skill files running the wrong logic, webhooks timing out for no obvious reason, Claude Cowork tasks not completing properly, and my n8n workflows getting incomplete data back from the Claude API. I cannot debug this myself and the original developer has gone quiet. Here is what is actually happening: the Claude Cowork skill files are inconsistently executing. Some tasks complete correctly, others return partial results, and a handful just silently fail without any error surfacing in the logs. The webhook server built in Node.js and deployed on Railway is throwing 500 errors on roughly 30% of incoming payloads and I have not been able to isolate the trigger. The Claude API responses are coming back with the right structure in testing but something in how the integration was built is stripping fields before they reach the downstream n8n nodes. The result is that my outreach automation sequences — which were supposed to be running on full AI personalization via Claude — are either sending with blank personalization fields or not sending at all. This is directly costing me conversions every day this stays broken. What I need fixed: A full audit of my existing Claude Code project structure and Claude Cowork skill files to identify everything that is misconfigured, missing, or written in a way that causes intermittent failures. Fix the Node.js webhook server so it handles all incoming payloads correctly, surfaces errors properly, and does not silently drop data — I want proper error handling and logging in place. Diagnose and resolve the Claude API response parsing issue so that downstream n8n nodes receive complete, correctly structured data every time. Rewrite or repair any Claude Cowork skill files that are producing inconsistent output — they need to be deterministic, properly scoped, and tested before you hand them back. Fix the GoHighLevel integration so that Claude outputs correctly populate contact fields, trigger the right workflows, and do not create duplicate records. End to end test of the full pipeline with documented proof that each stage works. A written handover document explaining what was wrong, what was fixed, and what I need to maintain going forward so I am not dependent on a developer for routine changes. What you need to bring: You must have real hands on experience with Claude Code and Claude Cowork in production environments. I will share my Railway logs, the webhook server codebase, and the Cowork skill files — you need to be able to look at these and know within a reasonable amount of time what is wrong. Strong Node.js debugging skills are non-negotiable. Experience with n8n workflow architecture and GoHighLevel data structures is required. Do not apply if your plan is to rebuild everything from scratch to avoid diagnosing the original code. I want this fixed, not replaced. This system being broken is costing me money every single day. I need someone who can begin diagnosing immediately and have a clear fix plan within 48 hours of receiving access. Please start your proposal with the phrase "Fix ready" so I know you read the full post.