agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/amplifier-bundle-work/skills/openai-docs/SKILL.md

openai-docs

Skill0 starsChanged 27 days agoMITView on GitHub

Research OpenAI APIs, models, and product behavior using current official documentation. Use for OpenAI integration or product questions, not Amplifier self-knowledge.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use mounted search/fetch tools or an authorized documentation connector to find the user's specific topic on official OpenAI sources.

    line 10
  2. Very specific:

    If no fetch tool is mounted but an authorized process tool has network access, retrieve a known official HTTPS page with curl or Python's …

    line 15
  3. Distinctive:

    Check status and final URL, retain the supporting response for inspection, and verify redirects remain on an official documentation domain.

    line 17
  4. Distinctive:

    Check changing details such as models, prices, limits, and supported parameters against current pages.

    line 22
  5. Distinctive:

    When the user says "this app" inside Amplifier, inspect Amplifier's own contracts.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenAI documentation

Use mounted search/fetch tools or an authorized documentation connector to find the user's specific topic on official OpenAI sources. Fetch the supporting page, not only its search snippet. Prefer developers.openai.com and platform.openai.com for APIs; use the product's official documentation for ChatGPT and Codex.

If no fetch tool is mounted but an authorized process tool has network access, retrieve a known official HTTPS page with curl or Python's urllib.request. Check status and final URL, retain the supporting response for inspection, and verify redirects remain on an official documentation domain. This provides direct retrieval, not a search engine or an authenticated product connector.

Preserve explicitly requested models, endpoint versions, and product context. Check changing details such as models, prices, limits, and supported parameters against current pages. Keep citations adjacent to the claims they support. Distinguish documented behavior from inference and runtime observations. If the source cannot be fetched, state the limit rather than supplying invented links or calling stale knowledge current.

For implementation, inspect the actual SDK and host integration. Keep API keys in the host's authorized secret configuration. Do not treat Codex-only tools, ChatGPT product features, or subscription benefits as public API capabilities. When the user says "this app" inside Amplifier, inspect Amplifier's own contracts; this skill does not redefine the current host as Codex.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free