bento-slides

Create and edit Bento presentations — single-file .bento.html decks whose document is plain JSON in a "#bento-doc" script block. Use whenever the user wants a slide deck or presentation: starting from NOTHING (it downloads the latest Bento app from bento.page automatically), from source material, or by improving an existing .bento.html. Maps content to the right feature (charts, morph transitions, state slides, ken-burns, motion paths) instead of static text slides, then writes the document JSON in place. Full schema + recipes at https://bento.page/agents.md.

Quality

86%

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

81%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 tight, actionable body with a strong sequenced workflow and self-audit feedback loop for a destructive/edit operation. Main gaps are the external URL dependency for the full schema and a few trimmable asides.

Suggestions

Bundle the schema skeleton and key recipes into ./references/ so the skill is self-contained instead of requiring a live fetch of bento.page/agents.md.

Tighten the Windows-without-curl aside and the collab-key diversion, or move them into a reference file, to lift conciseness.

Add an inline minimal-valid-document example so authoring can proceed without first fetching the external URL.

Dimension	Reasoning	Score
Conciseness	Largely lean and efficient, assuming Claude's competence without explaining JSON or slides, but a few asides (the Windows-without-curl aside, the collab-key diversion) could be trimmed.	4 / 5
Actionability	Provides executable curl commands, exact escaping rules, and concrete element-shape guidance, but the full schema/recipes live behind an external fetch (bento.page/agents.md) rather than as copy-paste-ready inline content.	4 / 5
Workflow Clarity	A numbered 6-step workflow with a self-audit checklist feedback loop and an explicit render-and-verify validation step ('look at every slide before you report done'), appropriate for document manipulation.	5 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep external references (bento.page/agents.md, template decks) rather than bundled files, keeping the bulk schema out of SKILL.md; no references/, scripts/, or assets/ bundles exist.	4 / 5
	Total	17 / 20 Passed

Description

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

A strong, specific description in consistent third person that clearly states what it does and when to invoke it, with concrete feature mapping. The only soft spot is trigger breadth, which favors Bento vocabulary over lay synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Create and edit Bento presentations', 'Maps content to the right feature (charts, morph transitions, state slides, ken-burns, motion paths)', 'writes the document JSON in place') with comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (create/edit single-file .bento.html decks) and 'when' ('Use whenever the user wants a slide deck or presentation: starting from NOTHING..., from source material, or by improving an existing .bento.html') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Includes natural triggers ('Use whenever the user wants a slide deck or presentation', '.bento.html') but leans on Bento-specific jargon (ken-burns, state slides) rather than broader synonyms a novice would say.	4 / 5
Distinctiveness Conflict Risk	The .bento.html niche plus named Bento features (morph, state slides, ken-burns) give it a clear, distinct trigger surface with minimal overlap against other skills.	5 / 5
	Total	19 / 20 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: nyblnet/bento
Path: plugins/bento-slides/skills/bento-slides/SKILL.md
Commit: 231d3f0

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