plugin-structure

Standardize Codex plugin directory layouts with manifest-driven configuration and auto-discovery.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/billydeeii136/black-opps-claude-skill --skill plugin-structure-billydeeii136
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/billydeeii136/black-opps-claude-skill/tree/main/agent-skills/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/billydeeii136/black-opps-claude-skill --skill plugin-structure-billydeeii136

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, jsonschema, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you organize and structure your plugin development in a standardized and maintainable way, ensuring seamless integration with Codex.

Core Features & Use Cases

  • Conventional Directory Layout: Automates the discovery of plugin components using a standardized directory structure.
  • Manifest-Driven Configuration: Defines plugin metadata and configuration in a single .Codex-plugin/plugin.json file.
  • Component-Based Organization: Organizes commands, agents, skills, hooks, and MCP servers into dedicated directories for easy management.
  • Portable Path References: Utilizes ${CLAUDE_PLUGIN_ROOT} for all intra-plugin path references for compatibility across installation methods and operating systems.
  • Auto-Discovery Mechanism: Codex automatically discovers and loads components from designated directories during plugin enablement.
  • Best Practices Documentation: Provides comprehensive guidance on plugin development best practices, including naming conventions, organization, and maintenance.

Quick Start

Set up your plugin directory and create the necessary subdirectories and files as per the provided guidelines. Use the following command to initialize your plugin manifest:

# Create and edit plugin.json
touch .Codex-plugin/plugin.json

Frequently Asked Questions about plugin-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Codex plugin for maintainable enterprise development?

To structure a Codex plugin, use a conventional directory layout that organizes commands, agents, skills, hooks, and MCP servers into dedicated subdirectories, ensuring maintainable and scalable enterprise integration.

What is manifest-driven plugin configuration in Codex?

Manifest-driven plugin configuration defines all plugin metadata and settings in a single .Codex-plugin/plugin.json file, centralizing setup for seamless integration and easy management across the plugin lifecycle.

How does auto-discovery work for Codex plugin components?

Auto-discovery works by having Codex automatically scan and load components from designated standardized directories during plugin enablement, eliminating manual registration and streamlining component organization.

Do I need python and jsonschema to use a standardized plugin directory layout?

Yes, you need python and jsonschema installed in your environment to support the manifest validation and scripts required by this structured plugin framework for Codex integration.

What is the best way to reference intra-plugin paths across different operating systems?

The best way to reference intra-plugin paths is using the portable ${CLAUDE_PLUGIN_ROOT} variable, which ensures compatibility across various installation methods and operating systems without hardcoding directory locations.

Why are my Codex plugin components not loading automatically?

If auto-discovery is not loading components, verify that your files are placed in the correct designated directories and that your plugin manifest .Codex-plugin/plugin.json is properly configured with valid jsonschema.