agentleFS
blas1nblas1n/claude-skills/skills/a-timeout-names-the-waiter-not-the-cause-read-the-other-end/SKILL.md

a-timeout-names-the-waiter-not-the-cause-read-the-other-end

Skill2 starsChanged 58 days agoNo licenceView on GitHub

타임아웃은 기다린 쪽의 경험이지 사건의 원인이 아니다. 보고 홉(worker→backend, client→API, job→queue)이 보내는 쪽에서 응답을 안 보고 받는 쪽에서 거절을 200 으로 돌려주면, 실패한 쓰기가 성공 로그로 세탁된다 — 그리고 한쪽 끝만 읽어 만든 진단표에는 진실이 들어갈 칸이 아예 없다. 두 끝을 같은 타임스탬프로 나란히 읽어라: 모순 자체가 진단이다. 트리거 - '왜 자꾸 타임아웃이지', 재현 안 되는 간헐 행(hang), 같은 증상을 두 번 이상 오진한 이력, 종결되지 않고 쌓이는 in-flight 행.

The file

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.