CtrlK
BlogDocsLog inGet started
Tessl Logo

powerpoint

Create, read, edit .pptx decks, slides, notes, templates.

63

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/productivity/powerpoint/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 exceptionally actionable, well-sequenced skill body with strong validation feedback loops and clear script navigation; its only weakness is conciseness/structure tradeoff — some long inline sections could be offloaded to reference files.

DimensionReasoningScore

Conciseness

The body is dense, high-signal footgun guidance that assumes Claude's competence (e.g., 'The model knows the API; these are the footguns') with only one justified format note ('A .pptx is a ZIP archive of XML files'); not a 5 because the Design Ideas palette/typography sections, while useful, could be trimmed for token efficiency.

4 / 5

Actionability

Fully executable throughout — copy-paste bash blocks, exact script invocations with flags ('add_slide.py deck.pptx slide2.xml -o out.pptx'), and precise API values ('color: "FF0000"', 'dataLabelPosition must be ctr, inEnd, or inBase') matching the 'fully executable, copy-paste ready, covers common cases' anchor.

5 / 5

Workflow Clarity

Multi-step workflows are explicitly sequenced with validation checkpoints and feedback loops — 'Do all structural work before editing content', 'After writeFile(), run validate.py', and the QA loop 'After fixes, rerun all four commands'; the QA section functions as a checklist, matching the 5 anchor.

5 / 5

Progressive Disclosure

Scripts are real, one-level-deep, and clearly signaled via a Scripts table plus inline references; the body is well-organized with headers and a Quick Reference table; not a 5 because substantial material (gotchas, Design Ideas) is inlined in SKILL.md rather than split into separate reference files.

4 / 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, concrete capabilities statement with good natural keywords and a clear PowerPoint niche, but it omits any explicit 'when to use' trigger guidance, which caps completeness at 3.

Suggestions

Add a 'Use when ...' clause listing trigger phrases (e.g., 'Use when the user mentions decks, slides, presentations, pitch decks, or .pptx/.potx files').

Include the synonym 'presentation' and 'pitch deck' alongside 'decks' and 'slides' to round out trigger-term coverage.

Optionally mention charts and speaker notes explicitly to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Quotes 'Create, read, edit .pptx decks, slides, notes, templates' — three concrete verbs across four concrete objects, matching the 'lists several specific actions; minor gaps' anchor; not a 5 because charts and design QA from the body are absent.

4 / 5

Completeness

The 'what' is clear ('Create, read, edit .pptx decks, slides, notes, templates') but there is no 'Use when...' or equivalent trigger clause, so per the rubric cap completeness stays at 3 rather than 4.

3 / 5

Trigger Term Quality

Includes natural terms 'decks', 'slides', 'notes', 'templates' plus the '.pptx' extension, but misses common synonyms like 'presentation' and 'pitch deck', fitting the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The .pptx/deck/slide niche is clearly distinct from sibling docx/xlsx/pdf skills, but the absence of an explicit trigger clause and minor overlap with .potx templates keep it just below the 5 anchor.

4 / 5

Total

15

/

20

Passed

Validation

75%

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

Validation12 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 8 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository
NousResearch/hermes-agent
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.