a0-create-plugin

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.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/a0-create-plugin/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable templates and a well-sequenced, validation-aware community submission workflow. Its main weakness is conciseness/progressive disclosure: a large amount of detail is inlined in SKILL.md with no bundle files to split it out.

Suggestions

Extract the longer reference material (e.g. full community submission/index manifest details, import-path rules) into one-level-deep reference files linked from SKILL.md to improve progressive disclosure and reduce inline length.

De-duplicate the plugin-local import guidance, which appears in both the 'Backend API & Context' and 'Import rule for plugin-local Python code' sections.

Tighten prose passages like the 'First rule of plugin side effects' paragraph into concise imperatives to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is dense with immediately useful, executable specifics, but it is long and repeats import-path guidance in multiple sections, and a few explanatory passages (e.g. 'First rule of plugin side effects...') could be tightened without losing clarity.	2 / 3
Actionability	It provides complete, executable code/templates across manifest YAML, the Store Gate HTML wrapper, separate store module, settings modal, backend imports, messaging, settings read/write, execute.py, and hooks.py — copy-paste ready and concrete throughout.	3 / 3
Workflow Clarity	The community-plugin path is a clearly numbered submission flow with CI validation checkpoints and constraints, and execute.py/hooks.py guidance includes explicit validation (return codes, rerun safety, validation of name-field matching), giving clear sequencing with feedback loops.	3 / 3
Progressive Disclosure	The body lists primary references and related skills at the top and points to a guided contribution flow, but all detailed plugin-build guidance lives inline in SKILL.md with no bundle files present; there are no one-level-deep reference files to offload the substantial inline content.	2 / 3
	Total	10 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies the Agent Zero plugin domain and lists several capabilities with supporting trigger patterns, but it embeds framework jargon and lacks an explicit 'Use when...' clause in the description text itself. It is solid but not exemplary.

Suggestions

Add an explicit 'Use when...' clause to the description naming natural user phrases (e.g. 'Use when the user asks to create, build, or extend an Agent Zero plugin').

Replace or downplay framework jargon ('Store Gating', 'AgentContext') in the description with user-facing terms so trigger matching is more natural.

Sharpen distinctiveness from the related a0 plugin skills (review, contribute, manage) by stating this skill is specifically for creation/extension/modification.

Dimension	Reasoning	Score
Specificity	Names the domain ('Agent Zero plugins') and several concrete capabilities (UI hooks, API handlers, lifecycle extensions, plugin settings UI), but does not enumerate the full set of actions as comprehensively as the 3-anchor examples, and leans on framework jargon for some actions.	2 / 3
Completeness	It clearly states what the skill does but the 'when to use' guidance is delivered via a separate trigger_patterns list rather than an explicit 'Use when...' clause in the description; per the guidelines a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Trigger patterns in frontmatter ('create plugin', 'build plugin') are natural, but the description text itself uses technical conventions ('Store Gating', 'AgentContext') that a user would rarely say, so coverage of natural terms is partial.	2 / 3
Distinctiveness Conflict Risk	The Agent Zero plugin niche is fairly specific, but the broad action list (UI hooks, API handlers, settings) could overlap with adjacent a0 plugin skills (review/contribute/manage) referenced in the body, so conflict risk is not fully eliminated.	2 / 3
	Total	8 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: agent0ai/agent-zero
Path: skills/a0-create-plugin/SKILL.md
Commit: 391fab9

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.