build-skill
Create, rename, move, audit, test or refine Agent Zero skills and reusable workflows.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- build-skill
- description
- Create, rename, move, audit, test or refine Agent Zero skills and reusable workflows.
02 资源文件 1
- 参考文档AGENTS.md1017 B
03 SKILL.md 正文
Build Skill
Skills are small folders that teach Agent Zero a repeatable workflow. Keep the always-visible metadata precise, keep SKILL.md lean, and move detailed material into scripts, references, or assets only when the task needs it.
Standard Shape
Every skill folder must be named exactly like the skill and contain SKILL.md.
skill-name/
├── SKILL.md
├── scripts/ # optional deterministic helpers
├── references/ # optional details loaded only when needed
└── assets/ # optional output resources or templates
The frontmatter should contain name, description, and optional triggers when lexical discovery needs phrases that do not fit naturally in the description:
---
name: skill-name
description: What the skill does and when to use it.
triggers:
- "user phrase that should surface this skill"
---
Use lowercase letters, digits, and hyphens. Prefer short verb-led names such as build-skill, review-plugin, or host-file-editing.
Workflow
- Identify two or three real user requests that should trigger the skill.
- Decide whether the skill belongs in core
skills/or inside a plugin'splugins/<plugin>/skills/directory. - Write the frontmatter description with the core trigger condition and key context; add
triggersfor short user phrases that should rank highly in skill search or relevant-skill recall. - Keep the body focused on procedure, contracts, failure handling, and the files/scripts to load next.
- Move long examples, schemas, policies, or variant-specific detail to one-level-deep
references/files. - Add scripts only for deterministic or repeatedly rewritten operations, and test representative scripts.
- Validate by searching, loading, and using the skill on a median-user prompt.
Placement
Use plugin-scoped skills when the skill exists to explain a plugin-owned tool or UI surface. Examples: Browser workflows belong under _browser; A0 CLI host tools belong under _a0_connector; Desktop canvas workflows belong under _desktop.
Use root skills/ for Agent Zero framework workflows that are not owned by one plugin, such as building skills, developing core features, or managing community plugins.
Writing Rules
- Put trigger language in frontmatter, not in a body section. Use
descriptionfor the compact always-visible purpose andtriggersfor phrase matches used by search and relevant-skill recall. - Do not add README, changelog, quick reference, or install guide files inside the skill.
- Avoid compatibility aliases in prompts or skill bodies when renaming; update references to the new name.
- Prefer concise examples over long prose.
- Do not duplicate the same guidance in both
SKILL.mdand references. - When multiple skills could apply, keep each skill's responsibility narrow and name the handoff clearly.
Validation
Run targeted checks after edits:
conda run -n a0 pytest tests/test_skills_runtime.py tests/test_tool_action_contracts.py -q
Also exercise the live path when the skill changes agent-facing tool behavior:
1. Ask a short ordinary prompt that should discover the skill.
2. Confirm the agent uses skills_tool search/load when appropriate.
3. Confirm it calls the intended tool only after the skill is loaded when the tool is skill-gated.
04 同仓库更多 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.
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.
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 「复刻这个视频」「照着这个视频做一个」.
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.
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.
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.