deck-guizang-editorial

Editorial magazine meets e-ink: 10 layouts and 5 palettes (Ink, Indigo Porcelain, Forest Ink, Kraft Paper, Dune).

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/deck-guizang-editorial/SKILL.md

Quality

Content

80%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 an exemplary dense template spec: exact palettes, layout anatomy, typography, prohibitions, and interaction behavior with zero padding. Its only structural weakness is the absence of an explicit assembly workflow and validation steps — the implied process (pick palette, pick layouts, build) must be inferred from section order.

Dimension	Reasoning	Score
Conciseness	The ~28-line body is pure specification: exact hex values (#0a0a0b), concrete sizes (8.5-10vw, 11px letterspacing 0.12em, 26vh/22vh grids), font names, and hard prohibitions ("严禁: 渐变 / drop-shadow / 圆角..."). Every token earns its place with no explanation of concepts Claude already knows, matching the 'lean and efficient' anchor.	5 / 5
Actionability	Guidance is mostly executable — each layout has concrete anatomy (L01 hero + kicker + subtitle + lead paragraph + metadata row; L09 1:1 split with left column opacity .55), and interaction is specified (keyboard ←/→, hash sync, single-file HTML). It falls short of anchor 5 because there is no example HTML snippet and a few directives remain aesthetic rather than executable ("纸感印刷", "杂志感细节").	4 / 5
Workflow Clarity	There is no explicit generation sequence (choose one palette → select layouts per user content → assemble single-file HTML) and no validation checkpoints; ordering is only implicit in the section structure (palettes → layouts → details). The content-count guidance ("短内容 6-12 张起步") partially sequences the task, matching anchor 3's 'sequence present but checkpoints missing or implicit' rather than anchor 4.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files (references/, scripts/, assets/ do not exist), and it has no need for external references; the four clearly labeled sections (【意图】【调色板】【布局】【设计细节】) are well organized. Per the simple-skill guidance this matches the top anchor.	5 / 5
	Total	17 / 20 Passed

Description

53%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 distinctive and concretely enumerates its deliverables (10 layouts, 5 named palettes), but it is a product tagline rather than a capability statement: no actions are named and there is no 'Use when' trigger guidance, so users needing a slide deck may not surface this skill. Adding an explicit trigger clause and natural terms like deck/slides/presentation would lift it substantially.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks for a slide deck, presentation, or magazine-style layout with a print/e-ink aesthetic.'

State the core action explicitly, e.g. 'Creates editorial-magazine-style HTML slide decks' instead of the tagline 'Editorial magazine meets e-ink'.

Include natural trigger terms and synonyms users would actually say — deck, slides, presentation, pptx-style deck, magazine layout.

Dimension	Reasoning	Score
Specificity	"10 layouts and 5 palettes (Ink, Indigo Porcelain, Forest Ink, Kraft Paper, Dune)" names the domain and enumerates concrete deliverables, but includes no capability verbs or actions. This matches the anchor for naming the domain with 1-2 concrete items but not comprehensive coverage, rather than anchor 4 (no several specific actions listed) or anchor 2 (deliverables are enumerated, not minimal or generic).	3 / 5
Completeness	The 'what' is present (an editorial-magazine × e-ink deck with 10 layouts and 5 palettes) but there is no 'when' / 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. Not anchor 2 because the 'what' is concrete rather than vague.	3 / 5
Trigger Term Quality	"Editorial magazine", "e-ink", "layouts", and "palettes" are relevant keywords, but common natural variations users would say — "deck", "slides", "presentation", "ppt" — are absent. Some relevant keywords with missing variations matches anchor 3 rather than anchor 4's 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	The niche is clear and distinctive ("editorial magazine meets e-ink" with five named palettes), giving minor overlap risk only with closely related deck/slide skills. It falls short of anchor 5 because the description includes no distinct explicit trigger phrases.	4 / 5
	Total	13 / 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: skills/deck-guizang-editorial/SKILL.md
Commit: 1b47e60

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