agentleFS
Sign inStart free
hideki5123hideki5123/agent-skill-set/openai-cli/SKILL.md

openai-cli

Skill2 starsChanged 4 months agoNo licenceView on GitHub

Call the OpenAI Platform API from the terminal via TypeScript on deno — chat completions, Responses API, reasoning (o-series), embeddings, image generation, audio (Whisper transcription, TTS), files, batches, moderation, and model listing. Two-tool stack: mise + deno (no node_modules, no pnpm, no bash). Models are resolved dynamically per session against `client.models.list()` — never hardcoded — and any detected upgrade prompts the user via AskUserQuestion (even in auto-mode). Secrets stay outside the agent: existence-only key checks, scoped `--allow-env=OPENAI_API_KEY` and `--allow-net=api.openai.com` flags, no `.env` files. Scoped to the Platform API specifically — for open-ended chat/conversation ("ask gpt", "chat with gpt") prefer the codex-server skill instead, which uses the user's ChatGPT subscription rather than API-key billing. Use this skill only when the request is explicitly about the Platform API surface (embeddings, image generation, audio, moderation, batches, files, or a chat/Responses call made programmatically as part of a script or pipeline). Trigger patterns (match any variation): openai api / openai platform api / open-ai api / embeddings / dall-e / gpt-image / image generation / generate image / whisper / transcribe audio / speech-to-text / tts / text-to-speech / read aloud / moderation / content moderation / openai cli / openai-cli / call openai api / use openai api / openai chat completions api / openai responses api / responses api / openai batch / openai files / openai embeddings api. Does NOT access ChatGPT chat history (the API does not expose it; use the Settings → Data Controls export instead). Does NOT handle open-ended chat/conversation requests — see codex-server for that.

  • Pipes a download into a shell
  • Reads credentials
  • Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 3 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.

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