$ ~/registry/skill/openai-curated-chatgpt-apps

SKILL

chatgpt-apps

Name: chatgpt-apps
Author: OpenAI

Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications.

Stars

★ 23,132

Source

GitHub

Updated

2026-07-15

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 22.0k

Summary

This appears to be an open-source, prompt-oriented skill focused on documentation-guided scaffolding, with no built-in secrets, remote egress, or local execution indicated in the materials. Given the public GitHub source and strong community adoption, overall risk is low, with minor caution only around downstream code it may help generate.

CredentialsLow risk

The materials explicitly state there are no required secrets or environment variables, and the README does not require API tokens or account credentials; no direct credential collection, storage, or abuse path is evident.

Network egressLow risk

The system checks indicate no remote endpoints, and the skill is classified as prompt-only; while the docs mention optionally consulting OpenAI docs skills/MCP docs tools, there is no indication that this skill itself sends user data to undeclared third-party endpoints.

Code executionLow risk

Based on the description, its role is planning, scaffolding, and code-generation guidance; there is no evidence that the skill itself launches local processes, executes commands, or uses privileged system capabilities.

Data accessLow risk

No filesystem, database, browser, or other local resource access is declared; as a prompt-oriented skill, its visible data scope appears limited to user-provided context, with no signs of excessive authorization.

Supply chainLow risk

The source is an OpenAI GitHub repository, marked open-source, with strong community adoption (~22k stars), all of which materially reduce risk. Although the license and maintenance status are not explicitly stated, the auditable source and high-trust origin place it closer to low risk than to any supply-chain red flag.

Recommendations

Treat it as a code and architecture suggestion tool; manually review any generated scaffold before use.
If you later integrate MCP servers, widgets, or external dependencies based on its output, separately reassess those added components for network, permission, and dependency risks.
Prefer pinning official doc versions, example commit hashes, or dependency versions to reduce compatibility drift and supply-chain uncertainty.

Audited by: gpt-5.4 · 2026-06-16

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "chatgpt-apps" skill from askskill:
1. Download https://raw.githubusercontent.com/openai/skills/main/skills/.curated/chatgpt-apps/SKILL.md
2. Save it as ~/.claude/skills/chatgpt-apps/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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.

Invoke $openai-docs (preferred) or call the OpenAI docs MCP server directly.
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
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.
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
Cite the docs URLs you used when explaining design choices or generated scaffolds.
Prefer current docs guidance over older repo patterns when they differ, and call out compatibility aliases explicitly.
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.

If $openai-docs is unavailable, use:

mcp__openaiDeveloperDocs__search_openai_docs
mcp__openaiDeveloperDocs__fetch_openai_doc

Read references/apps-sdk-docs-workflow.md for suggested doc queries and a compact checklist. Read references/app-archetypes.md to classify the request into a small number of supported app shapes before choosing examples or scaffolds. Read references/repo-contract-and-validation.md when generating or reviewing a repo so the output stays inside a stable “working app” contract. Read references/search-fetch-standard.md when the app is connector-like, data-only, sync-oriented, or meant to work well with company knowledge or deep research. Read references/upstream-example-workflow.md when starting a greenfield app or when deciding whether to adapt an upstream example or use the local fallback scaffold. Read references/window-openai-patterns.md when the task needs ChatGPT-specific widget behavior or when translating repo examples that use wrapper-specific app.* helpers.

Prompt Guidance

Use prompts that explicitly pair this skill with $openai-docs so the resulting scaffold is grounded in current docs.

Preferred prompt patterns:

Use $chatgpt-apps with $openai-docs to scaffold a ChatGPT app for <use case> with a <TS/Python> MCP server and <React/vanilla> widget.
Use $chatgpt-apps with $openai-docs to adapt the closest official Apps SDK example into a ChatGPT app for <use case>.
Use $chatgpt-apps and $openai-docs to refactor this Apps SDK demo into a production-ready structure with tool annotations, CSP, and URI versioning.
Use $chatgpt-apps with $openai-docs to plan tools first, then generate the MCP server and widget code.

When responding, ask for or infer these inputs before coding:

Use case and primary user flows
Read-only vs mutating tools
Demo vs production target

…

View full docs ↗

—Get→

$ loading_