ChatGPT Skills and plugins

These workflows are suitable for a chat-based Skills surface. They do not require your local repository or terminal.

1. Open Plugins → Skills in ChatGPT.
2. Choose Create, then select Upload from your computer.
3. Follow the uploader's accepted-file prompt. ChatGPT scans uploaded Skills before they become available.

Claude and ChatGPT both support Skills, but their public upload documentation does not promise the same archive format. A Claude-formatted ZIP is not presented here as a supported ChatGPT upload.

Codex local skills and Plugins are separate product surfaces. A plugin can include Skills, but a Skill is not automatically a plugin.

Personal Skills are available in supported ChatGPT Business, Enterprise, Healthcare, and Edu workspaces. Enterprise and Edu administrators may need to enable Skills before members can create, upload, or install them.

A skill can be distributed inside a plugin with its instructions and supporting files. For a workflow that uses only supplied context, start with a skill-only package. Add an MCP server when the workflow needs connected data or controlled actions.

The portable package has a root plugin.json and a skills/ directory. Here is a minimal manifest for our decision-doc workflow:

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "slashskills-decision-doc",
  "version": "0.1.0",
  "description": "Write a decision record from supplied context."
}

Place the complete decision-doc package at skills/decision-doc/, keeping SKILL.md and its supporting files together. We built and checked this layout locally; installation and activation in ChatGPT remain untested.

slashskills-decision-doc/
├── plugin.json
├── LICENSE
└── skills/
    └── decision-doc/
        └── SKILL.md

Use our package builder and three-case test fixture ↗ to reproduce the package from the original skill.

Follow OpenAI's packaging and local-testing instructions ↗ to add the package to a local marketplace and test it in a new session. Check direct invocation, an indirect request, and missing evidence before sharing it.

Share an individual Skill with people or groups in your workspace from its Skills menu. Use a local or repository marketplace to test a plugin bundle. Workspace plugin publishing requires an administrator; public directory submission is a separate review process.

A workspace share does not make a package publicly installable. Confirm the recipient's access and test the installed copy before treating it as available to your team.

Packaging guidance checked September 29, 2026. Official skill authoring documentation ↗