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.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

77%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-structured, highly actionable deck-generation workflow with explicit validation checkpoints and excellent progressive disclosure; its main weakness is verbosity in the philosophy and reference-works sections that does not earn its tokens.

Suggestions

Trim or move the 'Core design principles (philosophy)' and 'Reference works' sections into a reference file, keeping only the rules that change generation behavior in SKILL.md.

Inline one minimal paste-ready slide section (e.g. a cover) so the core action is executable without opening layouts.md first.

Tighten the image-convention block into a compact table; the prose around 'how to replace' and 'what if there are no images' can be shortened.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and skill-specific (class-name pre-check, theme-rhythm rules, pitfall list), but it carries padded sections such as 'Core design principles (philosophy)', 'Reference works', and a verbose image-convention explanation that could be trimmed.	3 / 5
Actionability	Provides concrete executable commands (mkdir/cp/open, grep self-checks), explicit class-name lists, CSS variable names, and image-ratio tables; the minor gap is that the actual slide HTML skeletons live in layouts.md rather than inline.	4 / 5
Workflow Clarity	A clear Step 0–6 sequence with explicit validation checkpoints (3.0 class pre-check, 3.0.5 theme-rhythm self-check, Step 4 checklist), grep-based verification, and feedback loops (add missing class to template, re-check) for a file-writing workflow.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview with a 'Resource file tour' file tree and a numbered 'Recommended loading order'; all references (styles.md, layouts.md, themes.md, components.md, checklist.md, template.html, example-slides.html) are one level deep, clearly signaled, and verified to exist.	5 / 5
	Total	17 / 20 Passed

Description

61%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 scopes a clear marketing/gtm niche and lists several domain trigger terms, but it never names the artifact it produces (an HTML deck) and lacks an explicit 'Use when…' trigger clause, capping completeness and leaving a gap in trigger-term coverage.

Suggestions

State explicitly what the skill produces, e.g. 'Generates a single-file HTML marketing/GTM deck that binds launches, campaigns, events, and brand plans to growth and pipeline outcomes.'

Add an explicit trigger clause: 'Use when the user asks for a marketing deck, GTM slides, or an annual marketing plan presentation.'

Include the natural artifact terms (deck, slides, presentation, HTML) so the skill triggers when users ask for slide-style output.

Dimension	Reasoning	Score
Specificity	Names the marketing/gtm domain and a couple of concrete actions ('bind launches, campaigns, events, and brand plans to growth and pipeline outcomes', 'approve launch plan, campaign budget, or GTM motion'), but the actions are abstract and it never states the artifact produced (a deck).	3 / 5
Completeness	There is no explicit 'Use when…' trigger clause (capped at 3 per guideline); the 'what' is outcome-focused rather than artifact-focused, and 'when' is only weakly implied via 'For marketing and gtm work' and the named core query.	3 / 5
Trigger Term Quality	Good natural keyword coverage for the domain (launches, campaigns, events, brand plans, growth, pipeline, marketing, gtm, annual-marketing-plan), but it omits the core artifact terms users would actually say (deck, slides, presentation, HTML).	4 / 5
Distinctiveness Conflict Risk	The brand-to-revenue / marketing-gtm niche with the annual-marketing-plan core query is mostly distinct, but because it never names the artifact type there is minor overlap risk with generic slide/presentation skills.	4 / 5
	Total	14 / 20 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: nexu-io/open-design
Path: design-templates/guizang-ppt/SKILL.md
Commit: 1a7a23d

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