sharepoint-powerpoint

Create, edit, restyle, and review PowerPoint `.pptx` files fetched from SharePoint, with emphasis on style preservation, slide cloning, theme-aware updates, and rendered visual QA. Use when the user wants reliable slide edits that should match an existing deck's design language.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

70%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with a clear, validation-gated workflow and honest handling of absent tooling. Its weaknesses are mild redundancy across sections and a lack of concrete executable examples for the python-pptx/OOXML operations it recommends.

Suggestions

Collapse the standalone "SharePoint Routing" and "Blocking Conditions" sections into the Core Workflow to remove duplication and shorten the body.

Add one short executable python-pptx snippet (e.g., clone a slide and replace text-bearing shapes) so the recommended edit strategy is copy-paste ready.

Show the exact fetch/update calls in context (e.g., `sharepoint.fetch(path, download_raw_file=True)` and `sharepoint.update_file(...)`) instead of naming them inline.

Dimension	Reasoning	Score
Conciseness	Mostly lean and free of concepts Claude already knows, but SharePoint routing appears in Core Workflow steps 2/7/8 and again in its own "SharePoint Routing" section, and blocking/stop guidance is duplicated between step 8 and "Blocking Conditions" — it could be tightened.	2 / 3
Actionability	Names concrete tools (python-pptx, lxml, Pillow, LibreOffice, Poppler) and operations (fetch(download_raw_file=true), update_file) with an ordered fallback strategy, but offers no executable code and leaves the python-pptx/OOXML mechanics at an abstract "use X for Y" level.	2 / 3
Workflow Clarity	The 8-step Core Workflow is clearly sequenced with explicit validation checkpoints ("Perform visual QA", "compare the new slide to its neighbors") and stop conditions ("If style fidelity cannot be validated, stop"), backed by the Blocking Conditions list.	3 / 3
Progressive Disclosure	A single self-contained file organized into well-labeled sections with no nested references; it explicitly and honestly states no helper scripts are bundled rather than implying missing files.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 is concrete, third-person, and answers both what and when with explicit triggers and natural terminology. It carves a clear niche around SharePoint-hosted, style-sensitive PowerPoint edits.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Create, edit, restyle, and review PowerPoint `.pptx` files" with specific capabilities like "slide cloning, theme-aware updates, and rendered visual QA" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly states what ("Create, edit, restyle, and review...") and an explicit when ("Use when the user wants reliable slide edits that should match an existing deck's design language"), satisfying both halves.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered: "PowerPoint", "`.pptx`", "slides", "deck", "slide edits", "design language" — the kind of wording a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The SharePoint-plus-PowerPoint-style-fidelity niche is distinct and unlikely to trigger for generic deck or document skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/sharepoint/skills/sharepoint-powerpoint/SKILL.md
Commit: 11c74d6

Reviewed: 17 days 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.