CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

slide-template-replacement

Replace the visual template of an existing HTML slide project while preserving its content. Use when a user asks to change, apply, or replace a PPT template for an existing project, a specific slide, or an explicit page range and provides a template_code or a template selected from the template picker. Do not use for creating templates or converting native PPTX files.

Quality

90%

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

88%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 operational skill body: exact tool calls, file names, attributes, and naming rules, sequenced into a clear pipeline with an explicit pre-save verification checklist and failure-reporting path. The only weaknesses are minor redundancy with the frontmatter description in the intro and reliance on an external skill for installation details.

DimensionReasoningScore

Conciseness

The body is dense with operational rules and explains no concepts Claude already knows, but the opening paragraph restates the frontmatter description ("Use this skill when the input asks to apply an existing platform template...") and "Do not load `slide-template-maker`. This skill only applies an existing platform template" duplicates the description's exclusion. These minor trimmable instances match the efficient-with-minor-over-explanation anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Fully actionable instruction-only guidance: exact tool calls (`install_slides_template` with the exact `template_code`, `ask_user` with enumerated choice strings), exact files to read (`template.json`, `theme.css`, `visual-spec.md`), concrete attributes (`data-width`, `data-ppt-step`, `data-ppt-effect`), and a worked naming example (`季度汇报-商务蓝-2.html`) with collision rules. Specific examples cover the common deck/slide/page-range cases.

5 / 5

Workflow Clarity

The sections sequence a complete pipeline (input validation → save mode → install → apply → verify and report), and the Verify section is an explicit pre-save checklist (slide count, page scope, canvas size, content presence, resource references, step-count diff requiring explanation) for what are destructive/batch file edits. Error recovery is specified: on failure, do not silently overwrite and report the concrete failure plus retry/recovery path.

5 / 5

Progressive Disclosure

The body is well-sectioned with no monolithic wall, and the one external pointer ("Reuse the installation and resource rules from `slide-template`") is clearly signaled with the key steps still enumerated inline. It falls short of 5 because the file is ~60 lines (past the simple-skill threshold where sections alone suffice) and the installation details live in another skill rather than a local reference, a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

87%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: it states one precisely scoped capability, gives explicit use-when triggers covering all three scopes, and carves out clear exclusions. Trigger coverage is good but could add a few natural synonyms.

DimensionReasoningScore

Specificity

"Replace the visual template of an existing HTML slide project while preserving its content" names the domain and a precise action with a preservation constraint, and the scope variants (whole project, single slide, page range) are concrete. It stays below 5 because only one core action is enumerated rather than multiple specific capabilities, and above 3 because the single action is scoped precisely enough to rival multi-action descriptions in coverage.

4 / 5

Completeness

Both halves are explicit: the what ("Replace the visual template... while preserving its content") and the when ("Use when a user asks to change, apply, or replace a PPT template... and provides a template_code"), with concrete trigger conditions and an explicit exclusion clause. This clearly matches the anchor for explicitly answering both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural trigger phrases are present: "change, apply, or replace a PPT template", "a specific slide", "an explicit page range", plus "template_code" and "template picker". Not 5 because common synonyms like "switch template" or file extensions (e.g. .html/.pptx as positive triggers) are absent, leaving a few natural terms uncovered.

4 / 5

Distinctiveness Conflict Risk

A clear niche (applying existing platform templates to HTML slide projects) with distinct triggers and explicit negative boundaries ("Do not use for creating templates or converting native PPTX files") that separate it from adjacent skills. Conflict risk with other skills is minimal.

5 / 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-replacement/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.