CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

powerpoint

Create, inspect, edit, template, render, and visually verify Microsoft PowerPoint .pptx presentations.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exemplary lean skill body: concrete commands, a validation-rich workflow with feedback loops, and clean structure that defers option details to the scripts' --help. The only minor gap is that input JSON formats (spec.json, edits.json) are not documented inline.

DimensionReasoningScore

Conciseness

The body is lean with zero concept explanations — no preamble about what PowerPoint is or how python-pptx works; every line is directive ("Never flatten a deck to images", "Check first and do not install missing dependencies silently"). Matches the 5 anchor: every token earns its place.

5 / 5

Actionability

Concrete executable commands are provided ("python3 -m pip install python-pptx" and four copy-paste-ready script invocations), but the formats of spec.json and edits.json are not shown and are deferred to --help. Mostly executable with minor gaps, matching the 4 anchor rather than the fully self-contained 5.

4 / 5

Workflow Clarity

The six-step workflow has explicit validation checkpoints ("re-read it to verify slide count and content", "Render every slide and inspect the output images with view_image"), a feedback loop ("Iterate until the deck is structurally and visually sound"), and a failure fallback ("If rendering is unavailable, report that limitation"). Clearly matches the 5 anchor.

5 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and no need for external reference files; the five helper references all point to real one-level-deep scripts (verified present in ./scripts/), with detailed options correctly deferred to --help. Per the simple-skill guideline this earns a 5.

5 / 5

Total

19

/

20

Passed

Description

75%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, highly specific description with strong distinctiveness, but it omits any 'when to use' trigger guidance, which caps completeness. Adding an explicit 'Use when...' clause with natural synonyms (slides, deck) would resolve both weaknesses.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions PowerPoint, .pptx, slides, decks, or presentation files."

Include natural synonyms such as "slides", "deck", or "slide deck" in the description itself rather than only in metadata keywords.

Consider mentioning speaker notes or templates in the trigger clause since editing/templating are named capabilities.

DimensionReasoningScore

Specificity

The description lists six concrete actions ("Create, inspect, edit, template, render, and visually verify") against a named domain, comprehensively covering the bundled helpers' capabilities. It exceeds the 4 anchor because there are no noticeable coverage gaps.

5 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the "when" is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

"Microsoft PowerPoint", ".pptx", and "presentations" are natural user terms, but common synonyms like "slides", "deck", or "slide deck" are absent from the description (they only appear in metadata keywords). Good coverage with a few natural terms missing, matching the 4 anchor rather than comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

"Microsoft PowerPoint .pptx presentations" carves out a clear niche with distinct triggers and minimal conflict risk with other skills. It clearly matches the 5 anchor rather than the 4 anchor's "minor overlap risk with closely related skills".

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

EKKOLearnAI/hermes-studio

Path

packages/ekko-agent/skills/powerpoint/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.