CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

a0-development

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

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/a0-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

The body is a lean, well-structured orientation hub: dense non-obvious operational rules, a clear needs-to-reference navigation table with verified one-level-deep files, and a sequenced workflow with verification steps. The only notable gaps are deferred executable detail and the lack of an explicit error-recovery loop in the working flow.

DimensionReasoningScore

Conciseness

The ~55-line body is dense with operational signal Claude would not know — Docker venv split ("/opt/venv-a0" vs "/opt/venv"), "/a0/" runtime root, port discovery via "--host", "--port", "WEB_UI_HOST", "WEB_UI_PORT" — with zero concept re-teaching or padding. Every section (Reality Rules, Reference Map, Working Flow, Handoffs, Closeout) earns its tokens.

5 / 5

Actionability

Guidance is concrete throughout: named files ("AGENTS.md" chain, specific references/*.md), exact paths and env vars, a copy-paste tool invocation JSON, and named handoff skills (a0-create-plugin, a0-manage-plugin, a0-create-agent, build-skill). It stops short of 5 because most executable detail (commands, API specifics) is deferred to reference files, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

The Working Flow gives a clear 7-step sequence (classify task → read AGENTS.md chain → read reference → inspect source → keep changes narrow → update DOX → run targeted checks) with validation in step 7 ("verify frontmatter parsing, reference paths, and markdown sanity") and Closeout reporting requirements. It is not 5 because there is no explicit error-recovery feedback loop (validate → fix → re-validate) for the verification steps.

4 / 5

Progressive Disclosure

The body is a clean overview: a Need→Read table maps each task type to one of 8 reference files, all of which exist in references/, and inspection confirms references are one level deep with no nested chains. Content is appropriately split, handoffs to other skills are explicit, and navigation is easy — matching the top anchor.

5 / 5

Total

18

/

20

Passed

Description

65%Weight 40%Scale 1-5

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 is distinctive and reasonably specific, anchored by the named Agent Zero system and a good spread of natural domain keywords. Its main weakness is the absence of any "when to use" trigger guidance, which caps completeness, and its reliance on two broad verbs rather than concrete enumerated actions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to extend, build features for, or operate Agent Zero — projects, chats, tasks, tools, extensions, or API/WebUI work."

Replace the broad verbs "develop or operate" with concrete actions such as "create projects and chats, manage tasks, build tools and extensions, add API endpoints".

Include the natural action phrasings users would say ("extend agent zero", "add a tool", "create an agent profile") so trigger-term coverage matches the frontmatter trigger_patterns.

DimensionReasoningScore

Specificity

"Develop or operate Agent Zero: projects, chats, tasks, framework, tools and API/WebUI" names the domain and two broad actions (develop, operate) with an enumeration of surfaces, matching the anchor for 1-2 concrete actions without comprehensive coverage. It falls short of 4 because the colon list names domain objects rather than several specific concrete actions (e.g., "create projects", "add tools", "extend the framework").

3 / 5

Completeness

It clearly answers "what" (develop or operate Agent Zero across projects, chats, tasks, framework, tools, API/WebUI) but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the "what" is specific and multi-faceted, not vague.

3 / 5

Trigger Term Quality

The description includes natural nouns users would say — "projects", "chats", "tasks", "tools", "API/WebUI" — giving good keyword coverage anchored to the distinctive term "Agent Zero". It is not 5 because common action phrasings users would naturally use ("extend", "build a feature", "add a tool", "plugin") are missing from the description itself.

4 / 5

Distinctiveness Conflict Risk

"Agent Zero" names a specific system and the enumerated surfaces (projects, chats, tasks, framework, tools, API/WebUI) further narrow the niche, so it is unlikely to trigger for the wrong skill. This matches the anchor for a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

agent0ai/agent-zero

Path

skills/a0-development/SKILL.md

Reviewed

Table of Contents

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.