CtrlK
BlogDocsLog inGet started
Tessl Logo

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill `brutalist-skill` (Tactical Telemetry mode).

59

Quality

67%

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/html-ppt-taste-brutalist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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 lean, well-organized, self-contained style spec with exact values and a pre-flight validation checklist. Its main gap is actionability: it gives precise design tokens but no executable HTML/CSS scaffold or slide template, so archetype assembly stays at the prose level.

Suggestions

Add a minimal copy-paste HTML/CSS scaffold for one slide (substrate + scanline overlay + register strip) so the spec is executable, not just descriptive.

Provide one worked archetype example (e.g., the telemetry grid) as actual HTML/CSS rather than a prose description.

Optionally include a one-line build sequence (set substrate → add scanline → assemble archetypes → run pre-flight) to make the workflow explicit.

DimensionReasoningScore

Conciseness

The body is dense and efficient — exact hex values, clamp() scales, and one-line rules with no padding or explanation of concepts Claude already knows ('density over decoration').

3 / 3

Actionability

Concrete specs abound ('border-radius: 0', 'display: grid; gap: 1px', '#E61919', 'clamp(56px, 7vw, 96px)'), but there is no executable HTML/CSS scaffold or slide example; the 11 archetypes are described in prose ('giant numeral or call-sign on the left, redaction bar above the title'), leaving actual assembly non-copy-paste.

2 / 3

Workflow Clarity

The single task is unambiguous and the Pre-flight section is an explicit validation checklist (e.g., 'All border-radius is 0', 'Scanline overlay applied... opacity ≤ 0.08') serving as a completion gate for this non-destructive, single-purpose skill.

3 / 3

Progressive Disclosure

Self-contained and well-organized into clear sections (Hard rules, Banned, Required slide archetypes, Motion, Pre-flight) with no bundle files and no nested references — appropriate for a concise style spec.

3 / 3

Total

11

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 vividly conveys a specific aesthetic but is light on concrete actions and lacks explicit use-when trigger guidance. All dimensions land at the mid-level because niche jargon narrows natural trigger terms and the generic 'HTML deck' framing risks overlap with sibling presentation skills.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when creating project debriefs, security reviews, or incident write-up decks in a CRT-terminal/brutalist style').

Lead with a concrete action verb (e.g., 'Generates 16:9 HTML presentation decks...') so capabilities read as actions, not just aesthetic attributes.

Include common synonyms ('presentation', 'slides', 'report deck') alongside the niche taste terms to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('16:9 HTML deck') and concrete aesthetic attributes ('Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay') but frames them as visual properties rather than listing multiple concrete build actions, so coverage is not comprehensive.

2 / 3

Completeness

Describes what the skill produces (a styled 16:9 HTML deck) but provides no explicit 'Use when...' trigger guidance, so the 'when' is only implied — capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Includes some terms a user might say ('HTML deck', 'CRT-terminal') but leans on niche jargon ('tactical-telemetry', 'white-phosphor', 'hazard-red') and omits common variations like 'presentation', 'slides', or 'report'.

2 / 3

Distinctiveness Conflict Risk

The CRT-terminal aesthetic is a distinct niche, but '16:9 HTML deck' is generic and the skill body references a sibling 'light Swiss-print mode', indicating a family of overlapping html-ppt taste skills.

2 / 3

Total

8

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.