CtrlK
BlogDocsLog inGet started
Tessl Logo

pptx

Create, edit, review, and finalize editable Microsoft PowerPoint .pptx presentations. Use for new decks, source- or template-based presentations, targeted slide edits, charts, tables, images, speaker notes, visual QA, and legacy .ppt conversion. Do not use for HTML/browser presentations, Google Slides, or live Microsoft PowerPoint control.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

A well-crafted, genuinely useful skill body: a clear five-stage framework, concrete CLI commands, honest caveats about renderer fidelity, and disciplined external reference gating. Minor gaps are a slightly repeated anti-pipeline theme and the absence of an explicit error-recovery feedback loop.

Suggestions

State the "tools are independent, not a pipeline" point once and reference it, rather than re-deriving it in both the intro and the Review section.

Add one short worked python-pptx or OOXML edit snippet under Build so the core editing task has an executable starting point like the CLI ops do.

Spell out a validate→fix→re-validate retry loop (e.g., on `validate` failure, fix the package part and re-run before delivering) to make the feedback path explicit for destructive/package edits.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explaining of what PowerPoint or python-pptx is), but the "not a fixed pipeline / independent, not a required pipeline" theme is restated across the intro and Review section and could be tightened once.

4 / 5

Actionability

Provides copy-paste-ready bash for validate, render, compare, convert-legacy, and deliver with full flags, but the core Build/edit work is given as approach guidance ("python-pptx, PptxGenJS, direct OOXML...") rather than a worked executable example.

4 / 5

Workflow Clarity

The Understand→Build→Review→Specialized→Deliver sequence is clear with validation steps (validate, render, compare) and source-protection safeguards, but no explicit validate→fix→re-validate feedback loop is spelled out for the XML/package manipulation the skill involves.

4 / 5

Progressive Disclosure

Overview is well-structured into stages and the two references (powerpoint-specifics.md, legacy-ppt-conversion.md) are one level deep, gated with "only when relevant" / "when handling .ppt", and verified to exist as real files.

5 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: third-person voice, concrete actions, natural trigger terms with synonyms and file extensions, clear what/when guidance, and an explicit out-of-scope boundary that lowers conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Create, edit, review, and finalize" plus "targeted slide edits, charts, tables, images, speaker notes, visual QA, and legacy .ppt conversion" — giving comprehensive coverage rather than vague verbs.

5 / 5

Completeness

Explicitly answers both what ("Create, edit, review, and finalize editable Microsoft PowerPoint .pptx presentations") and when ("Use for new decks, source- or template-based presentations...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural terms and synonyms users say ("new decks", "presentations", "slide edits") alongside file extensions (.pptx, .ppt), matching the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

The PowerPoint/.pptx niche is distinct and the explicit boundary "Do not use for HTML/browser presentations, Google Slides, or live Microsoft PowerPoint control" minimizes wrong-skill triggering.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
OpenBMB/PilotDeck
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.