CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

writer

Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.

Quality

70%

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/AI-Agents-Safe-Coding-Skills-claude/skills/libreoffice/writer/SKILL.md

The canonical home for this skill is writer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured, code-forward skill body with executable examples for the main workflows. Its main weaknesses are the lack of any validation/verification checkpoints for batch and document-repack operations, and some redundant or generic sections that could be tightened or split into reference files.

Suggestions

Add explicit validation steps after batch conversion and template repack workflows (e.g., verify output file exists and opens, validate modified content.xml), with fix-and-retry loops for failures.

Trim redundancy and off-topic content: merge the Format Conversion Reference with Core Capabilities, and drop the --calc/--impress/--draw lines from a Writer skill.

Move the UNO socket-listener setup next to the UNO code example (or reference a script) so the example is self-contained, and consider moving the UNO/format details into reference files.

DimensionReasoningScore

Conciseness

The body is mostly dense and code-focused with little conceptual padding, but there is redundancy and generic filler: 'Best Practices' items like 'Test conversions thoroughly' and 'Handle conversion failures gracefully', the Format Conversion Reference repeating Core Capabilities, and soffice --calc/--impress/--draw flags irrelevant to a Writer skill. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean 5 anchor.

3 / 5

Actionability

Mostly executable, concrete guidance: ready-to-run soffice --headless --convert-to commands, a complete UNO Python snippet, an odfpy example, and a working template-fill script. Falls short of 5 because of minor gaps — the UNO example silently assumes a running socket listener (setup is buried in Troubleshooting), and the odfpy example omits paragraph text insertion.

4 / 5

Workflow Clarity

Sequences exist (three creation methods, conversion commands, template generation), but validation/checkpoints are entirely absent: the batch conversion loop never verifies outputs, and the template workflow edits content.xml and repacks with no validation step. Per the guideline that batch/destructive operations without validation cap workflow clarity at 3, this cannot score above 3 despite the coherent structure.

3 / 5

Progressive Disclosure

No bundle files exist, and the ~190-line body is well-organized into clearly headed sections (workflows, references, troubleshooting, resources). This fits 'good structure; most content appropriately placed; minor organization gaps'. Not a 5 because reference-worthy material (UNO API usage, format conversion matrix) is inlined in a longer document where one-level-deep reference files would improve navigation.

4 / 5

Total

14

/

20

Passed

Description

66%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 solid, concise description that clearly conveys what the skill does with concrete format names and capabilities. Its main weakness is the complete absence of 'when to use' trigger guidance, which caps completeness and limits discovery.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating or converting ODT/DOCX/PDF documents, performing mail merges, or automating document generation with LibreOffice.'

Add common synonyms and file extensions users might say, such as 'Word documents', '.odt', 'convert to PDF', and 'DOC' files.

Mention document editing and template usage to round out capability coverage.

DimensionReasoningScore

Specificity

Names several concrete capabilities — 'Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation' — matching the anchor for several specific actions with minor coverage gaps (e.g., editing, styles, templates are absent). Not a 5 because coverage is not comprehensive, and the noun-phrase style lists fewer distinct actions than the top anchor.

4 / 5

Completeness

The 'what' is clear (create, convert, mail merge, automate documents), but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'document creation', 'format conversion', 'ODT', 'DOCX', 'PDF', 'mail merge', 'LibreOffice Writer' — terms users would actually say. A few natural variations are missing ('Word documents', 'convert to PDF', '.doc'), so it falls just short of the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

'LibreOffice Writer' plus explicit ODT/DOCX/PDF formats carves a clear niche that is mostly distinct, with only minor overlap risk against closely related skills (e.g., a generic DOCX- or PDF-focused skill). It does not reach 5 because document format conversion is territory where sibling skills could also trigger.

4 / 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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/libreoffice/writer/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.