CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pptx-author

Build PowerPoint decks headless with python-pptx.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/finance/pptx-author/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a strong, executable guide: a robust self-validating setup, concrete conventions, and copy-paste Python covering deck creation and Excel-model binding. The main gaps are the absence of any bundle files (shared setup logic and the pitch-deck checklist are inlined) and no explicit validation of the saved output.

Suggestions

Move the shared environment setup into a scripts/ helper (e.g. scripts/setup-docs-env.sh) and invoke it in one line, since the block is identical to the microsoft-office/pdf skills.

Move the 13-slide pitch-deck checklist to references/pitch-deck-structure.md with a one-line pointer from the body.

Add an explicit output validation step after prs.save (e.g., re-open the .pptx with python-pptx and confirm the slide count) to close the workflow's one checkpoint gap.

DimensionReasoningScore

Conciseness

The body is directive and assumes competence ("Never transcribe numbers from memory or from a summary — open the workbook, read the named range"), with no padding explaining PowerPoint or how python-pptx works, matching "Efficient; minor instances of over-explanation that could be trimmed". Not 5 because the ~25-line commented venv-construction block and the provenance/attribution material are trimmable or movable overhead.

4 / 5

Actionability

Every example is complete, executable code with concrete paths: the bash setup block, the template-loading snippet, add_picture with Inches coordinates, the full deck skeleton ending in prs.save("./out/pitch-aurora.pptx"), and the openpyxl named-range resolver — together covering the common cases (setup, title/table/chart slides, model binding). Matches "Fully executable; copy-paste ready code or commands; specific examples cover the common cases"; nothing is pseudocode.

5 / 5

Workflow Clarity

A clear sequence is implied by section order — validated setup (the bash block self-checks imports), optional firm template, build slides, bind numbers to a recalculated workbook, save to ./out/, return the path — with the recalculation warning acting as a data checkpoint, matching "Clear sequence with most checkpoints present; minor validation gaps". Not 5 because the sequence is never enumerated and there is no validation of the saved output (e.g., re-opening the .pptx); not 3 because checkpoints do exist in setup and data binding.

4 / 5

Progressive Disclosure

The file is well-sectioned and navigable, but it is a ~190-line monolith with no bundle: the setup block is stated to be "the same block as the microsoft-office/pdf skills" and the 13-item pitch-deck checklist ("Not prescriptive, but useful as a starting skeleton") is inline reference material, matching "Some structure but could be better organized... content that should be separate is inline". Not 4 because the shared setup logic and checklist genuinely belong in a script/reference file; not 2 because headers are clear and nothing is a wall of text.

3 / 5

Total

16

/

20

Passed

Description

50%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 states a clear, single-sentence "what" with a concrete tool and mode, but contains no "Use when..." trigger clause and only thin natural-keyword coverage. It is serviceable but would miss requests phrased as "presentation", "slides", or ".pptx file".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a .pptx deck as a file artifact, a pitch deck, or presentation slides built headless — not for driving a live PowerPoint session."

Include natural synonyms and the file extension — "presentation", "slides", ".pptx" — so common user phrasing matches the description.

Name a second concrete capability (e.g., binding slide numbers to an Excel model, or applying a firm .pptx template) to raise specificity and distinctiveness versus the broader microsoft-office skill.

DimensionReasoningScore

Specificity

"Build PowerPoint decks headless with python-pptx" names the domain and one concrete action with its tool, matching the anchor "Names domain and 1-2 concrete actions, but not comprehensive". Not 2 because it does state a concrete action plus mode and tool rather than a bare generic verb, and not 4+ because only one action is listed (no editing, templating, or extraction capabilities).

3 / 5

Completeness

The "what" is clear ("Build PowerPoint decks headless with python-pptx") but there is no "Use when..." clause or equivalent trigger guidance in the description itself — the trigger guidance ("Use when you need to deliver a deck as a file artifact") lives only in the body, which caps completeness at 3 per the guidelines. Not 4 because the "when" is entirely absent from the evaluated text.

3 / 5

Trigger Term Quality

"PowerPoint" and "decks" are natural terms users would say, but common variations like "presentation", "slides", and the ".pptx" extension are missing ("python-pptx" is a tool name, not a file-extension trigger), matching "Some relevant keywords but missing common variations or synonyms". Not 4 because synonym coverage is too thin for "good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

"headless with python-pptx" carves a niche, but "PowerPoint decks" overlaps with the broader microsoft-office presentation skill (explicitly listed in related_skills), matching "Somewhat specific but could still overlap with similar skills". Not 4 because the description alone gives the model no cue to prefer this skill over a general presentation skill for a given request.

3 / 5

Total

12

/

20

Passed

Validation

81%

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

Validation — 13 / 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

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/finance/pptx-author/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.