OpenAI Dev Kit
Frozen compatibility package. New development and fixes belong in Claudin. Kept temporarily for existing installations pending retirement.
Two focused OpenAI Dev Kit skills plus the official read-only OpenAI documentation MCP. No other installed plugin is required.
- Plugin building:
skills/chatgpt-plugin-builder/SKILL.md, with targeted build references and validation/scaffolding scripts. - OpenAI documentation:
skills/openai-docs/SKILL.md, withreferences/openai-workflows.mdand topic guides for API/Codex, models, MCP Apps and submission. - MCP:
https://developers.openai.com/mcp, streamable HTTP, anonymous read-only documentation access. - Branding: supplied Plugin Builder PNG artwork, reused for the package and both skill icons.
Personal toolkit maintained by travnie. Not an official OpenAI plugin. The MCP reads documentation; it does not run API requests, deploy servers, or submit apps.
Install
- Claude Code:
/plugin install openai-dev-kit --marketplace travnie/twojstar - claude.ai, ChatGPT, Codex: upload the
openai-dev-kitpackage built from this folder (see Package), or install it from the directory listing once published.
Package
From the repository root:
python -m pip install -r plugins/openai-dev-kit/requirements.txt
python plugins/openai-dev-kit/scripts/package_plugin.py /tmp/openai-dev-kit.zip
The source contains portable Agent Plugins 1.0 manifests. Packaging generates
synchronized .codex-plugin/plugin.json and .mcp.json compatibility files.
The archive has one openai-dev-kit/ root and no account-specific IDs.
Private ChatGPT installation
A remote endpoint in mcp.json alone does not prove that ChatGPT imported a
connectable app. Register the official endpoint through developer mode, then
copy its verified connection page or underlying App ID:
python plugins/openai-dev-kit/scripts/package_plugin.py /tmp/openai-dev-kit-private.zip \
--docs-app-id VERIFIED_ID_FROM_CHATGPT
This stages .app.json and matching OpenAI/compatibility declarations. A page ID
plugin_asdk_app_<id> is normalized to the underlying asdk_app_<id>. Keep those
bindings out of repository source. Install the resulting private archive only
after the user confirms that account changes may proceed.
Use OpenAI Dev Kit for both independently activated skills inside one plugin. A separately registered dependency may remain visible as OpenAI Docs MCP. Removing an old connection does not guarantee one directory entry. Avoid naming both the combined package and its connection identically.
For public submission, use the supported With MCP flow and omit .app.json and
all apps declarations. This repository package is not a reviewed public listing.
Validation
python plugins/openai-dev-kit/skills/chatgpt-plugin-builder/scripts/validate_plugin.py plugins/openai-dev-kit
python -m unittest discover -s plugins/openai-dev-kit/tests -v
Both upstream workflows retain their substance and Apache-2.0 licensing. Developer references live in openai-docs; build references and the unique scaffold live in chatgpt-plugin-builder.
The plugin is Apache-2.0, like its sources; the repository's packaging script isn't shipped in the package.
Original supplied archives remain the provenance source. Local validation does
not prove account installation or live MCP discovery; verify those in ChatGPT.