CtrlK
BlogDocsLog inGet started
Tessl Logo

visual-style

Create, extract, and apply portable visual design systems via visual-style.md files. Use when: (1) Creating a visual-style.md design system from scratch, (2) Extracting a visual style from a website URL, video, or PDF brand guide, (3) Applying a visual style to HeyGen videos, HTML slides, Figma, or paper.design, (4) Browsing the gallery of pre-built visual styles (Swiss, Saul Bass, Game Boy, etc.), (5) User mentions "visual style", "design system", "brand style", or "style guide", (6) Styling a HeyGen video with a consistent design language.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 well-organized, token-efficient overview that defers detail to a verified reference bundle. Its main weakness is workflow validation: the generative/extract flows include a 'Validate' step but no failure-handling feedback loop, which the rubric caps at 3 for workflow clarity.

Suggestions

Add a feedback loop to the Extract 'Validate' step (e.g. 'If validation fails: list missing fields, regenerate, re-validate — only proceed when valid') to lift workflow clarity above the cap.

Tighten the Create and Apply workflows with one concrete, copy-paste-ready artifact (e.g. a minimal filled visual-style.md snippet or a sample connector transform) to move actionability from good to fully executable.

Optionally add an explicit checkpoint after Apply 'Generate output' to verify the tool-specific output is consistent with the source style fields.

DimensionReasoningScore

Conciseness

Lean and efficient: no explanations of concepts Claude already knows, no padding; every section earns its place with quick-reference tables and terse workflows assuming Claude's competence.

5 / 5

Actionability

Concrete YAML field spec with example values and pointers to specific template files; however the workflows themselves are high-level process steps (e.g. 'Define colors', 'Set typography') rather than copy-paste-ready executable instructions, leaving minor gaps.

4 / 5

Workflow Clarity

Create/Extract/Apply/Gallery workflows are clearly sequenced into numbered steps, but the Extract flow performs a batch/generative operation with a 'Validate' step that lacks any feedback loop or failure-handling guidance; per the rubric this validation gap caps the score.

3 / 5

Progressive Disclosure

Clean overview structure pointing one level deep to real, verified reference files (connectors, extractors, gallery, templates, spec) organized in navigable tables; no nested references and content is appropriately split.

5 / 5

Total

17

/

20

Passed

Description

100%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 exemplary: it states concrete capabilities, provides six explicit trigger scenarios, uses natural user vocabulary with synonyms, and carves out a distinct niche. Voice is third person and there is no vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — create, extract, apply — across named tools (HeyGen, HTML slides, Figma, paper.design) and sources (URL, video, PDF brand guide), with gallery browsing as an additional capability.

5 / 5

Completeness

Explicitly answers what (create/extract/apply portable visual design systems via visual-style.md files) and when (six numbered 'Use when' scenarios with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural terms including synonyms users would say — 'visual style', 'design system', 'brand style', 'style guide' — alongside concrete tool names; covers variations well.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (portable visual-style.md design systems) with distinct tool and trigger vocabulary unlikely to fire for unrelated skills; minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 16 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 32 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
calesthio/OpenMontage
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.