CtrlK
BlogDocsLog inGet started
Tessl Logo

deck-swiss-international

16-column grid, one saturated accent, and 22 locked layouts (Klein Blue, Lemon, Mint, Safety Orange).

57

Quality

66%

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-swiss-international/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A disciplined, token-efficient design spec with exact, executable constraints (hexes, CSS values, font stack, output format) and a clear layout inventory. Weaknesses are the implicit workflow — no explicit step order or validation of the generated HTML — and the absence of even one concrete layout code example to anchor the terse per-layout descriptions.

DimensionReasoningScore

Conciseness

Lean and dense throughout: every line is a hard constraint ('border-radius: 0', '1px hairline borders, 严禁阴影 / 渐变 / blur') with zero padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Highly concrete guidance — exact hexes, 'grid-template-columns: repeat(16, 1fr); gap: 0', named fonts, font sizes ('9.6vw display, body 14-16px, label 11px uppercase letterspacing 0.08em'), per-layout structure, and a single-file HTML output contract. Minor gap: no HTML snippet showing any of the 22 layouts.

4 / 5

Workflow Clarity

The sequence is implicit (pick one of 4 themes → select layouts from the pool, count driven by content → apply design rules → emit single-file HTML) with no explicit step ordering and no validation/checkpoint step for the generated output.

3 / 5

Progressive Disclosure

The body is ~42 lines with no bundle files (no references/scripts/assets exist) and is clearly sectioned (【意图】/【主题】/【布局】/【设计细节】), matching the simple-skill case where well-organized sections alone suffice.

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 a concrete, attribute-dense design spec but reads as a noun phrase rather than a capability statement: it names no actions, omits all natural trigger terms (slides, deck, presentation), and lacks any 'use when' guidance. Distinctiveness is decent thanks to the specific palette and layout inventory.

Suggestions

State the action explicitly, e.g. 'Creates single-file HTML slide decks using a 16-column Swiss International grid...' so the description answers 'what does this skill do'.

Add a 'Use when...' clause with natural trigger terms (slides, deck, presentation, Swiss/international style, marketing deck) so users and Claude know when to invoke it.

Align the palette naming between description and body ('Mint' vs body's 'Lemon Green / Neon') to avoid confusion about the actual theme set.

DimensionReasoningScore

Specificity

Concrete attributes ('16-column grid', 'one saturated accent', '22 locked layouts', named palettes) but no stated actions or capabilities — the description says what the template has, never what the skill does.

3 / 5

Completeness

The 'what' is only implied via template attributes with no action verb, and the 'when' is entirely missing — no 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 3.

3 / 5

Trigger Term Quality

Design keywords like 'Klein Blue', 'accent', and 'grid' are relevant, but every natural task-level phrase a user would say ('slides', 'deck', 'presentation', 'Swiss') is absent from the description.

3 / 5

Distinctiveness Conflict Risk

Named palettes (Klein Blue, Safety Orange) and fixed counts (16-column, 22 layouts) make it fairly distinguishable, though without deck/slides vocabulary it risks overlap with generic layout-design skills.

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