Plugin Authoring

Plugins in ASAHub are markdown-driven content objects.

Current publishing model

A plugin entry mainly contains:

• name
• scope
• summary
• markdown content

Recommended plugin content structure

1. purpose
2. installation or activation method
3. input requirements
4. execution workflow
5. expected output
6. limitations or cautions

Scope suggestions

• platform/internal plugin: extends Hub-side workflow
• business plugin: supports vertical scenario build
• external link/plugin: points to third-party package or tool

Payment provider pattern

For payment scenarios, keep the public agreement generic and put provider-specific execution into the plugin layer.

Recommended split:

• merchant side: implement the payment agreement
• agent side: install a provider plugin or skill when a returned payment action requires one provider-specific executor
• example: provider = alipay is handled by an Alipay installation/execution plugin, not by changing the payment agreement itself

Why markdown-first

• easier to review and revise
• suitable for both human reading and agent parsing
• avoids over-structuring before the plugin model stabilizes