ppt-keynote

Apple Keynote-quality slides, one card per screen, with keyboard left/right navigation.

Quality

57%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/ppt-keynote/SKILL.md

Quality

Content

65%

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 lean, concrete spec that respects token budget, but it describes the keyboard-navigation JavaScript rather than providing executable code and reads as a feature checklist without workflow checkpoints. Organization is flat rather than sectioned.

Suggestions

Provide an executable JavaScript snippet for the ArrowLeft/ArrowRight/space + hash navigation instead of describing it in prose.

Group the bullets into labeled sections (Structure, Typography, Navigation, Layout) to improve organization and progressive disclosure.

Add a short verification step (e.g. open index.html and confirm arrow-key + hash navigation works) to give the single-task workflow an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is a terse 9-line bullet spec (e.g. "整体宽 1280 高 720", "标题 text-7xl font-semibold tracking-tight") with no concept explanations or padding, matching the lean score-3 anchor; every token earns its place.	3 / 3
Actionability	Concrete tokens are present (class names, dimensions, Tailwind classes), but the navigation logic is described as instruction ("加一段 JavaScript 监听 ArrowLeft / ArrowRight / 空格键切换 slide") rather than executable code, matching 'some concrete guidance but incomplete'; not score 3 because the JS is not copy-paste ready, not score 1 because specific class/size guidance is given.	2 / 3
Workflow Clarity	The bullets form a feature checklist rather than a sequenced workflow, and there is no validation/preview checkpoint, matching 'steps listed but validation gaps'; not score 3 because no explicit checkpoints, not score 1 because the spec is concrete and the single task is fairly unambiguous.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no external bundle files, but the body is a single flat unsectioned list rather than organized sections, matching 'some structure but could be better organized'; not score 3 because it lacks sectioned organization, not score 1 because it is compact with no nested references.	2 / 3
	Total	9 / 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 conveys a clear, specific output style but stops short of an explicit "Use when" trigger and lacks natural term variations. It is competent but generic enough to risk overlap with other presentation skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a presentation, slide deck, or pitch slides, or wants Keynote-style visuals.'

Broaden trigger terms in the description itself (presentation, deck, slides, pitch) rather than relying on tags.

Enumerate concrete actions (build a deck, lay out one-card-per-screen slides, wire keyboard navigation) to raise specificity.

Dimension	Reasoning	Score
Specificity	Quotes "Apple Keynote-quality slides, one card per screen, with keyboard left/right navigation" name the domain and a couple of concrete attributes, but do not list multiple distinct actions (e.g. build, theme, animate, export), matching the score-2 anchor; not score 3 because no enumerated action list, not score 1 because actions are named rather than abstract.	2 / 3
Completeness	It clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2; not score 1 because the "what" is concrete, not score 3 because the "when" is only implied.	2 / 3
Trigger Term Quality	"slides" is a natural term a user would say, but common variations like presentation, deck, or PowerPoint are absent from the description (present only in tags), matching 'some relevant keywords but missing common variations'; not score 3 due to thin coverage, not score 1 because at least one natural term appears.	2 / 3
Distinctiveness Conflict Risk	The phrasing "Keynote-quality... one card per screen, with keyboard left/right navigation" is a fairly specific niche, yet the trigger "slides" could still overlap with generic deck/presentation skills, matching the score-2 anchor; not score 3 because triggers are not distinct enough, not score 1 because the niche is recognizable.	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/ppt-keynote/SKILL.md
Commit: a2ba3ee

Reviewed: 3 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.