writer-documents

Create, open or edit Writer documents: ODT default; DOCX for Word compatibility.

Quality

72%

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/writer-documents/SKILL.md

Quality

Content

72%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 an efficient, well-organized instruction skill: a concrete create example, specific named edit actions, and clear format/UI policy. Its main gap is the lack of any post-edit verification or feedback loop in the edit workflow, and edit/read actions lack example payloads.

Suggestions

Add a verification step after edits, e.g. re-run the read action (or check the saved result) to confirm the change landed, creating a validate-and-retry loop for the document-manipulation workflow.

Include one short example JSON payload for the edit action (e.g. replace_text with file_id/path and text args) so the common edit case is copy-paste ready like the create case.

Merge the duplicated UI-ownership rules (faux action labels vs. 'do not say the document is open') into a single rule set to save tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean, explains no concepts Claude already knows, and every section carries operational rules. Minor redundancy: the UI-ownership rules are stated twice ("Do not write faux UI action labels such as 'Open document'" and "Do not say the document is open. Say it was created or updated"), which could be trimmed — anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	Provides a concrete, copy-paste-ready JSON tool call for creation and names specific edit actions ("set_text, append_text, prepend_text, replace_text, delete_text") plus the read-before-edit rule. Minor gaps: no example payloads for the read or edit actions, so common edit cases lack a model — anchor 4, not 5.	4 / 5
Workflow Clarity	Create and edit sequences are present and ordered, with a pre-edit checkpoint ("Use the read action with file_id or path before content-sensitive edits"), but there is no post-edit verification or feedback loop. Per scoring notes, document manipulation without validation feedback loops caps workflow_clarity at 3; it stays above 2 because the sequence itself is clear and specific.	3 / 5
Progressive Disclosure	The skill is a single-purpose, ~35-line body with no bundle files (references/, scripts/, assets/ do not exist) and no content that belongs in separate files. Sections (## Workflow, practical rules) are well organized, which per the judging guidelines earns a 5 for a sub-50-line skill needing no external references.	5 / 5
	Total	16 / 20 Passed

Description

61%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 concise and distinct, with a clear format policy (ODT default, DOCX for compatibility) and good natural trigger terms. Its main weakness is the absence of an explicit 'Use when...' clause, which caps completeness and leaves the triggering conditions only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a Writer/ODT document, mentions Word/DOCX compatibility, or provides an existing .docx or .odt file."

Name one or two more concrete capabilities (e.g. structured text edits such as append/replace/delete, or reading existing documents) to lift specificity beyond the generic create/open/edit triad.

Include common synonyms like "LibreOffice" and "OpenDocument" in the description itself so trigger matching does not depend solely on the frontmatter triggers list.

Dimension	Reasoning	Score
Specificity	"Create, open or edit Writer documents" names the domain plus three verbs, but the verbs are the generic document triad and coverage is not comprehensive (no mention of reading, structured edits, or formatting). It matches anchor 3 better than anchor 4, which expects several distinct specific capabilities.	3 / 5
Completeness	The "what" is clear (create/open/edit Writer documents with an ODT-default format policy), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied by "DOCX for Word compatibility". Per judging guidelines, a missing 'Use when' clause caps completeness at 3; it is not 2 because the what is clear rather than vague.	3 / 5
Trigger Term Quality	Includes natural terms users would say — "Writer documents", "ODT", "DOCX", "Word" — but misses common variations such as "LibreOffice", "OpenDocument", and literal .odt/.docx extensions. Good coverage with a few natural terms missing fits anchor 4, not the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	"Writer documents", "ODT", and "DOCX" carve a mostly distinct niche with minor overlap risk against generic office/document skills — matching anchor 4. It is not 5 because the bare phrase "Writer documents" could still brush against other document-creation skills.	4 / 5
	Total	14 / 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/writer-documents/SKILL.md
Commit: e3051fb

Reviewed: 10 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.