· ai-devtools
Stop Hardcoding Your Timeouts
A developer rant about tools built for one kind of internet Recently, I’ve been losing my mind to hardcoded timeouts.
Silent, arbitrary, unconfigurable time limits baked into tools by developers who apparently have never had to wait more than 200ms for anything in their lives. Now that coding agents are everywhere, everyone is using skills.
The popular way to add them is through packages developed by vercel-labs, and the go-to collection is awesome-copilot, a curated set of skills sitting at 30K+ stars at the time of writing. The repository is too big, and the npx skills installer just chokes and dies.
There’s an open issue about this since February #278 on the vercel-labs/skills repo and no one has responded. I’d be happy to send a PR and fix it myself.
I just need someone to acknowledge it exists. Clone the repo manually first, then install from the local copy.
Except now skills-lock.json points to a path on my machine. I also have to update my copy everytime I want update my skills.
One workaround creates a lot of other problems. Then came Docker Gordon, the AI-powered debugging assistant baked into Docker. I was stepping through a container build issue, the kind that requires iteration: tweak, rebuild, inspect, repeat.
