CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-libreoffice

Command-line interface for Libreoffice - A stateful command-line interface for document editing, producing real ODF files (ZIP archives with ...

Quality

62%

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 ./libreoffice/agent-harness/cli_anything/libreoffice/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized CLI reference with genuinely executable commands and useful agent-oriented guidance, held back by duplication, inconsistent command-group naming, and the absence of an explicit validated workflow for the document edit/export cycle. Command tables that would serve better as a one-level-deep reference file are inlined in SKILL.md. Strongest on actionability, weakest on workflow structure and file organization.

Suggestions

Add an explicit end-to-end workflow with validation checkpoints (e.g. 1. `document import input.docx -o work.json` 2. edit via Writer/Calc/Impress commands 3. `document save` 4. `export render output.pdf` 5. verify the output file exists and is non-empty before reporting success).

Move the full command-group tables to a `references/COMMANDS.md` file and keep only a quick-start example in SKILL.md, making the reference one level deep.

Reconcile command-group naming with the actual CLI invocations (the "Document" table is invoked as `project`/`document` and the "Export Group" as `export` in examples), and consolidate the duplicated REPL and `project new` examples.

DimensionReasoningScore

Conciseness

The body is mostly efficient — command tables and code blocks with little explanation of concepts Claude already knows — but includes unnecessary duplication (REPL mode described in both Usage and Examples, `project new` shown twice) and full command-reference tables inlined that could be tightened or split out. It is above anchor 2 (no heavily padded concept explanations) but not anchor 4 (the repetition and inline reference bulk could be trimmed).

3 / 5

Actionability

Mostly executable guidance: concrete invocations like `cli-anything-libreoffice --json project info -p project.json`, `document import input.docx -o work.json`, and `export render output.pdf --overwrite`. Minor gaps keep it below 5: table commands lack argument examples, and group naming is inconsistent (the "Document" group is invoked as `project`, the "Export Group" as `export`).

4 / 5

Workflow Clarity

The "For AI Agents" numbered practices and examples imply a sequence (create/import → edit → export → verify), but there is no explicit end-to-end workflow with validation checkpoints. Document manipulation is a feedback-loop-critical context and validation appears only as a single bullet ("Verify outputs exist"), so workflow clarity is capped at 3 per the rubric guidelines.

3 / 5

Progressive Disclosure

Sections are clearly organized with headers, but the ~230-line body inlines full command-group reference tables that belong in a separate reference file, and its only pointers (README.md, TEST.md, HARNESS.md "in the package") are not bundled files in the skill directory. This matches "some structure but content that should be separate is inline"; it is above anchor 2 because structure and navigation are present and clear.

3 / 5

Total

13

/

20

Passed

Description

50%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 communicates a clear niche (a stateful LibreOffice CLI producing real ODF files) in third person, but it reads as a truncated "what" statement with no trigger guidance and redundant duplicated phrasing ("Command-line interface for Libreoffice - A stateful command-line interface..."). It covers some natural keywords (LibreOffice, ODF) yet omits the component names and file extensions users would most likely mention. All dimensions land at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating or editing Writer, Calc, or Impress documents (.odt, .ods, .odp) or converting Office files (docx/xlsx/pptx) without a GUI."

Remove the duplicated opening ("Command-line interface for Libreoffice - A stateful command-line interface...") and list the concrete capabilities (create/edit Writer, Calc, and Impress documents, import Office/ODF files, export to PDF and other formats) instead of the generic "document editing".

Complete the truncated description — it currently ends mid-sentence at "(ZIP archives with XML...", losing detail that would otherwise raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ("command-line interface for document editing") and one or two concrete actions ("producing real ODF files (ZIP archives with XML...)") but is not comprehensive — no mention of Writer/Calc/Impress, import, or export. It sits above anchor 2 (which only names a domain with generic actions) and below anchor 4 (several specific actions with minor gaps).

3 / 5

Completeness

There is a clear "what" ("A stateful command-line interface for document editing, producing real ODF files") but no "when" — no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3. It is not a 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

It includes some relevant keywords users would say ("Libreoffice", "document editing", "ODF files", "command-line") but misses common variations and synonyms such as Writer, Calc, Impress, spreadsheet, presentation, or file extensions like .odt/.docx/.xlsx/.pptx. This matches the anchor for relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

The LibreOffice/ODF focus gives it a somewhat specific niche, but the broad phrase "document editing" creates real overlap risk with generic document/docx manipulation skills. It does not reach anchor 4 because the overlap risk with closely related document skills is more than minor.

3 / 5

Total

12

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

HKUDS/CLI-Anything

Path

libreoffice/agent-harness/cli_anything/libreoffice/skills/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.