impress-presentations

Use when creating, opening, or editing LibreOffice Impress ODP presentations, or PPTX decks only when PowerPoint compatibility is explicitly required.

Quality

75%

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/impress-presentations/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 concise, actionable, and well-organized for a simple single-tool skill, with two concrete JSON examples. Its chief weakness is workflow clarity: the set_slides edit overwrites deck content yet the workflow includes no validation or verification checkpoint, which caps that dimension.

Suggestions

Add a verification step after set_slides edits (e.g., confirm the deck saved and the slide count/title matches intent) since set_slides overwrites all slides, satisfying the destructive/batch validation requirement and lifting the workflow_clarity cap.

Show the '---' separator text-to-slide creation path as a concrete code example rather than only describing it in prose, so both creation methods are copy-paste ready.

Split the dense GUI/Desktop paragraph into two short bullets (one for the no-auto-open rule, one for the faux-UI-label prohibition) to tighten the already-lean content.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanation of what ODP/Impress/PPTX are), with compact JSON examples, but the GUI/Desktop paragraph is a dense run-on packing several rules into one sentence that could be split, matching the score-4 anchor of efficient content with minor instances that could be trimmed rather than the fully-lean score-5.	4 / 5
Actionability	Provides two complete, copy-paste-ready JSON tool invocations (create and set_slides edit) covering the primary operations, but the alternative text-to-slide creation path using '---' separators is described in prose rather than shown as an executable example, leaving a minor gap that fits score-4 rather than the fully-covered score-5.	4 / 5
Workflow Clarity	The create/edit flow is clearly organized into sequenced subsections with code, but the set_slides edit operation overwrites all deck content (a batch/destructive operation) and there is no validation or verification checkpoint, so per the destructive/batch cap workflow clarity cannot exceed 3; it does not fit score-4 because the required validation checkpoint is absent.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed and no bundle files present, and the body is cleanly organized into an intro, a Workflow section with create/edit, and a Practical rules list, satisfying the simple-skill exception that allows a score of 5 with well-organized sections.	5 / 5
	Total	16 / 20 Passed

Description

78%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 strong: it explicitly states both what the skill does and when to use it, with concrete product/format triggers and a thoughtful PPTX boundary condition. Its main limitation is that the listed actions are generic lifecycle verbs rather than a fuller enumeration of presentation capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain (ODP/PPTX presentations) and three concrete actions (creating, opening, editing), but the actions are generic verbs and coverage is limited to deck lifecycle without other presentation tasks (layouts, comments, export), matching the score-3 anchor for domain plus 1-2 concrete actions that are not comprehensive.	3 / 5
Completeness	Explicitly answers both 'what' (creating, opening, or editing ODP/PPTX decks) and 'when' (Use when... plus the specific PPTX conditional) with concrete trigger phrases, matching the score-5 anchor; it does not fit score-4 because the 'when' is already explicit and specific rather than merely present.	5 / 5
Trigger Term Quality	Covers natural product/format terms users would say (LibreOffice Impress, ODP, PPTX, PowerPoint, presentations, decks) with good keyword coverage, but omits plain synonyms like 'slides'/'slide deck' in the description itself, fitting the score-4 anchor of good coverage with a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche anchored to LibreOffice Impress and ODP with a boundary condition for PPTX, but the PPTX/PowerPoint portion shares trigger space with a hypothetical PowerPoint-specific skill, giving minor overlap risk that fits score-4 rather than the minimal-risk score-5.	4 / 5
	Total	16 / 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/impress-presentations/SKILL.md
Commit: b22a144

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.