--- name: a0-development-96de797ce2a5 description: "Develop or operate Agent Zero: projects, chats, tasks, framework, tools and API/WebUI." version: 1.1.0 author: Agent Zero Team tags: ["development", "framework", "agent-zero", "extending", "tools", "extensions", "skills", "api", "agents", "prompts", "dox"] trigger_patterns: - "extend agent zero" - "agent zero development" - "build agent zero feature" - "create agent zero tool" - "add extension" - "framework development" - "agent zero architecture" - "how does agent zero work" - "create agent zero extension" - "add api endpoint" - "create agent profile" - "agent zero internals" - "how does the agent loop work" - "extension hook points" - "prompt system" - "agent profile" - "dox" - "manage Agent Zero projects" - "create Agent Zero chat" - "Agent Zero API" - "create project" - "activate project" - "project instructions" - "create chat" - "new chat" --- # Agent Zero Development Use this skill to develop Agent Zero or operate an existing instance on the user's behalf. For projects, chats, tasks, and other application features, read `references/operate-agent-zero.md` and use existing APIs. Load only the references needed for the task; verify current source before changing code. ## Reality Rules 1. Source and nearest DOX beat memory, examples, and this skill if they disagree. 2. Before editing, read the applicable `AGENTS.md` chain from the repo root to every file you expect to touch. 3. New capabilities should usually be plugins. For plugin-specific work, load `a0-create-plugin` for authoring/review/contribution or `a0-manage-plugin` for discovery and lifecycle operations. 4. Do not assume ports. Discover WebUI host/port from startup output, launcher or Docker mapping, or explicit `--host`, `--port`, `WEB_UI_HOST`, and `WEB_UI_PORT` configuration. 5. In Docker, framework checks belong to `/opt/venv-a0` and agent/user code execution belongs to `/opt/venv`. Do not use one runtime as proof for the other. 6. Treat `/a0/` as the runtime framework root inside Docker. In local development it means the repository root. If a live container matters, prove that `/a0` matches the checkout before trusting source-only conclusions. 7. Do not document or change ignored `usr/` or `tmp/` runtime state unless the user explicitly asks. ## Reference Map Load references with: ```json {"tool_name": "skills_tool:read_file", "tool_args": {"skill_name": "a0-development", "file_path": "references/.md"}} ``` | Need | Read | |---|---| | Operate Agent Zero for the user: projects, chats, tasks, profiles, skills and settings | `references/operate-agent-zero.md` | | Runtime split, root layout, discovery order, path and port boundaries | `references/architecture-runtime.md` | | DOX edit workflow, when to update docs, file-level DOX checks | `references/dox-workflow.md` | | Tool contracts, locations, prompts, and verification | `references/tools.md` | | Python/WebUI extension discovery, hook points, ordering, implicit hooks | `references/extensions.md` | | HTTP API, WebSocket handlers, WebUI extension surfaces | `references/api-webui.md` | | Agent profiles, prompts, skills, projects | `references/agents-prompts-skills-projects.md` | | Plugin-first workflow, where to put new work, handoffs to plugin skills | `references/plugins-workflow.md` | ## Working Flow 1. Distinguish operating existing features from developing new behavior. For application operations, follow `references/operate-agent-zero.md`; the remaining steps apply to source changes. 2. Read the root `AGENTS.md`, then the nearest child `AGENTS.md` files for the target paths. 3. Read the focused reference file from this skill. 4. Inspect the current source files named by the reference before making a claim or patch. 5. Keep changes narrow and in the repo-owned surface. Prefer `usr/` for user-created runtime content, but do not document ignored user state unless requested. 6. Update DOX when a durable contract, path, behavior, workflow, responsibility, or verification rule changes. 7. Run targeted checks from the relevant DOX file. For skill-only changes, at minimum verify frontmatter parsing, reference paths, and markdown sanity. ## Handoffs - Plugin creation: load `a0-create-plugin`. - Plugin management or installation: load `a0-manage-plugin`. - Plugin review, debugging or publishing: load `a0-create-plugin` and read its relevant reference. - Agent profile creation: load `a0-create-agent`. - Skill creation or skill format work: load `build-skill`. ## Closeout Report the exact files changed, the grounding checks used, whether DOX was updated or intentionally left unchanged, and what verification ran. If a claim depends on a live Docker runtime, include the runtime proof, not only checkout evidence. --- Source attribution: agent0ai Original project: https://github.com/agent0ai/agent-zero License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2026 Gabriel Moreira Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: agent0ai Original project: https://github.com/agent0ai/agent-zero Attribution basis: Upstream repository explicitly recorded in package mirror path Fields of work: Development & Engineering, Product Management Roles: Backend Developer, DevOps / SRE, ML / AI Engineer, Product Manager, Technical Product Manager Specialties: API, Backend, Database, Design, DevOps, Word Documents, Frontend, Git, Testing Tools: AWS, Docker, Firebase, GCP, GitHub Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 9570d8e7548205ec754e6f7dc59d67f33d76619fd2ce256615cb82ef3e8372b9