agents-sdk
Use when the user wants to build, adapt, run, or evaluate an OpenAI Agents SDK app from Claude Code. Prefer a docs-first workflow and route API credential decisions through openai-platform-api-key before API-backed work.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-03
- Stars
- ★ 44
- Forks
- 16
01 前言 Front Matter
- description
- Use when the user wants to build, adapt, run, or evaluate an OpenAI Agents SDK app from Claude Code. Prefer a docs-first workflow and route API credential decisions through openai-platform-api-key before API-backed work.
03 SKILL.md 正文
Agents SDK
Use this skill to turn an idea or repo into a focused Agents SDK implementation.
Before You Build
- Use
openai-docsto inspect current Agents SDK guidance. - If the work will call the OpenAI API, use
openai-platform-api-keybefore building, running, testing, or debugging the API-backed path. - Inspect the repo's existing language, package manager, entrypoints, and testing style before choosing a structure.
Workflow
- Define the agent contract:
- goal
- user input
- expected output
- tools
- approval or escalation boundaries
- Prefer the smallest runnable implementation first.
- Use tools deliberately and keep side effects narrow.
- Add evals when the user asks for reliability, comparison, or regression coverage.
- Provide a local run command and a concrete smoke result when implementation is requested.
Guidance
- Prefer Python unless the repo or user already points to TypeScript.
- Start with one agent before introducing handoffs or orchestration.
- Keep prompts, tools, tests, and deployment artifacts clearly separated.
- Use
openai-docsagain when current SDK behavior or product guidance is central to the answer.
04 同仓库更多 Skills
openai-platform-api-key
Use when Claude Code is asked to build, run, test, debug, or configure an OpenAI-backed or provider-unspecified AI app, UI, script, CLI, generator, or tool, especially requests phrased only as "using AI" or generators driven by forms/user input; also use for OPENAI_API_KEY or sk-proj setup. Do not gate model or prompt migrations that can proceed with source edits and offline validation. Otherwise treat this as the credential gate: inspect safely, ask reuse-vs-new before API work, guide manual local setup when needed, verify presence, and never expose plaintext.
openai-docs
Use whenever the user asks anything about OpenAI products, APIs, models, or SDKs — including factual lookups, coding requests, latest/current/default model selection, prompting guidance, model upgrades, and citation requests. Invoke before calling any openaiDeveloperDocs MCP tool.
openai-api-troubleshooting
Use when an OpenAI API request fails or the user asks what an error means, including blocked access to api.openai.com, 401 invalid_api_key, missing OPENAI_API_KEY, 429 insufficient_quota, 429 rate_limit_exceeded, or 403 model_not_found. Classify the failure, name the next step, route credential setup to openai-platform-api-key, and current guidance to openai-docs.
chatgpt-app-submission
Use when a developer needs a ChatGPT Apps submission import file from an MCP server. Inspect the implementation, generate chatgpt-app-submission.json with app info, tool-hint justifications, positive and negative test cases, then report review findings and outputSchema warnings.
build-chatgpt-app
Use when the user explicitly wants a ChatGPT App, Apps SDK project, MCP server plus widget UI, ChatGPT-compatible tool UI, or submission/deployment work for that surface. Build, scaffold, refactor, or troubleshoot those projects from Claude Code, consult openai-docs before generating code, and use openai-platform-api-key before any app path that requires live OpenAI API credentials.