CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

magazine-web-ppt

For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.

63

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./design-templates/guizang-ppt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is a well-engineered operating manual: fully executable steps, explicit pre-flight checks and self-check loops, and a clean one-level-deep reference structure with a documented loading order. Its only real weakness is redundancy — several rules appear two or three times across the body and checklist.md — which costs tokens without adding information.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive — tables, hard rules, exact commands — and does not explain concepts Claude already knows. It falls short of anchor 5 because of duplication (image-ratio and title rules repeated across Step 3.2, Step 4, and checklist.md) and marginal sections ("Reference works", editorial asides like "this is the source of all generation problems").

4 / 5

Actionability

The guidance is copy-paste executable throughout: exact `mkdir`/`cp`/`open` commands, a placeholder-replacement table with a grep verification step, a paste-ready layout catalog, explicit class-name lists, per-scenario image-ratio rules, and self-check grep commands. Every referenced file and section (Pre-flight list, P0 checklist, theme-color block, `[必填]` placeholder) was verified to actually exist in the bundle.

5 / 5

Workflow Clarity

Steps 0–6 are clearly sequenced with explicit validation checkpoints and feedback loops: the Step 3.0 class pre-check before writing slide code, the "grep for [必填]" check after copying the template, the theme-rhythm self-check (`grep 'class="slide' index.html`), and a final item-by-item pass against checklist.md. Error-recovery guidance (what to do when a class is missing, when an image filename changes) is explicit.

5 / 5

Progressive Disclosure

SKILL.md is an overview with details correctly split into five one-level-deep reference files (styles, themes, layouts, components, checklist) plus two assets, each clearly signaled at the point of need and summarized in a "Resource file tour" with a recommended loading order. All referenced paths exist and no reference chains deeper than one level.

5 / 5

Total

19

/

20

Passed

Description

57%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 orients around a clear scenario (annual-marketing-plan, GTM) with natural trigger keywords, but it obscures the skill's core capability — generating a styled single-file HTML slide deck — behind outcome framing and buzzword phrases like "GTM strategy lead judgment" and "buyer-ready proof". It lacks an explicit 'Use when' clause and output-format trigger terms, capping completeness and specificity at mid-scale.

Suggestions

State the concrete deliverable up front, e.g. "Generates a single-file HTML horizontal-swipe deck..." so the 'what' is unambiguous.

Add an explicit trigger clause: "Use when the user needs an annual-marketing-plan, launch plan, or campaign/GTM deck."

Add natural trigger synonyms users would say — "go-to-market", "marketing plan", "deck", "slides" — and trim buzzword phrases like "GTM strategy lead judgment".

DimensionReasoningScore

Specificity

The description names the domain ("marketing and gtm work") and lists concrete objects ("launches, campaigns, events, and brand plans"), but the action verbs are generic strategy-speak ("bind ... to growth and pipeline outcomes") and it never states the actual deliverable — a single-file HTML deck. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) better than anchor 4, which requires several specific actions with only minor gaps.

3 / 5

Completeness

The 'what' is only implied — the description frames judgment and outcomes ("approve launch plan, campaign budget, or GTM motion") but omits what the skill actually produces — and the 'when' is a weak "For marketing and gtm work" framing with no explicit 'Use when' clause, which caps this dimension at 3 per the rubric guidelines. This is not a 4 because anchor 4 requires both a clear 'what' and a more explicit 'when', and the 'what' here is genuinely unclear.

3 / 5

Trigger Term Quality

It includes natural keywords a marketing user would say — "launches, campaigns, events, brand plans, growth, pipeline", and the core query "annual-marketing-plan" — which users would naturally voice. It falls short of anchor 5 because common variations are missing: "go-to-market" spelled out, and any output-format terms like "deck", "slides", or "presentation".

4 / 5

Distinctiveness Conflict Risk

Niche phrases like "annual-marketing-plan", "GTM motion", and "campaign budget" give it a recognizable niche, but broad terms like "launch", "campaign", and "pipeline" appear in many other marketing/presentation skills and could trigger it for the wrong one. This sits between anchor 3 (somewhat specific, could still overlap) and anchor 4 (mostly distinct); the generic single-word terms keep it at 3.

3 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

nexu-io/open-design

Path

design-templates/guizang-ppt/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.