Menu
Main entry point for all Agent Zero plugin tasks. Routes to specialist skills for creating, reviewing, contributing, managing, or debugging plugins. Use when the user mentions plugins, asks how the plugin system works, wants to build/install/uninstall/publish/debug a plugin, or asks about the Plugin Hub.
| name | a0-plugin-router |
| description | Main entry point for all Agent Zero plugin tasks. Routes to specialist skills for creating, reviewing, contributing, managing, or debugging plugins. Use when the user mentions plugins, asks how the plugin system works, wants to build/install/uninstall/publish/debug a plugin, or asks about the Plugin Hub. |
| version | 1.0.0 |
| tags | ["plugins","router","meta","create","review","contribute","manage","plugin-hub"] |
| trigger_patterns | ["plugin","create plugin","build plugin","review plugin","contribute plugin","publish plugin","install plugin","manage plugin","plugin hub","plugin index","how does the plugin system work"] |
Classify the user's request and read the appropriate specialist skill immediately.
| User intent | Skill to read |
|---|---|
| Create / build / develop / write a new plugin | Read /a0/skills/a0-create-plugin/SKILL.md |
| Review / audit / validate / check a plugin | Read /a0/skills/a0-review-plugin/SKILL.md |
| Contribute / publish / submit / share to community | Read /a0/skills/a0-contribute-plugin/SKILL.md |
| Install / update / uninstall / remove / browse / scan | Read /a0/skills/a0-manage-plugin/SKILL.md |
| Plugin not working / crashing / missing / debug / troubleshoot | Read /a0/skills/a0-debug-plugin/SKILL.md |
| Explain / how does it work / architecture | Answer inline using the overview below |
If intent is ambiguous, ask one question before routing:
"Are you trying to create a new plugin, review one, contribute it to the community, manage (install/update/uninstall) plugins, or debug a plugin that isn't working?"
If the user says "make a plugin for the community" - start with a0-create-plugin, then note that a0-contribute-plugin handles the publishing step after the plugin is built and tested.
Agent Zero discovers plugins from two roots, in priority order:
usr/plugins/<name>/ - user plugins (your custom plugins go here)plugins/<name>/ - core system plugins (framework-bundled, do not modify)A plugin is valid when its directory contains a plugin.yaml. Directories starting with . are skipped.
plugin.yaml)Every plugin requires a plugin.yaml at its root:
name: my_plugin # required by CI for community plugins (^[a-z0-9_]+$)
title: My Plugin # UI display name
description: What it does.
version: 1.0.0
settings_sections: [agent] # which Settings tabs show a subsection
per_project_config: false # enables project-scoped settings/toggle
per_agent_config: false # enables agent-profile-scoped settings/toggle
always_enabled: false # forces ON, disables toggle (framework use only)
settings_sections valid values: agent, external, mcp, developer, backup. Use [] for none.
| Directory/File | Purpose |
|---|---|
api/ | API handlers (ApiHandler subclasses) |
tools/ | Agent tools (Tool subclasses) |
extensions/python/<point>/ and extensions/python/_functions/<module>/<qualname>/<start_or_end>/ | Backend lifecycle hooks and implicit @extensible hooks |
extensions/webui/<point>/ | HTML/JS injected into UI breakpoints |
webui/config.html | Plugin settings UI |
webui/*.html, webui/*.js | Full plugin pages and Alpine stores |
hooks.py | Framework runtime hooks (install, uninstall, pre_update, cache, registration) |
execute.py | User-triggered script (setup, maintenance, repair) |
default_config.yaml | Settings defaults |
README.md | Optional locally; strongly recommended for community plugins so Plugin Hub users can inspect the plugin |
agents/<profile>/agent.yaml | Plugin-distributed agent profiles |
conf/model_providers.yaml | Add/override model providers |
LICENSE | Optional under usr/plugins/; required at the root of a plugin GitHub repo before submitting to the Plugin Index |
For @extensible targets, the only valid implicit hook layout is extensions/python/_functions/<module>/<qualname>/<start|end>/. The older flattened extensions/python/<module>_<qualname>_<start|end>/ folders are obsolete.
.toggle-1 (ON) / .toggle-0 (OFF) files in the plugin dirper_project_config or per_agent_config is truealways_enabled: true forces ON and hides controls (reserved for framework)project/.a0proj/agents/<profile>/plugins/<name>/config.jsonproject/.a0proj/plugins/<name>/config.jsonusr/agents/<profile>/plugins/<name>/config.jsonusr/plugins/<name>/config.jsonplugins/<name>/default_config.yaml| Route | Purpose |
|---|---|
GET /plugins/<name>/<path> | Serve static plugin assets |
POST /api/plugins/<name>/<handler> | Call plugin API endpoint |
POST /api/plugins | Management (toggle, config, docs) |
/a0/plugins/AGENTS.md/a0/docs/developer/plugins.md/a0/webui/components/AGENTS.md/a0/webui/js/AGENTS.md and /a0/webui/css/AGENTS.mdGuide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.
Create a new Agent Zero agent profile (subordinate). Covers where profiles live (user / plugin-distributed / project-scoped), the agent.yaml schema, the prompt inheritance & override model, and optional profile-specific tools and extensions. Use for any "create/add/new agent profile" request.
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.
Diagnose and fix Agent Zero plugin problems. Covers plugin not appearing, won't enable, API endpoints not responding, frontend store errors, extension point injection, settings resolution, hooks.py issues, and log inspection. Use when a plugin is not working, not loading, crashing, missing from the list, or behaving unexpectedly.
Manage Agent Zero plugins lifecycle: browse the Plugin Hub, scan for security, install from Git/ZIP/Plugin Hub, update, uninstall, enable, disable, debug, and troubleshoot. Use when asked to install, update, uninstall, remove, scan, find, search, enable, disable, debug, or troubleshoot a plugin.
Full audit of Agent Zero plugins in usr/plugins/. Reviews manifest validity, directory structure, code patterns (Store Gating, notifications, imports), security, and duplicate detection against the community index. Use when asked to review, audit, validate, or check an existing plugin before using or contributing it.