QwenLM/qwen-mm-plugins-hub

QwenLM/qwen-mm-plugins-hub

Description: A documentation for Qwen-MM-Plugins

Language: HTML

License: Apache-2.0

Stars: 1

Forks: 0

Open issues: 0

Created: 2026-09-09T07:40:40Z

Pushed: 2026-09-09T21:03:10Z

Default branch: main

Fork: no

Archived: no

README:

Qwen MM Plugins Hub

Documentation, tool references, and cookbooks for Qwen MM Plugins.

Browse the Hub · Install plugins · Plugin source

Use the plugins

Open the Hub, choose a plugin, and follow its Install tab. Its Cookbook has workflows and examples. You do not need to run this repository.

Add or update a plugin

1. In [Qwen-MM-Plugins](https://github.com/QwenLM/Qwen-MM-Plugins): implement the plugin, write its Skill and tool docstrings, and register it using Add a new plugin. Update existing plugins in the same place. 2. In this repository: add or edit content/cookbooks//usage.md. Put example files in public/cases///assert/ and link them from the cookbook. Replace ` with the plugin's capability ID, such as core`.

The Hub reads plugin descriptions, Skills, tools, and English guides automatically. Generated data/*.json stays out of Git; only the source repository owns that content. Hub authoring has a copyable cookbook template, media examples, and local content-refresh instructions.

Work on the website locally

Use Node 24, Git, and uv:

git clone https://github.com/QwenLM/qwen-mm-plugins-hub.git
cd qwen-mm-plugins-hub
npm ci
npm run dev

Open the URL printed by the server. Development and production builds generate content automatically; the first run downloads the configured plugin source and exporter dependencies. Run npm run content:sync to refresh the cached source. See local validation to use your own plugin checkout or Python environment.

Publish your changes

• Hub changes: merge your PR or push to this repository's main; GitHub Actions builds and publishes the website automatically.
• Plugin-source changes only: merge into the branch selected in [source.config.json](source.config.json), currently plugin main. The Hub checks for updates every 30 minutes and rebuilds when the source or release tags change. You can also use Run workflow on Build and deploy plugin directory.

For a new plugin, both its source and Hub cookbook must be available before the build runs. Stable publishing waits for the release tags referenced by the plugin catalog. Failed builds leave the public site unchanged. See Hub automation for immediate-refresh setup and source-PR build checks. PR results appear in GitHub Checks; there is no comment bot or preview hosting. Publishing the website does not publish plugin releases.

Maintenance constraints and verification commands are in [AGENTS.md](AGENTS.md). See [third-party notices](THIRD_PARTY_NOTICES.md) for licenses and content provenance.