office-artifacts

Use when creating, opening, reading, or editing Office artifacts such as LibreOffice-native ODT/ODS/ODP files and compatibility DOCX/XLSX/PPTX files with the office_artifact tool.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An actionable, well-organized skill body with executable examples and a complete argument reference. The main gap is an explicit validation/feedback loop for destructive edits, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint for destructive edit operations (e.g., replace_text/delete_text): read after edit to confirm the change, and retry if the find string was not matched.

Tighten the Practical Rules section, which repeats the Desktop/Editor auto-open guidance already stated in the intro paragraph.

For set_cells and create_chart, note how to verify the result (e.g., re-read the range or confirm the chart object) so batch/visual operations have a feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean and task-focused with executable JSON examples and an argument reference, avoiding explanation of known Office/ODF concepts; minor rule repetition in Practical Rules but no padded fluff.	3 / 3
Actionability	Provides copy-paste-ready, fully executable tool_args examples for create/read/edit/append/set_cells/create_chart plus a complete per-format operation list and argument reference.	3 / 3
Workflow Clarity	A clear numbered workflow with a read-before-edit step exists, but there is no explicit validate-then-proceed feedback loop for destructive operations like replace_text/delete_text, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	No bundle files exist and the body is self-contained with well-organized labeled sections, which is appropriate for a single-file skill per the scoring notes.	3 / 3
	Total	11 / 12 Passed

Description

100%

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, well-targeted description that explicitly answers what the skill does and when to invoke it, with concrete actions and natural trigger terms. It is distinguishable from sibling skills through format-specific scoping.

Dimension	Reasoning	Score
Specificity	Names four concrete actions ("creating, opening, reading, or editing") plus specific formats and the tool name, matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly states what it does ("creating, opening, reading, or editing Office artifacts... with the office_artifact tool") and when to use it via the "Use when..." clause, answering both what and when.	3 / 3
Trigger Term Quality	Covers natural terms users say including file extensions ("ODT/ODS/ODP", "DOCX/XLSX/PPTX") and "Office artifacts/documents" with good variation coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to LibreOffice-native and OOXML compatibility formats via a specific tool, with distinct format-extension triggers unlikely to conflict with general document skills.	3 / 3
	Total	12 / 12 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/office-artifacts/SKILL.md
Commit: 391fab9

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.