AGENT SKILL

a0-development

Develop or operate Agent Zero: projects, chats, tasks, framework, tools and API/WebUI.

License 许可
MIT
最近更新
2026-11-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
a0-development
tags
[ "development", "framework", "agent-zero", "extending", "tools", "extensions", "skills", "api", "agents", "prompts", "dox" ]
author
Agent Zero Team
version
1.1.0
description
Develop or operate Agent Zero: projects, chats, tasks, framework, tools and API/WebUI.
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" ]

02 资源文件 10

03 SKILL.md 正文

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:

{"tool_name": "skills_tool:read_file", "tool_args": {"skill_name": "a0-development", "file_path": "references/<file>.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.

04 同仓库更多 Skills

mdnaimul22
mdnaimul22/human-skills

system-lifecycle-designer

Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.

★ 3
mdnaimul22
mdnaimul22/human-skills

style-sampling

Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for "an episode of", "in the style of", "sample this style", 「用这个风格做一集」. One video to copy is reverse-any-video.

★ 3
mdnaimul22
mdnaimul22/human-skills

reverse-any-video

Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.

★ 3
mdnaimul22
mdnaimul22/human-skills

typescript-patterns

TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.

★ 3
mdnaimul22
mdnaimul22/human-skills

test-collaboration

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit/integration/contract/E2E/smoke classification, bug-to-test regression protection, consumer/provider contract testing, test-necessity review, and pre-delivery evidence review.

★ 3
mdnaimul22
mdnaimul22/human-skills

story-lifecycle

Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira/Linear/Taiga but needs structured delivery tracking.

★ 3