CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

slide-template-maker

Create, reconstruct, extract, or update reusable HTML slide templates from presentation files, images, screenshots, HTML, text style briefs, existing template folders, or Super Magic slide projects. Use when the user asks to make a slide/PPT template, convert a PPT/PPTX into a template, recreate a visual style as a template, extract reusable layouts, or improve an existing template.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

An exceptionally actionable, well-sequenced operations manual: complete executable code for every tool, explicit validation gates, retry loops, and a blocked-report protocol. Its main costs are repetition of the same anti-failure guardrails and duplication of fidelity rules between the body and quality-guidelines.md, which inflate token usage without adding information.

Suggestions

State the 'finalize always runs regardless of source type' guardrail once (e.g., in Source vs pipeline) and remove its repetitions from Workflow step 7, the end of Required tool sequence, and the Blocked Report false-blocker paragraph; likewise consolidate the repeated 'Do not say the template is complete' warnings.

Move the shared fidelity rules (surface class per background scheme, 1.8% body-text floor, measured margins/alignment axis) fully into references/quality-guidelines.md and keep only one-line pointers in Source Fidelity Rules and the Completion Gate, so the body stops duplicating the reference.

Trim the Intake Checkpoint by removing question-dropping rules that are restated in the Workflow section, keeping a single authoritative list of when shape and asset questions can be skipped.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, project-specific rules and teaches no basic concepts, but the same guardrails repeat: the false-blocker warning ("That is a false blocker. Skipping prepare for those sources is correct; skipping finalize is not") recurs in Source vs pipeline, Workflow step 7 ("skip beat 6"), Required tool sequence ("Do not skip this call because the source is not PPTX"), and Blocked Report; "Do not say the template is complete" appears roughly four times. Mostly efficient but could be meaningfully tightened, fitting anchor 3.

3 / 5

Actionability

Fully executable, copy-paste-ready Python snippets cover every tool call (taxonomy query, create, prepare/review in batches of 6, asset decisions, finalize, visual QA), with explicit placeholder-substitution instructions ("replace `category_code` and `tag_codes` with codes you actually read from the catalog"), batch limits, defaults, and error handling via `raise SystemExit(result.content)` — matches anchor 5.

5 / 5

Workflow Clarity

An 11-step numbered main path with an Intake Checkpoint before creation, a Completion Gate checklist, explicit feedback loops ("If a dedicated tool fails, print `result.content`, fix the arguments, and retry the same tool"; "Fix and finalize again if needed"), and a structured Blocked Report — clear sequence with validation steps, error-recovery loops, and checklists, matching anchor 5.

5 / 5

Progressive Disclosure

The Source vs pipeline table cleanly routes each source type to a real, one-level-deep evidence reference (all cited paths exist in references/), and the 68KB taxonomy catalog is properly externalized. However, the ~4,000-word body duplicates fidelity rules that also live in references/quality-guidelines.md (surface classes per background scheme, the 1.8% body-text floor, measured margins), making it more manual than overview — good structure with minor organization gaps, anchor 4 rather than a lean anchor-5 overview.

4 / 5

Total

17

/

20

Passed

Description

88%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 description: concrete, third-person, and explicitly covering both capabilities and trigger conditions with natural user phrasing and file extensions. Its only weaknesses are a few missing common synonyms (PowerPoint, deck) and an unstated boundary against the sibling template-application skill.

DimensionReasoningScore

Specificity

Lists four concrete actions ("Create, reconstruct, extract, or update") across seven enumerated source types ("presentation files, images, screenshots, HTML, text style briefs, existing template folders, or Super Magic slide projects") — comprehensive coverage of operations and inputs, matching the anchor-5 breadth rather than anchor 4's 'minor gaps'.

5 / 5

Completeness

Explicitly answers both 'what' (first sentence enumerating the actions and sources) and 'when' ("Use when the user asks to make a slide/PPT template, convert a PPT/PPTX into a template, recreate a visual style as a template, extract reusable layouts, or improve an existing template") with concrete trigger phrases — a clear anchor-5 match.

5 / 5

Trigger Term Quality

Good natural coverage with extensions ("make a slide/PPT template", "convert a PPT/PPTX into a template", "extract reusable layouts", "improve an existing template"), but a few common user terms are missing — 'PowerPoint', 'deck', and 'presentation template' never appear, so it fits anchor 4 ('a few natural terms missing') rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The template-creation/reconstruction niche is clear and verbs are distinct from template application, but "make a slide/PPT template" carries minor overlap risk with closely related slide-creation and template-browsing skills (the body's own 'Load `slide-template` for those tasks' boundary is not reflected in the description), fitting anchor 4 rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

18

/

20

Passed

Validation

100%

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-maker/SKILL.md

Reviewed

Table of Contents

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.