| name | chatgpt-app-submission |
| description | 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. |
ChatGPT App Submission
Use this skill when a developer needs a chatgpt-app-submission.json file for a ChatGPT Apps submission. The file is uploaded in the Apps submission form to fill out parts of App Info, MCP Server, and Testing.
Workflow
- Inspect the MCP server codebase from the current working directory.
- Read repo metadata, package metadata, README files, app manifests, tool descriptors, resource templates, and widget metadata needed to understand the app.
- Find every exposed MCP tool, its declared
readOnlyHint, openWorldHint, and destructiveHint annotations, and whether it declares outputSchema.
- Read each tool implementation and any called helper functions needed to understand side effects.
- Compare tool annotations, tool names, tool descriptions, and CSP values against actual behavior. If any value is missing, stale, misleading, or inconsistent, ask the developer for approval before updating source.
- Generate concise review-facing app info suggestions, tool hint justifications, positive test cases, and negative test cases.
- Write
chatgpt-app-submission.json in the current working directory.
- Print review-check findings and any missing
outputSchema warnings in the final response, and explain what the developer should do with each finding before submission.
Do not infer behavior from the tool name alone. Use the real tool implementation and declared annotations. If a tool calls into another module or API client, inspect enough of that path to know whether it reads, writes, deletes, sends, publishes, or changes external state.
App Info Rules
Suggest app info from source-of-truth project metadata and the tool behavior you inspected. Keep it plain-language and submission-review-facing.
display_name: use the product or app name from repo metadata, package metadata, README, manifest, or existing configuration. Keep it short enough for the submission form.subtitle: summarize what the app does in one short functional phrase, not marketing copy. It must be 30 characters or less.description: describe concrete user value and the main workflows the tools support.category: choose one of BUSINESS, COLLABORATION, DESIGN, DEVELOPER_TOOLS, EDUCATION, ENTERTAINMENT, FINANCE, FOOD, LIFESTYLE, NEWS, PRODUCTIVITY, SHOPPING, or TRAVEL.
Hint Rules
Use the Apps SDK review meanings:
readOnlyHint: true only when the tool strictly fetches, looks up, lists, retrieves, or computes data without changing state. false if it can create, update, delete, send, enqueue, run jobs, write logs, start workflows, or otherwise mutate state.destructiveHint: true if the tool can delete, overwrite, send irreversible messages or transactions, revoke access, or perform destructive admin actions, including via some modes or parameters. Otherwise false.openWorldHint: true if the tool can change publicly visible internet state or external third-party systems, such as sending emails or messages, posting/publishing content, creating public tickets/issues, pushing code/content, or submitting external forms. false if it only operates in closed/private systems.
ChatGPT Apps submissions require every tool to set all three hints explicitly. Missing or null hints are submission blockers, even if MCP clients may have protocol-level defaults.
If a hint is missing, null, or behaviorally wrong, stop before writing the JSON and ask the developer for approval to update source. List each affected tool, the current or missing hint, the behavior you observed, and the recommended explicit value. If approval arrives, make the smallest source change and continue; otherwise report the blocked mismatch instead of generating misleading JSON.
Output Schema Warnings
While inspecting exposed MCP tools, record each tool whose descriptor or source definition omits outputSchema or sets it to null. Missing outputSchema is not a blocker for generating chatgpt-app-submission.json, and the submission JSON does not include output schemas.
Do not infer or invent output schemas for this warning. Use the actual MCP tool descriptor or source definition. In the final response, include a concise warning for any missing tools: Add an outputSchema so models can use this tool's results more reliably. See https://modelcontextprotocol.io/specification/draft/server/tools#tool. Include the affected tool names. If every tool declares outputSchema, do not include an outputSchema warning.
Tool Descriptor and CSP Rules
Check tool names, tool descriptions, and widget CSP metadata while inspecting the app.
- Tool input schemas should not solicit sensitive data unless that data is strictly necessary for the app's stated user-facing workflow. Flag fields that ask for PHI, PCI, SSNs, credentials, MFA codes, government IDs, biometrics, or similarly sensitive identifiers.
- Tool names should match the action the tool performs and should not imply capabilities the implementation does not provide.
- Tool descriptions should accurately describe inputs, side effects, and user-visible results.
- CSP values should be as narrow as the implementation supports. Flag wildcard domains, unused domains, broad resource/connect domains, and missing domains required by actual widget behavior.
If tool names, descriptions, or CSP values are missing or inconsistent with behavior, ask for approval before editing source. If approval does not arrive or the edit is ambiguous, keep the JSON truthful and report the finding.
Test Case Rules
Generate exactly five positive test cases and exactly three negative test cases.
- Positive test cases must use exact MCP action names in
tools_triggered.
- Positive prompts should cover the main tool-backed workflows and edge conditions that review should exercise.
- Negative test cases should describe prompts where the app should not trigger, including nearby-but-out-of-scope requests.
- Keep expected outputs review-facing and concise. Do not include secrets, credentials, source snippets, local paths, request IDs, stack traces, or private implementation details.
Output Contract
Write exactly one JSON file named chatgpt-app-submission.json:
{
"$schema": "https://developers.openai.com/apps-sdk/schemas/chatgpt-app-submission.v1.json",
"schema_version": 1,
"app_info": {
"display_name": "Example App",
"subtitle": "Find and update records",
"description": "Example App helps users find records, inspect details, and update workspace data through ChatGPT.",
"category": "PRODUCTIVITY"
},
"tools": {
"tool_name": {
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
},
"justifications"
$schema identifies the import file shape for editors and importers; Cursor does not need to fetch it. tools is required. app_info, test_cases, and negative_test_cases are optional in the schema, but generate them whenever the repo contains enough information. Do not include review-check findings in this JSON file.
Writing Justifications
- Keep each justification to one sentence and describe actual behavior, not the annotation name.
- For write tools, state what system changes and whether the change is bounded/private or public/external.
- For destructive tools, name the irreversible action and mention a safeguard only when one really exists.
- Exclude source snippets, secrets, tokens, request IDs, local paths, stack traces, and private implementation details.
Reporting Review Checks
Report these checks in the final response after writing chatgpt-app-submission.json. Do not write them into the JSON file.
- Sensitive data solicitation: flag tool input schema fields that request PHI, PCI, SSNs, credentials, MFA codes, government IDs, biometrics, or similarly sensitive identifiers. Include the tool name and input field in the finding.
- Tool data use: flag tools that collect, expose, mutate, or transmit sensitive data in a way the descriptor or tests do not clearly explain.
- Tool naming: flag names or descriptions that are too vague, misleading, overbroad, or inconsistent with implementation behavior.
- Weak CSPs: flag broad, wildcard, unused, or missing CSP domains in widget metadata.
For each finding, explain the practical next step: update source, update submission copy, narrow CSP, remove or justify a sensitive input, or manually review before submitting. If there are no findings, say that these checks did not find obvious issues from source inspection.
Final Response
After writing the file, summarize the app info fields generated, number of tools covered, positive test case count, and negative test case count. Then include a Review findings section with any sensitive data solicitation, tool data use, tool naming, weak CSP findings, or missing outputSchema warnings and what to do with each one. If generation is blocked, lead with the exact missing hints or source ambiguity.
