CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-design-style

Apply a bundled DESIGN.md visual system to an existing HTML file while preserving its content and behavior.

Quality

71%

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 ./backend/super-magic/agents/skills/html-design-style/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is a well-structured, efficient, instruction-only skill: an explicit workflow with validation and failure handling, executable tool-call guidance, precise input validation, and strong preservation rules for a destructive-adjacent operation (modifying an existing file in place). Its main gaps are the unspecified method for step 5's validation and some redundancy between the fetching rules, modification rules, and failure-behavior sections.

Suggestions

Make the step 5 validation checkpoint concrete — specify how to verify preserved behaviors (e.g., re-check event handler bindings, form fields, and API calls in the edited file) so the check is executable rather than aspirational.

Consolidate the repeated preservation and failure statements that appear in Workflow step 5, the Modification rules, and the Failure behavior section into a single authoritative list.

Add a brief fix-and-revalidate loop (on validation failure, correct and re-run the check before saving) to complete the feedback cycle for in-place file modification.

DimensionReasoningScore

Conciseness

The body is mostly lean — a compact code snippet ('tool.call("get_html_design_style_source", {"style_code": "apple"})') and terse rule lists with no explanations of concepts Claude already knows. Minor trimming is possible: 'Use only the returned content as the design source of truth' overlaps 'Do not reconstruct the design system from a catalog, preview metadata, or prior knowledge', and preservation rules are restated across the Workflow, Modification rules, and Output sections. Matches anchor 4; not 5 because of this repetition, not 3 because there is no padded or unnecessary explanation.

4 / 5

Actionability

Guidance is largely executable: a complete Python snippet for the tool call, a precise input-validation spec ('lowercase ASCII letters, digits, dots, and hyphens, beginning with a letter or digit'), and an explicit failure protocol ('If result.ok is false, report the failure from result.content and leave the target file unchanged'). The gap is step 5's 'Validate that content, data requests, permissions, event handling, and existing interactions remain available', which names what to validate but gives no concrete method — matches anchor 4, not 5.

4 / 5

Workflow Clarity

The six-step Workflow is clearly sequenced with a validation checkpoint ('Validate that content, data requests, permissions, event handling, and existing interactions remain available') and a dedicated Failure behavior section ('do not overwrite the target file. Explain the exact failure and leave the original file unchanged'). It is not 5 because there is no fix-and-revalidate feedback loop and the validation method itself is unspecified. Validation is present, so the destructive-operation cap at 3 does not apply.

4 / 5

Progressive Disclosure

Sections (Workflow, Input, Fetching the design document, Modification rules, Failure behavior, Output) are clear and every piece of content belongs inline for a single-purpose skill; the design document is correctly delegated to Magic Service ('Design documents are owned by Magic Service. Do not expect a local copy under this skill directory.') rather than bundled. The body is roughly 72 lines — above the under-50-line simple-skill threshold that would justify a 5 without external references — so it sits at anchor 4 with no organization gaps that matter.

4 / 5

Total

16

/

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 communicates a clear, single-purpose capability in third person with a concrete what, but it lacks any 'when to use' trigger clause and the natural trigger vocabulary (style, theme, restyle) users would say. It is distinguishable from generic skills mostly through the 'bundled DESIGN.md' and 'existing HTML file' qualifiers rather than through distinctive trigger phrases.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to restyle or change the visual style/theme of an existing HTML file using a bundled design system.'

Include natural trigger terms users would actually say: 'style', 'restyle', 'theme', 'look and feel', 'redesign'.

Enumerate the concrete actions of applying the design system (colors, typography, spacing, layout, component states, responsive behavior) to raise specificity from one action to several.

DimensionReasoningScore

Specificity

Quotes: 'Apply a bundled DESIGN.md visual system to an existing HTML file' and 'preserving its content and behavior' name the domain and one concrete action plus a preservation constraint, but the description stops short of enumerating what the design system touches (colors, typography, spacing, layout). This matches anchor 3 (domain and 1-2 concrete actions, not comprehensive); it is not 4 because several specific actions are not listed, and not 2 because a real concrete action is stated.

3 / 5

Completeness

The 'what' is clear ('Apply a bundled DESIGN.md visual system to an existing HTML file') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Keywords like 'DESIGN.md', 'visual system', 'HTML file', and 'design' are relevant, but the natural phrases a user would actually say — 'style', 'restyle', 'theme', 'look and feel' — are missing. This matches anchor 3 (some relevant keywords, missing common variations or synonyms); not 4 because natural user vocabulary is largely absent, not 2 because the terms are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

'bundled DESIGN.md visual system' and 'existing HTML file' carve a fairly distinct niche tied to a specific service and artifact type, with only minor overlap risk against general styling/branding skills. This matches anchor 4 (mostly distinct); not 5 because generic visual-styling vocabulary could still collide with broader design-skill triggers.

4 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dtyq/magic

Path

backend/super-magic/agents/skills/html-design-style/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.