officecli-pptx

Use this skill any time a .pptx file is involved -- as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions 'deck', 'slides', 'presentation', 'pitch', or references a .pptx filename.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

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 high-quality, deeply actionable skill body with strong workflows and explicit validation gates. The main weakness is progressive disclosure: everything lives in one large SKILL.md with no reference files, so large reference tables (color themes, font pairings) compete with the core operating instructions for context.

Suggestions

Move the 10-row color-theme table and 8-row font-pairing table into a references/ file (e.g. THEMES.md, FONTS.md) and link to them from the body, shrinking the always-loaded SKILL.md footprint.

Consider extracting the deck-level recipes (cover, chart slide, flowchart, KPI grid, decision tree) into a references/RECIPES.md so the main file reads as overview + workflow + QA.

If keeping the single-file form, add a short 'References' section header that explicitly states no external files are needed, so the absence of progressive disclosure reads as intentional rather than accidental.

Dimension	Reasoning	Score
Conciseness	Lean and almost entirely free of concepts Claude already knows — no 'what is a presentation' padding; every section earns its tokens with domain-specific traps (zsh globbing, \n interpretation, KPI fit math, false-positive alt-text). Slightly below a 5 because the 10-row color-theme table and 8-row font-pairing table are reference-heavy and could be trimmed or externalized.	4 / 5
Actionability	Copy-paste-ready, fully executable blocks throughout — Quick Start, plus deck-level recipes (cover, chart slide, flowchart, KPI grid, decision tree) with exact props, coordinates, and a batch heredoc pattern covering the common cases.	5 / 5
Workflow Clarity	A numbered Common Workflow (open → orient → build → format → close → QA), an explicit shape-of-every-build summary, and a rigorous QA section with Gate 1/2/2b/3 validation checkpoints and a mandatory fix-verify feedback loop (max 3 cycles) — exactly the validation discipline a file-writing skill needs.	5 / 5
Progressive Disclosure	Well-organized with clear section headers, but the file is a ~580-line monolith with no bundle files in references/scripts/assets and no one-level-deep references — content that could be split out (10 color themes, font pairings, deck-recipe catalog) is inlined rather than progressively disclosed.	3 / 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 exemplar description: concrete capabilities, comprehensive natural trigger terms, and an explicit 'Use when/Trigger whenever' clause that answers both what and when. Voice is imperative/third-person ('Use this skill any time...'), avoiding the penalized first/second-person forms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text... editing, modifying, or updating... combining or splitting slide files; working with templates, layouts, speaker notes, or comments' — giving comprehensive coverage of the .pptx domain.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated create/read/edit/split operations) and 'when' via the concrete 'Trigger whenever the user mentions...' clause with named trigger phrases.	5 / 5
Trigger Term Quality	Covers natural terms users say — 'deck', 'slides', 'presentation', 'pitch' — plus the '.pptx filename' / '.pptx file' extension form, giving comprehensive synonym and extension coverage.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to .pptx files with extension- and synonym-based triggers, occupying a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	20 / 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
skill_md_line_count	SKILL.md is long (587 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Team-Commonly/commonly
Path: backend/commonly-bundled-skills/officecli/skills/officecli-pptx/SKILL.md
Commit: e701dba

Reviewed: 1 day 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.