slide-template

Use when the user asks to create slides with a specific style, wants to use or inspect a slide template by code, wants to see platform-provided slide template options before creating, describes a custom template style, provides a PPTX/PPT file to convert into a platform template, or wants to extract a template from an existing Super Magic slide project.

Quality

92%

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

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

The content is well-structured, actionable, and externalizes detailed workflows to real reference files with clear navigation. Its main weakness is mild verbosity in the contract and style-specificity sections that could be trimmed without losing clarity.

Suggestions

Tighten the PPTX-Derived Template Contract and Style Specificity bullet lists by merging redundant rules; some guidance (e.g., layout property placement) repeats across sections.

Add a short copy-paste-ready snippet for the common non-PPTX path (create_slide_project + asset copy) alongside the existing install_slides_template example to raise actionability.

Consider condensing the Decision section and Template Application Workflow step 10, which overlap on when to load creating-slides and template-preserving reuse.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely avoids explaining concepts Claude already knows, but several contract bullet lists and repeated guidance across workflow sections could be tightened; it is efficient with minor over-explanation.	4 / 5
Actionability	Provides concrete executable code (the install_slides_template snippet, the theme.css link tag) and specific tool calls with decision branches, but a few steps remain prose instruction without copy-paste-ready examples.	4 / 5
Workflow Clarity	Multi-step processes (Template Application Workflow, PPTX and Project conversion workflows) are clearly sequenced with explicit validation checkpoints — sanitize, ask_user confirmation, lightweight QA, and ZIP packaging confirmation — and feedback loops for sensitive assets.	5 / 5
Progressive Disclosure	The body acts as an overview with well-signaled one-level-deep references to real bundle files (pptx-template-workflow.md, project-template-workflow.md, custom-template-workflow.md), each confirmed present, keeping detail appropriately externalized.	5 / 5
	Total	18 / 20 Passed

Description

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

The description is comprehensive, trigger-rich, and clearly scoped to slide template management on the platform. It answers both what and when explicitly and is highly distinguishable from generic skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — create slides with a style, inspect a template by code, see platform template options, describe a custom style, convert a PPTX/PPT file, and extract a template from an existing project — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	An explicit 'Use when...' clause with concrete trigger phrases answers both what the skill does and when to invoke it, matching the anchor for clearly and explicitly answering both.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('create slides with a specific style', 'PPTX/PPT file', 'extract a template', 'Super Magic slide project') plus file extensions, covering synonyms and concrete triggers.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (platform slide templates) with distinct triggers such as PPTX conversion and Super Magic slide project extraction, minimizing overlap with unrelated skills.	5 / 5
	Total	20 / 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: dtyq/magic
Path: backend/super-magic/agents/skills/slide-template/SKILL.md
Commit: f9973c5

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