impress-presentations

Create, open or edit slides: ODP default; PPTX for PowerPoint compatibility.

Quality

79%

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

85%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 lean, actionable skill body: concrete tool-call examples for create and edit, a clear ODP-default vs PPTX-compatibility decision rule, and explicit UI-behavior guardrails. The only notable gaps are minor duplication of the Desktop rule and the absence of an example for the 'open' action.

Dimension	Reasoning	Score
Conciseness	The body is lean: two compact JSON examples plus short rule lists, with no explanation of concepts Claude already knows. Not score 5 because the do-not-open-Desktop rule is stated twice (paragraph 2 and again in 'Practical rules'), which could be trimmed to one statement; not score 3 because padding is minimal and every section carries task-specific information.	4 / 5
Actionability	Both 'Create' and 'Edit slides' are shown as complete, copy-paste-ready office_artifact JSON calls with concrete fields (format, content, slides array with bullets). Not score 5 because the description promises 'open' but no example shows it, and how file_id is obtained is never stated; not score 3 because the provided examples are fully executable, not pseudocode.	4 / 5
Workflow Clarity	This is a simple, single-purpose skill (~45 lines): the format-selection rule (ODP default, PPTX only for compatibility), create, and edit paths are each unambiguous, so the simple-skill exception applies. Not score 4 because the two operations and their preconditions ("must save the deck") are fully specified with no gaps; the operations are non-destructive, so no validation checkpoints are required.	5 / 5
Progressive Disclosure	The body is under 50 lines, needs no external references, and no references/scripts/assets directories exist — consistent with the body, which cites none. Sections are well-organized (format rule, Workflow with examples, Practical rules), so the short-skill exception for a 5 applies. Not score 4 because nothing that belongs in a separate file is inlined and navigation within the single file is clear.	5 / 5
	Total	18 / 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 concise, specific description with good trigger vocabulary, but it omits an explicit 'Use when...' clause, leaving the invocation conditions implied rather than stated. Adding when-to-use guidance would raise completeness without sacrificing brevity.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for a presentation, slides, or a deck.'

Include the natural terms 'presentation' and 'deck' in the description itself rather than only in the frontmatter triggers list.

Clarify what 'open' means (e.g., opening a provided .odp/.pptx file) to close the specificity gap.

Dimension	Reasoning	Score
Specificity	"Create, open or edit slides" lists several specific concrete actions in the presentation domain, with format guidance ("ODP default; PPTX for PowerPoint compatibility") adding further precision. Not score 5 because coverage is thin on what 'open' entails and no analysis/export actions are named; not score 3 because three distinct actions plus format policy exceed the 1-2-action anchor.	4 / 5
Completeness	The 'what' is clear (create, open, edit slides with ODP default and PPTX compatibility), but there is no 'Use when...' clause or equivalent explicit trigger guidance — when to use it is only weakly implied by the format note. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3; it is not 2 because the 'what' is concrete and specific, and not 4 because the 'when' is absent rather than merely imprecise.	3 / 5
Trigger Term Quality	Includes natural terms users say: "slides", "PowerPoint", plus format-specific "ODP" and "PPTX". Not score 5 because common natural phrases "presentation", "deck", and "Impress" are absent from the description itself; not score 3 because keyword coverage is good, spanning both user-natural and file-format vocabulary.	4 / 5
Distinctiveness Conflict Risk	Clearly scoped to presentations with distinct format triggers (ODP, PPTX, PowerPoint), so it is unlikely to fire for the wrong skill. Not score 5 because "slides"/"PowerPoint" could overlap with other office-document or generic presentation skills; not score 3 because the format-specific niche makes conflicts unlikely.	4 / 5
	Total	15 / 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: e3051fb

Reviewed: 10 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.