CtrlK
BlogDocsLog inGet started
Tessl Logo

writer-documents

Use when creating, opening, or editing LibreOffice Writer ODT documents, or DOCX documents only when Microsoft Word compatibility is explicitly required.

64

Quality

78%

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 ./plugins/_office/skills/writer-documents/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A concise, mostly actionable skill body that is well-structured for its size. The main gap is the missing validation/feedback checkpoint in the edit workflow, which the rubric caps at 3 for document manipulation.

Suggestions

Add an explicit validation/verification step to the edit workflow (e.g., re-read the document or confirm the change saved correctly before proceeding) to lift workflow_clarity above the document-manipulation cap of 3.

Provide a complete copy-paste JSON example for the edit action — not just the action-name list — so both create and edit paths are fully executable.

Tighten the UI/Desktop paragraph by consolidating the repeated no-auto-open guidance and the list of faux-label prohibitions into a single concise rule.

DimensionReasoningScore

Conciseness

Lean with no concept padding and a tight code example, but the UI/Desktop paragraph restates the no-auto-open rule and stacks several "do not" clauses that could be trimmed.

4 / 5

Actionability

The create path is a complete, copy-paste JSON example, but the edit path only enumerates action names (set_text, append_text, …) without a full second executable example.

4 / 5

Workflow Clarity

The edit workflow lists a clear 3-step sequence but has no validation/verification checkpoint; per the rubric, document-manipulation workflows without validation are capped at 3.

3 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized sections (# Writer Documents / ## Workflow / Create / Edit / Practical rules), meeting the simple-skill exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

83%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.

A strong, third-person description with an explicit trigger clause, concrete actions, and good natural keyword coverage. Its only weakness is mild overlap risk on the DOCX side and a few missing keyword variants.

DimensionReasoningScore

Specificity

Names the domain (LibreOffice Writer ODT, DOCX) and three concrete actions ("creating, opening, or editing"), which exceeds the 1–2 action anchor but stops short of comprehensive coverage (no formatting/converting/merging).

4 / 5

Completeness

An explicit "Use when…" clause is present and both what (create/open/edit ODT & DOCX) and when (DOCX only when Word compatibility is explicitly required) are answered with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users say ("LibreOffice Writer", "ODT", "DOCX", "Microsoft Word") with synonyms, but omits dotted extensions (.odt/.docx) and common phrasings like "Word docs".

4 / 5

Distinctiveness Conflict Risk

ODT/Writer is a clear niche and the DOCX conditional scoping reduces overlap, but DOCX still carries minor conflict risk with generic Word/document skills.

4 / 5

Total

17

/

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.

Validation15 / 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
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.