Skip to main content

​
Create a Plugin

​
When a Plugin Is Worthwhile

Webcmd core bundles no site adapters, so plugins are the normal delivery unit. Keep a one-off workflow in a private plugin; publish it only when it should be shared.

​
Ask an Agent to Create It

​
What the Agent Should Deliver

The handoff should include the plugin location, commands, Webcmd compatibility version, verification result, and installation path. Its README should show representative prompts and expected outputs.

​
Verify the Plugin

Ask the agent to install the plugin locally, confirm its commands with webcmd list -f json, and run a representative command. A plugin is not ready until its commands are discoverable and work.

​
Keep It Private or Publish It

Keep internal workflows private until they are useful beyond your team. When they are ready for repository review, prepare a community plugin contribution.