openai-docs

Answer OpenAI API questions with cited developer documentation.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/erichugy/agentic.skills --skill openai-docs-erichugy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openai-docs
Source: https://github.com/erichugy/agentic.skills/tree/main/.system/openai-docs
Command: npx skills add https://github.com/erichugy/agentic.skills --skill openai-docs-erichugy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides concise, cited, and up-to-date guidance from official OpenAI developer documentation to help engineers and integrators answer API questions, choose models, and plan safe GPT-5.4 upgrades without relying on stale knowledge or unsupported sources.

Core Features & Use Cases

  • Official-doc-first lookups: Prioritizes the OpenAI developer MCP server for searching and fetching exact doc sections and quotes.
  • Model selection & upgrade guidance: Targets model-selection queries and explicit GPT-5.4 upgrade or prompt-upgrade requests using curated reference files while verifying everything against current docs.
  • Fallback and install workflow: Defines MCP install and escalation steps, restricted web fallback to official OpenAI domains, and precise citation and verification rules for technical recommendations.
  • Use Case: When migrating a chat app to GPT-5.4, use this Skill to identify required prompt changes, recommend a starting reasoning effort, and produce a verification plan with doc citations.

Quick Start

Use the openai-docs skill to find the recommended OpenAI model and exact documentation citations for upgrading a chat integration to GPT-5.4.

Frequently Asked Questions about openai-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade my chat application to GPT-5.4?

To upgrade your chat application to GPT-5.4, identify required prompt changes, set a starting reasoning effort, and generate a verification plan using cited OpenAI developer documentation. This ensures a safe migration by verifying exact API requirements against current docs.

What is the best way to choose an OpenAI model for my API integration?

Choosing an OpenAI model requires querying official developer documentation through the OpenAI MCP server to compare capabilities. You get model-selection guidance verified against current docs, ensuring the chosen model fits your specific API usage and integration needs.

How does the OpenAI MCP server retrieve developer documentation?

The OpenAI MCP server retrieves developer documentation by prioritizing official doc-first lookups, fetching exact sections and quotes. It verifies technical recommendations against referenced helper files and restricts any fallback web searches strictly to official OpenAI domains.

Can I use this approach for prompt migrations across different OpenAI models?

Yes, you can use this approach for prompt migrations by targeting explicit prompt-upgrade requests with curated reference files. It verifies all migration steps and prompt changes against current OpenAI developer documentation to ensure compatibility.

When should I not rely on stale knowledge for OpenAI API usage?

You should not rely on stale knowledge for OpenAI API usage when integrating tools, selecting models, or planning GPT-5.4 upgrades. Instead, use the OpenAI developer MCP tools to fetch cited doc snippets and ensure your code integration follows current official specifications.