CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

simple-deck

OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Built as a decision-grade corporate strategy deck for leadership team.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./design-templates/simple-deck/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 content body is an exemplary instruction file: a lean overview that delegates the seed template, the 8 paste-ready layouts, and the self-review checklist to one-level-deep bundle files that all exist and match their descriptions. The workflow is fully sequenced with a concrete validation command, error-recovery guidance, and a cheap user checkpoint before HTML is written.

DimensionReasoningScore

Conciseness

The body is lean throughout: no concept explanations, no library tutorials, no padding — every section instructs ("Copy assets/template.html to the project root as index.html", "Don't rewrite the nav script. It's proven."). The one repetition (theme-rhythm rule appearing in both Step 2 and Hard rules) is deliberate reinforcement of a hard rule, not verbosity, so it does not drop it to level 4.

5 / 5

Actionability

Fully executable guidance: concrete file operations (copy seed, replace six :root variables, replace page title), a runnable verification command (`grep 'class="slide' index.html`), an explicit tagging pattern (`data-screen-label="01 Cover"`), and paste-ready slide skeletons confirmed present in references/layouts.md. Specific examples cover the common cases.

5 / 5

Workflow Clarity

Steps 0-5 are clearly sequenced with an explicit validation checkpoint (Step 4 self-check via checklist.md plus the grep rhythm spot-check) and a concrete error-recovery loop ("If you see light × 4 in a row, swap one to dark... If no hero dark exists in an 8+ slide deck, promote one"). It also includes a user feedback checkpoint (show the rhythm sketch before writing HTML), matching the top anchor's feedback-loop and checklist pattern.

5 / 5

Progressive Disclosure

The body is a clear overview with a resource map, and all three referenced bundle files exist exactly one level deep and contain what is claimed (assets/template.html seed; references/layouts.md with the 8 paste-ready layouts and theme-rhythm rules; references/checklist.md with P0/P1/P2 self-review and the rhythm spot-check). Navigation is easy and the split is appropriate: SKILL.md orchestrates, references carry the detail.

5 / 5

Total

20

/

20

Passed

Description

36%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 reads as a description of one specific deck artifact's content (OpenDesign's operating review) rather than a description of what the skill does and when to invoke it. It neither states the skill's capability (building a single-file horizontal-swipe HTML deck) nor provides use-when trigger guidance, leaving it weak on completeness and specificity despite a distinctive topic niche.

Suggestions

Rewrite the description to state the skill's capability in third person, e.g. "Produces a single-file horizontal-swipe HTML deck from a seed template with paste-ready slide layouts and theme-rhythm rules" — replacing the deck-subject framing ("OpenDesign's operating review: growth, burn...") which describes one artifact, not the skill.

Add an explicit "Use when..." clause with natural trigger phrases such as "Use when the user asks for a board deck, pre-read deck, corporate strategy presentation, or HTML slides" to fix the missing "when" and raise trigger-term coverage.

Include synonyms users would naturally say (slides, presentation, pitch deck, board deck) so the description competes with generic presentation skills on trigger matching.

DimensionReasoningScore

Specificity

The description names a domain ("corporate strategy deck", "operating review") but describes a single deck's subject matter ("growth, burn, and the concrete path to sustainability") rather than any action the skill performs — no verbs describe capability. It is not level 1 (concrete nouns like "decision-grade", "leadership team" anchor it to a domain), but it never lists even 1-2 concrete actions, so it cannot reach level 3.

2 / 5

Completeness

"Built as a decision-grade corporate strategy deck" is only a vague, implied "what" — the skill's actual function (producing a single-file HTML deck from a seed template) is absent — and there is no "when"/"Use when" guidance at all in the description. Level 3 requires a clear "what", which this does not provide; level 4+ requires an explicit "when", which is entirely missing.

2 / 5

Trigger Term Quality

Contains some natural phrases a user might say ("operating review", "corporate strategy deck", "board") but misses common variations and synonyms like "slides", "presentation", "pitch deck", "HTML deck". Coverage goes beyond generic jargon (not level 2) but lacks the breadth of level 4.

3 / 5

Distinctiveness Conflict Risk

The niche (board operating-review strategy deck) is reasonably distinctive, but because the description never states the skill's function, it can be confused with other presentation/deck skills. Not level 4-5: distinct triggers are not established by a capability statement; not level 2: the topic framing is specific enough to avoid broad overlap.

3 / 5

Total

10

/

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

Path

design-templates/simple-deck/SKILL.md

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.