Plugin Marketplace Publishing - Sharing Skills and Integrations

A repository-local Skill can remain in .agents/skills/. Package related Skills, Apps, and MCP server configuration as a Codex Plugin when other users need an installable workflow.

Choose a coherent distribution unit

docs-maintenance-plugin/
├── plugin manifest
├── skills/
│   ├── docs-content/
│   └── i18n-sync/
├── hooks/
├── app mappings/
└── assets/

A docs maintenance Plugin can combine authoring, locale synchronization, and link validation. Unrelated email or deployment capabilities belong in separate Plugins.

Pre-publication checks

1. Remove tokens, personal paths, and internal URLs.
2. Declare required MCP servers, Apps, and commands.
3. Explain filesystem, network, and external write permissions.
4. Test installation without the author’s local configuration.
5. Document disable and uninstall procedures.

Marketplace Sources

Codex can install Plugins from a Marketplace source such as a project or team repository. Users inspect and install entries through the Codex app directory or CLI /plugins browser.

Expand distribution gradually: local development, small repository testing, workspace sharing, then a community Marketplace. Review permission requests, failure behavior, and external data sharing at each stage.

Versioning and Maintenance

Record the supported Codex version and last verification date because Hooks, Rules, and Plugin formats evolve. Test Skill selection, MCP authentication failure, safe removal, and leftover configuration after uninstall.

This completes the Codex harness path from design and implementation through validation and distribution.

See the references for the external specifications and background sources used on this page.[1][2]

References

1. OpenAI, Codex documentation
2. OpenAI, OpenAI API documentation