publish-install

Publish and install Native or Process plugin ZIP packages with unload and reload handling.

46|7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill publish-install
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-install
Source: https://github.com/sunyonghuan/Netor.Madorin/tree/main/Plugins/Samples/ReminderPlugin/.github/skills/plugin-development/subskills/publish-install
Command: npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill publish-install

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill standardizes plugin release and installation so you can update loaded Native or Process plugins without manually copying files or breaking runtime state.

Core Features & Use Cases

  • Zip-based installation: Publishes plugin packages as ZIP archives and installs them through the approved package flow.
  • Safe update handling: Checks loaded plugins, unloads the target when updating, then reloads it after installation.
  • Typical use cases: Releasing a new plugin build, installing a fresh plugin package, or hot-reloading an updated plugin in a running environment.

Quick Start

Ask me to publish a plugin package, install it with the approved ZIP flow, and reload any already loaded plugin safely.

Frequently Asked Questions about publish-install

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

FAQPage Schema
How do I hot reload a plugin package that is already loaded?

To hot reload a plugin package, the Skill checks loaded plugins, unloads the target plugin, installs the updated ZIP package, and then verifies the post-install reload.

How do I install a fresh Native or Process plugin from a ZIP archive?

You can install a fresh Native or Process plugin by publishing it as a ZIP archive and processing it through the approved ZIP deployment flow without needing to unload existing components.

What is the safest way to update a running plugin without breaking runtime state?

The safest way to update a running plugin is using the unload-before-install handling mechanism, which removes the active plugin before applying the ZIP installation and reloading it.

Does the ZIP deployment flow support both Native and Process plugins?

Yes, the ZIP deployment flow explicitly supports publishing, installing, and hot reloading both Native and Process plugins while maintaining runtime stability.

Why do I need to unload a plugin before installing an update?

You need to unload a plugin before installing an update to prevent breaking the runtime state, ensuring the old version is safely removed before the new ZIP package is applied.