CtrlK
BlogDocsLog inGet started
Tessl Logo

digits-fintech-swiss-template

Swiss-grid fintech deck template in black / warm paper / neon-lime contrast. Use when users ask for premium data-story slides with strict modular layout, bold numeric cards, restrained motion, and keyboard/click navigation in one HTML file.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured template skill body with concrete workflow steps and a precise output contract. Its main weaknesses are integration of the bundle: the checklist reference is listed but never invoked, sandbox-hostile APIs are named without enumeration, and the resource map advertises an example.html that is missing from the bundle.

Suggestions

Add a final workflow step that invokes the reference, e.g. "6. Validate the finished deck against `references/checklist.md` (P0 items are blocking)", which would also give the workflow an explicit validation checkpoint.

Fix the resource map and frontmatter outputs: `example.html` is listed at the skill root (and required by the checklist's P0) but is missing from the bundle — either ship it or remove it from the map.

Point the "no sandbox-hostile APIs" rule at the checklist's concrete list (localStorage, sessionStorage, alert, confirm, prompt, window.open) or inline that enumeration so the constraint is checkable from the body alone.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and efficient — a one-line intro, a file map, five terse workflow steps, and a copy-paste output contract — with zero padding and no explanation of concepts Claude already knows, matching the 5 anchor.

5 / 5

Actionability

The guidance is mostly executable: "Start from `assets/template.html`", keep "keyboard navigation (`ArrowLeft` / `ArrowRight`)", "keep the file self-contained (inline CSS/JS)", plus an exact artifact block for output. It falls short of 5 because "no sandbox-hostile APIs" is never enumerated in the body, and the workflow never tells Claude to actually consult `references/checklist.md`, leaving those concrete details unreachable.

4 / 5

Workflow Clarity

The five-step workflow is a clear, well-sequenced instruction set with explicit preserve-constraints (structure, hierarchy, interactions, motion). It is not 5 because there is no validation checkpoint, even though `references/checklist.md` exists precisely for verification and is never wired into the sequence — a minor but real gap versus the explicit-checkpoint anchor.

4 / 5

Progressive Disclosure

Structure exists (resource map, workflow, output contract) and references are one level deep, but scoring against the actual bundle reveals two problems: the resource map lists `example.html` at the skill root and it does not exist in the bundle, and `references/checklist.md` appears only as a tree entry with no in-text navigation or 'see' signal from any workflow step. This fits the 3 anchor — references present but not clearly signaled — rather than 4.

3 / 5

Total

16

/

20

Passed

Description

83%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.

A strong description with an explicit 'Use when' clause, concrete visual/domain specifics, and a well-delineated niche. Its only weaknesses are a noun-phrase 'what' lacking action verbs and some missing natural synonyms like "presentation" or "pitch deck".

DimensionReasoningScore

Specificity

The description gives several concrete specifics — "Swiss-grid fintech deck template", "strict modular layout, bold numeric cards, restrained motion, and keyboard/click navigation in one HTML file" — but the what is a noun phrase with no action verbs (e.g. "Generate" or "Create"), and it omits that the skill also covers customizing/replacing copy and metric values, so it falls just short of the comprehensive 5 anchor.

4 / 5

Completeness

It explicitly answers both: what ("Swiss-grid fintech deck template in black / warm paper / neon-lime contrast") and when ("Use when users ask for premium data-story slides with strict modular layout, bold numeric cards, restrained motion, and keyboard/click navigation in one HTML file") with concrete trigger phrases, exactly matching the 5 anchor's structure.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("fintech", "deck", "data-story slides", "keyboard navigation", "one HTML file") that a user would plausibly say, but common synonyms like "presentation", "pitch deck", or "finance slides" are missing, matching the 'a few natural terms missing' anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — Swiss-grid, fintech, neon-lime contrast is unlikely to be confused with most skills — but it could still overlap with generic slide/deck/presentation template skills, so the 'mostly distinct; minor overlap risk' anchor fits better than 5.

4 / 5

Total

17

/

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.