CtrlK
BlogDocsLog inGet started
Tessl Logo

deck-guizang-editorial

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

64

Quality

77%

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 ./skills/deck-guizang-editorial/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally lean and actionable design spec that gives concrete, executable guidance within a single well-organized file, weakened only by the absence of an explicit assembly workflow with a validation checkpoint.

Suggestions

Add a short numbered assembly sequence (pick palette → map content to layouts → assemble single-file HTML → verify hairline/folio/baseline rules).

Include an explicit verification step for the generated deck (e.g., confirm no prohibited effects, all images are inline CSS/SVG, hash paging works) to close the feedback loop.

Optionally split the layout catalog into a referenced LAYOUTS.md if the file grows, keeping SKILL.md as an overview.

DimensionReasoningScore

Conciseness

The body is a dense, lean spec — palette hex values, layout specs, fonts, and prohibitions — with no padding or explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

It provides fully concrete, copy-paste-ready guidance: exact hex codes, vw sizing, layout compositions, font names, and explicit 严禁/不许 lists, leaving nothing abstract.

3 / 3

Workflow Clarity

The content is well-organized by section but presents a spec catalog rather than a sequenced assembly process, and includes no validation/verification checkpoint for the generated deck.

2 / 3

Progressive Disclosure

This is a compact single-file skill (no references/scripts/assets exist) with clearly delimited sections (调色板 / 布局 / 设计细节); per the simple-skill guidance, well-organized sections without external references score 3.

3 / 3

Total

11

/

12

Passed

Description

67%

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 specific, distinctive description that concretely names the skill's deliverables, but it lacks any explicit "Use when..." trigger guidance, which caps completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating editorial magazine-style or e-ink presentations, magazine layouts, or narrative decks."

Broaden trigger terms to include common phrasings users might say ("magazine slides", "editorial deck", "e-ink theme").

Optionally note the 16:9 horizontal paging format in the description to further differentiate from other slide skills.

DimensionReasoningScore

Specificity

Names the domain and concrete deliverables — "10 layouts and 5 palettes" with each palette enumerated by name — listing multiple specific concrete artifacts rather than vague actions.

3 / 3

Completeness

It clearly answers "what" (editorial e-ink deck with 10 layouts and 5 palettes) but provides no "when"/Use-when clause; per the guidelines a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

It includes some natural terms a user might say ("editorial magazine", "e-ink", "layouts", "palettes") but omits common variations and any explicit trigger phrasing.

2 / 3

Distinctiveness Conflict Risk

The niche is precise — editorial/e-ink magazine decks with named palettes — making it clearly distinguishable from generic slide skills and unlikely to trigger for the wrong one.

3 / 3

Total

10

/

12

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.

Validation15 / 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
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.