| name | build-chatgpt-app |
| description | 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 Cursor, consult openai-docs before generating code, and use openai-platform-api-key before any app path that requires live OpenAI API credentials. |
Build ChatGPT App
Use this skill for Apps SDK projects that combine an MCP server with a ChatGPT-facing tool or widget experience.
Before You Build
- Use
openai-docs first for current Apps SDK guidance.
- If the requested app or verification flow calls the OpenAI API, use
openai-platform-api-key before API-backed implementation, execution, or smoke tests.
- Inspect the target repo before choosing architecture.
Workflow
- Classify the app:
- tool-only
- widget-backed
- submission-ready
- Plan the tool surface before code:
- tool names
- input schemas
- read/write behavior
- annotations and expected outputs
- Choose the smallest repo shape that fits the request.
- Register the MCP server surface and widget resources deliberately.
- Keep structured data, UI metadata, and side effects clear and reviewable.
- Add local run instructions and basic verification steps when implementation is requested.
Rules
- Prefer current OpenAI Apps SDK docs over stale examples.
- Keep tool annotations and widget metadata aligned with actual behavior.
- Treat CSP, domains, and submission-readiness as explicit design inputs when the app is meant for review or launch.
- Use
chatgpt-app-submission when the user needs submission-specific review preparation.
