markdown-documents

Use when creating or editing Markdown documents, notes, reports, briefs, drafts, or other editable writing where Markdown should be the primary artifact format.

Quality

70%

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 ./plugins/_office/skills/markdown-documents/SKILL.md

Quality

Content

71%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, actionable guide for a simple single-purpose skill, with a clear workflow and a copy-paste example. Its main weakness is redundancy between the intro and the practical-rules section, which slightly hurts token efficiency.

Suggestions

De-duplicate the practical rules: the ODT/DOCX preference and Editor-surface behavior are already stated in the intro paragraphs, so trim the repeated bullets.

Add a minimal patch example alongside the create example so the edit case is as concrete as the create case.

Vary the repeated 'unless the user explicitly asks' phrasing to reduce padding in the Editor-surface paragraph.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but the 'Practical rules' duplicate the intro (ODT/DOCX preference and Editor-surface guidance are each stated twice) and 'unless the user explicitly asks' repeats, so it is mostly efficient with notable redundancy that could be tightened.	3 / 5
Actionability	A concrete, copy-paste JSON example for text_editor write plus specific patch-vs-write guidance is executable, but only the create case is exemplified — the common edit/patch case lacks a concrete example, leaving a minor gap.	4 / 5
Workflow Clarity	The four-step workflow (decide, create, read-then-patch/write, report) is clearly sequenced for a simple non-destructive skill, with the final report step as a soft checkpoint, but there is no explicit verify-the-write validation step.	4 / 5
Progressive Disclosure	The skill is under 50 lines, self-contained with no need for external references, and well-organized into clear sections (intro, Workflow, example, practical rules), satisfying the simple-skill exception for a top score.	5 / 5
	Total	16 / 20 Passed

Description

70%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 strong on trigger phrasing and explicit 'Use when' guidance, with a clear Markdown-writing niche. Its main weakness is thin action specificity — only two generic verbs — which keeps it just below the top anchors.

Suggestions

Expand the 'what' beyond 'creating or editing' to list a few concrete actions (e.g., 'format with headings and tables, convert between .md and office formats') to lift specificity and completeness.

Add the '.md' file extension to the description's trigger terms for full keyword coverage.

Tighten the trigger list or add a discriminating clause to reduce overlap with general office-document skills.

Dimension	Reasoning	Score
Specificity	The description names the domain richly ('Markdown documents, notes, reports, briefs, drafts, or other editable writing') but offers only two generic verbs ('creating or editing'), matching the anchor that names the domain with 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It has an explicit 'Use when...' trigger clause with concrete trigger phrases, and the 'what' (creating/editing Markdown) is present but thin and fused into the when-clause, so it answers both but not as comprehensively as the top anchor.	4 / 5
Trigger Term Quality	It covers natural user phrasings and synonyms ('Markdown documents, notes, reports, briefs, drafts, editable writing') but omits the '.md' file extension from the description, leaving a few natural terms missing rather than fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	'Markdown should be the primary artifact format' is a clear niche discriminator, though the broad list of writing types creates minor overlap risk with general writing or office-document skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: agent0ai/agent-zero
Path: plugins/_office/skills/markdown-documents/SKILL.md
Commit: b22a144

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.