Agent skill · software engineering · openai
chatgpt-apps
Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.
Why this skill is useful
Adds a comprehensive scaffold generation process for ChatGPT Apps SDK applications, including executable templates and integration patterns not found in public documentation.
What it needs
Requires node installed locally. Requires openai account access. About 11k tokens when loaded. Last updated 2026-07-14. 24,594 stars on the source repository.
What this skill does
ChatGPT Apps Overview Scaffold ChatGPT Apps SDK implementations with a docs-first, example-first workflow, then generate code that follows current Apps SDK and MCP Apps bridge patterns. Use this skill to produce: A primary app-archetype classification and repo-shape decision A tool plan (names, schemas, annotations, outputs) An upstream starting-point recommendation (official example, ext-apps example, or local fallback scaffold) An MCP server scaffold (resource registration, tool handlers, metadata) A widget scaffold (MCP Apps bridge first, window.openai compatibility/extensions second) A reusable Node + @modelcontextprotocol/ext-apps starter scaffold for low-dependency fallbacks A validation report against the minimum working repo contract Local dev and connector setup steps A short stakeholder summary of what the app does (when requested) Mandatory Docs-First Workflow Use $openai-docs first whenever building or changing a ChatGPT Apps SDK app. 1. Invoke $openai-docs (preferred) or call the OpenAI docs MCP server directly. 2. Fetch current Apps SDK docs before writing code, especially (baseline pages): apps-sdk/build/mcp-server apps-sdk/build/chatgpt-ui apps-sdk/build/examples apps-sdk/plan/tools apps-sdk/reference 3. Fetch apps-sdk/quickstart when scaffolding a new app or generating a first-pass implementation, and check the official examples repo/page before inventing a scaffold from scratch. 4. Fetch deployment/submission docs when the task includes local ChatGPT testing, hosting, or public launch: apps-sdk/deploy apps-sdk/deploy/submission apps-sdk/app-submission-guidelines 5. Cite the docs URLs you used when explaining design choices or generated scaffolds. 6. Prefer current docs guidance over older repo patterns when they differ, and call out compatibility aliases explicitly. 7. If doc search times out or returns poor matches, fetch the canonical Apps SDK pages directly by URL and continue; do not let search failure block scaffolding. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills openai/chatgpt-apps