Codex openai-sdk-debugging skill for diagnosing response parsing
Investigate Node.js SDK integration issues across configuration, connectivity, availability, and response shapes. Flag unverified causes.
中文Install in Codex
A Codex project using the Node.js OpenAI SDK. The example provides fictional response shapes so parsing can be checked offline.
- Review `.agents/skills/openai-sdk-debugging/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/openai-sdk-debugging/` in your project and save the reviewed file as `.agents/skills/openai-sdk-debugging/SKILL.md`.
- Start Codex from that project's root, then type `$openai-sdk-debugging` and select the matching skill.
Example task
Invoke $openai-sdk-debugging and use these fictional response fixtures to locate a parsing mismatch.
case `two-response-shapes`
Responses fixture `{output_text: "Route ready"}`
Chat Completions fixture `{choices: [{message: {content: "Route ready"}}]}`
legacy parser reads choices onlyWhat to check
Explain that the legacy branch only reads choices. Use `output_text` for Responses and `choices[0].message.content` for Chat Completions. Both fixtures should return `Route ready`.
Original SKILL.md on GitHub · Updated
Frequently asked question
What should I check when a response exists but the interface shows nothing?
Compare the SDK response shape against the endpoint and parser. Check with fictional fixtures first and then verify the real request.