plugin-authoring

Plugin authoring starts with scaffolding a new plugin using /plugin-development:init <plugin-name>, which generates the required directory structure, plugin.json manifest, and marketplace.json configuration. This creates a standards-compliant foundation with proper naming conventions and frontmatter requirements ready for customization.

A valid plugin requires plugin.json (core manifest), marketplace.json (marketplace metadata), commands/ and agents/ directories for executables, skills/ for skill definitions, and hooks/ for lifecycle handlers. All must follow naming conventions and path structures validated against official schemas.

Run /plugin-development:validate to audit your plugin.json, marketplace.json, scripts, and directory structure against standards. Validation checks naming conventions, executable permissions, schema compliance, and frontmatter requirements to catch issues before marketplace integration.

Yes. Inspect your plugin with read-only analysis to diagnose manifest files and repository structure, then request a deep audit through the plugin-reviewer for comprehensive recommendations on safety, maintainability, and standards compliance.

Executable scripts in commands/, agents/, and hooks/ must follow best practices for permissions, path conventions, and error handling. The authoring guidance covers script structure, environment assumptions, and integration patterns to ensure safe, maintainable plugin behavior.

Use /plugin-development:init scaffolding to set up new plugins quickly with correct structure and templates. Manual configuration suits extending existing plugins or applying custom marketplace metadata; read-only inspection helps validate your changes before applying edits.