PRACTICAL FIELD NOTES / 18 OCTOBER 2026
Set up Claude, ChatGPT and Codex skills
Use the installation route for your actual product. Keep supporting files and check tool access.
Skills, plugins and prompts have different jobs
A skill packages reusable instructions and may include references or scripts. A plugin can bundle skills with tools and other capabilities. A starter prompt asks for a particular run. Copying a prompt does not install a plugin or grant app access.
Use the source-specific setup notes on each listing. The current product guides are Claude’s plugin guide and OpenAI’s skills overview.
Claude: keep the complete pack
For a publisher-maintained plugin, follow its current marketplace instructions in a supported Claude surface. For a folder-based skill in Claude Code, preserve the complete folder structure and supporting references. Do not overwrite a customised local copy without preserving it first.
Check whether the source’s local scripts, hooks or connected apps are available in your chosen product. A workflow intended for a local runtime may need adaptation in a browser chat.
ChatGPT: read the exact compatibility label
Some listings document a manual instruction protocol for ChatGPT or a custom GPT. Others offer Fieldwork’s prompt adaptation of an instruction-led skill. Neither label claims that a Claude or Codex plugin installs natively into ChatGPT.
Supply the relevant protocol and permitted reference material, describe the tools available in your account, and ask for a draft. If the workflow requires a local script, live connector or packaged tool that is unavailable, stop at the supported part. Check your account and workspace controls against the current product documentation.
Codex: use current publisher sources
The current OpenAI plugin examples live in openai/plugins. The older openai/skills repository identifies itself as deprecated. Fieldwork points new OpenAI listings at the current source and records its revision.
Install through the publisher-supported plugin or skill route, then verify credentials, local dependencies and app permissions. A paid app or API is a separate requirement from the public instruction file.