hook-publisher

Publishing hook scripts requires enforcing the correct directory structure, validating duplicates, and generating plugin.json and marketplace.json metadata. This skill automates that process by taking a source hook directory and producing a structured, portable plugin package.

To prevent duplicate hook registrations, the publishing process validates the hook's repository layout against existing public and internal repos before packaging. This ensures no overlapping entries are added to the marketplace.json file during the relocation or publishing flow.

Yes, you need python3 and jq installed to organize and publish hook scripts, as these dependencies are required to validate the repository layout, enforce the directory structure, and generate the necessary plugin.json metadata.

Yes, you can generate plugin.json with portable command paths by using a $HOME-based variable for the hook commands. This ensures the published hook scripts remain portable across different user environments without hardcoded paths.

A source hook directory must contain either a hook.py or hook.sh file, along with optional test files. The publishing process validates this repository layout before generating the plugin.json and marketplace.json metadata for the package.

Yes, the hook publisher supports both internal and public plugin publishing flows. It applies the correct directory structure and metadata generation safeguards regardless of whether you are publishing the hook package to an internal repository or a public marketplace.