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).

62

Quality

74%

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

86%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 tight, highly actionable generative template spec with exact CSS values, palette hex codes, and 22 concrete layout recipes, well-organized into a single self-contained file. The main gap is the absence of any explicit output-validation checkpoint and complete copy-paste code examples.

DimensionReasoningScore

Conciseness

Lean imperative-only spec with no padding or explanation of concepts Claude already knows; each of the 22 layouts is a single terse line and the design rules are tight bullets, so every token earns its place.

5 / 5

Actionability

Provides concrete executable values (exact hex codes, 'grid-template-columns: repeat(16, 1fr); gap: 0', '9.6vw', '11px uppercase letterspacing 0.08em', exact font stack, ←/→ + hash sync) and per-layout composition recipes, but lacks complete copy-paste HTML code blocks covering common cases.

4 / 5

Workflow Clarity

Clear composition sequence — pick one of four themes, draw layouts from the 22-pool 'until user content is fully covered', apply locked design rules — with an integrity constraint ('不许编造: numbers must come from user input'), but no explicit validation/verification step for the generated output.

4 / 5

Progressive Disclosure

Self-contained body under 50 lines with no external references, organized into clearly labeled sections (【意图】, 【主题】, 【布局】, 【设计细节】); meets the simple-skill exception for full marks with well-organized sections and no bundle files needed.

5 / 5

Total

18

/

20

Passed

Description

62%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 concrete and highly distinctive about what the deck produces, but it lacks any explicit 'Use when...' trigger guidance and is missing the most natural user-facing terms like 'deck', 'slides', or 'presentation'. Adding a trigger clause and natural vocabulary would lift the weaker dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating Swiss/International-style slide decks, product roadmaps, or data presentations.' to satisfy the 'when' requirement and lift completeness above 3.

Include the natural vocabulary users actually say — 'deck', 'slides', 'presentation', 'pitch' — alongside the technical grid/accent terms to improve trigger-term coverage.

Lead with the artifact type (a 16:9 slide deck) before the compositional details so the 'what' reads as an action/output rather than a static configuration.

DimensionReasoningScore

Specificity

Quotes concrete compositional primitives — '16-column grid', 'one saturated accent', '22 locked layouts' — plus four named palettes, naming the domain and several specific building blocks rather than vague language.

4 / 5

Completeness

Clearly answers 'what' (16-column grid, one accent, 22 layouts, four palettes) but provides no 'when' / 'Use when...' trigger clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains relevant domain keywords (grid, layouts, accent, Klein Blue) but omits the natural terms users would actually say ('deck', 'slides', 'presentation') and any file extension, missing common variations.

3 / 5

Distinctiveness Conflict Risk

The '16-column grid + one saturated accent + 22 locked layouts (Klein Blue, Lemon, Mint, Safety Orange)' combination is a highly specific niche with unmistakable triggers and minimal conflict risk.

5 / 5

Total

15

/

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.

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.