slide-template

Use when the user asks to create slides with a specific style, wants to see available PPT templates before creating, describes a custom template style, or wants to extract a template from an existing PPT project.

Quality

93%

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

Quality

Content

87%

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

A well-structured, highly actionable skill body that leverages progressive disclosure to keep the overview lean while pointing to verified bundle files. The main gap is the absence of an explicit validation/retry checkpoint on the core slide-generation step, which leaves workflow clarity at the 2 level.

Suggestions

Add an explicit verify checkpoint after step 8 (e.g., confirm each generated slide is fixed 1920x1080, links local theme.css, and has one visual anchor) with a fix-and-retry loop, mirroring the custom workflow's quality gate.

Tighten the Decision section's "recommend 3-5 built-in templates with ask_user" by stating how the 3-5 are selected from the catalog (e.g., match trigger keywords in the table) so the branching step is fully deterministic.

Consider collapsing the duplicate "Do not link preview.html / skill files outside the project" guidance (steps 3, 4, 9) into one authoritative rule to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Dense, assumes Claude's competence, and avoids explaining concepts Claude already knows; the long 24-row template table is lookup content central to the skill rather than padding, and every token earns its place.	3 / 3
Actionability	Concrete, executable guidance throughout — exact tool calls (read_files, shell_exec cp, create_slide_project, image_search, generate_images), absolute paths, and a copy-paste <link> snippet — not abstract description.	3 / 3
Workflow Clarity	The built-in workflow has a clear 9-step sequence with a pre-generation summary checkpoint and the custom workflow has a quality-gate feedback loop, but the core slide-generation path (step 8) lacks an explicit validate-then-proceed checkpoint for what is effectively a batch output operation, capping it at the 2 anchor.	2 / 3
Progressive Disclosure	SKILL.md is an overview that signals one-level-deep references to real bundle files (references/custom-template-workflow.md and assets/templates/<dir>/{visual-spec.md,theme.css,preview.html}, all verified present), organized via a table and clear section headings.	3 / 3
	Total	11 / 12 Passed

Description

100%

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, trigger-rich description that names concrete capabilities and explicit use conditions within a single well-scoped niche. Its only minor weakness is that capability statements are folded into the "Use when" clause rather than stated separately, but both what and when are clearly covered.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "create slides with a specific style", "see available PPT templates", "describes a custom template style", "extract a template from an existing PPT project" — rather than vague language.	3 / 3
Completeness	An explicit "Use when..." clause supplies the when, and the embedded verbs (create/see/describe/extract) supply the what, satisfying both halves; not capped at 2 since the Use-when trigger guidance is present.	3 / 3
Trigger Term Quality	Natural phrasings a user would actually say ("create slides with a specific style", "see available PPT templates", "extract a template from an existing PPT project") with good coverage of the skill's entry points.	3 / 3
Distinctiveness Conflict Risk	Niche is clearly scoped to PPT slide templates and style extraction; the triggers are specific enough to avoid firing for unrelated slide-editing or document skills.	3 / 3
	Total	12 / 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: dtyq/magic
Path: backend/super-magic/agents/skills/slide-template/SKILL.md
Commit: 41d7ef4

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