mirror of
https://github.com/agent0ai/agent-zero.git
synced 2026-07-09 17:08:29 +00:00
f8b06e0b12
Delete the empty active-skills prompt extension and its unused prompt template now that selected skills are loaded through chat history instead of protocol. Stop clearing legacy loaded_skills keys from protocol/extras in the loaded-skills hook while keeping history reattachment for compacted skill bodies. |
||
|---|---|---|
| .. | ||
| api | ||
| extensions/webui/initFw_end | ||
| helpers | ||
| webui | ||
| __init__.py | ||
| AGENTS.md | ||
| default_config.yaml | ||
| hooks.py | ||
| LICENSE | ||
| plugin.yaml | ||
| README.md | ||
Skills
Skills is a built-in Agent Zero plugin that manages skill loading and visibility for the current chat.
What It Does
- loads selected skills into current-chat history
- hides noisy skills from the model-facing available catalog, skill search, and load access
- shows loaded skills without offering removal, because loaded skill bodies are part of chat history
- lets users hide or show skills live per conversation
- supports global and project scoped configurations without agent-profile variants
- links directly to the built-in Skills list
- links directly to the active project's Skills section when a project is active
Why This Exists
Agent Zero already supports loading skills dynamically with skills_tool, and already has great built-in skill management surfaces. What it did not have was a lightweight way to use that same history-backed skill loading from the Skills screen.
Skills fills that gap as a bundled built-in plugin.
The shared skill discovery and loaded-skill ledger live in helpers/skills.py, and this plugin focuses on catalog UI, chat loading, and visibility.
Notes
- selected skills are appended to current-chat history using the same metadata shape as
skills_tool - loaded skills are not removable from the UI; future context compaction may reattach their bodies from the loaded-skill ledger
- hidden skills are stored as control data, not injected into the prompt
- hidden skill paths are stored in normalized
/a0/...form so configs stay portable across development and Docker-style layouts - if a configured hidden skill is not visible in the current agent scope, it is skipped quietly instead of breaking catalog builds