slides

Create and edit .pptx presentation decks with PptxGenJS. Useful for sales decks, kickoff briefs, and design-system showcases.

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/slides/SKILL.md

Quality

Content

42%

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 well-structured but hollow catalogue stub: organization and the upstream pointer are good, yet it provides no executable PptxGenJS guidance and only a vague meta-workflow for installing the real skill. Actionability is the clear weakness.

Suggestions

Replace or augment the redirect with at least one executable PptxGenJS example (e.g., a minimal node script creating a deck and saving .pptx) so the skill is actionable on its own.

Remove the verbatim repetition of the frontmatter description in 'What it does' or replace it with genuinely new detail.

If the skill is intentionally a stub, add an explicit validation step (e.g., confirm the upstream bundle installed and the 'slides' skill resolves) to the install workflow.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept-explaining padding, but the 'What it does' section repeats the frontmatter description verbatim and the catalogue meta-explanation ('advertises the skill in Open Design so the agent discovers it during planning') could be tightened, so not every token earns its place.	2 / 3
Actionability	There is no executable guidance for the skill's actual purpose: the only code block is 'open https://github.com/openai/skills' (a browser open, not a pptx command) and the rest ('install the upstream bundle', 'ask the agent to invoke') is abstract redirection rather than instruction, matching the 'vague/abstract; describes rather than instructs' anchor.	1 / 3
Workflow Clarity	A loose meta-sequence exists (install upstream bundle, then invoke by name/trigger), but it describes acquiring the real skill rather than the pptx workflow itself and has no validation checkpoints, so it sits at 'steps listed but gaps' rather than a clear validated sequence.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no local bundle files (references/, scripts/, assets/ are empty) and is cleanly organized into 'What it does', 'Source', and 'How to use' sections with a single clearly-signaled one-level-deep upstream reference, which per the simple-skills guideline earns a 3.	3 / 3
	Total	8 / 12 Passed

Description

50%

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 concise and third-person with a clear domain, but it lists only two generic actions, omits common trigger variations, and lacks an explicit 'Use when...' clause, leaving every dimension at the mid anchor. It is adequate but not exemplary.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when creating or editing PowerPoint .pptx decks, sales decks, or slide presentations').

Expand the action list beyond 'create and edit' to specific concrete operations (e.g., add slides, apply themes, insert charts/images, export .pptx).

Include natural user variations like 'PowerPoint' and 'slides' alongside 'PptxGenJS' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('.pptx presentation decks with PptxGenJS') and two concrete actions ('Create and edit'), but stops at two generic verbs rather than listing multiple specific actions like extract/fill/merge, so it is not comprehensive enough for a 3.	2 / 3
Completeness	It clearly answers 'what' (create/edit .pptx decks) but 'when' is only implied via 'Useful for...' rather than an explicit 'Use when...' clause, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant natural terms appear ('.pptx', 'presentation decks', 'sales decks', 'kickoff briefs') but common variations a user would say ('PowerPoint', 'slides') are absent and 'PptxGenJS' is library jargon, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The .pptx/PptxGenJS niche is somewhat specific, but the description lacks explicit trigger phrasing and could still overlap with a generic presentation/slides skill, matching the 'somewhat specific but could still overlap' anchor rather than the distinct-trigger anchor at 3.	2 / 3
	Total	8 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/slides/SKILL.md
Commit: a2ba3ee

Reviewed: about 7 hours 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.