sketch

Throwaway HTML mockups: 2-3 design variants to compare.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/creative/sketch/SKILL.md

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 highly actionable and well-sequenced with a real verify-and-fix feedback loop, and its single-file structure is cleanly organized. Its main weakness is mild verbosity — a few sections (CSS reset, GSD aside, intake script) restate things Claude already knows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and action-oriented, but ~200 lines include padding Claude already knows (a full CSS reset + system-font stack, an aside on the GSD system, and verbose intake-script prose) that could be trimmed, so it is not fully lean.	2 / 3
Actionability	Provides copy-paste-ready, executable guidance: concrete tool calls (browser_navigate, browser_vision), file paths, a default HTML/CSS template, README and comparison-table templates, and a typical terminal/write_file sequence.	3 / 3
Workflow Clarity	Clear intake → variants → head-to-head → pick-winner sequence with numbered steps and an explicit validation feedback loop (browser_vision, then 'fix and re-navigate until each variant looks right').	3 / 3
Progressive Disclosure	Single SKILL.md with no bundle files, cleanly sectioned (When NOT to use, Core method, Theming, Output), and no nested/deep references; the well-organized inline structure is appropriate for this standalone skill.	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 is concise and third-person, naming a clear niche, but it omits an explicit 'Use when...' trigger clause and stops short of listing multiple concrete actions. It reads as a domain label rather than a complete trigger-rich description.

Suggestions

Add an explicit 'Use when...' clause with natural triggers, e.g. 'Use when the user wants to sketch a screen, compare 2-3 UI directions, or see variants before committing to a design.'

List multiple concrete actions (generate, compare, iterate variants) to raise specificity beyond the single mock+compare framing.

Include user-natural phrasings such as 'sketch this screen', 'show me variants', or 'mockup this' directly in the description to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	Quotes "Throwaway HTML mockups" and "2-3 design variants to compare" — names the domain and a concrete approach, but does not list multiple distinct concrete actions (only mock + compare), so it falls short of the multi-action level 3.	2 / 3
Completeness	It states what the skill does (throwaway HTML mockups, 2-3 variants to compare) but lacks any "Use when..." trigger clause; per the guideline a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms like "mockups", "design variants", and "compare" appear, but common phrasings users actually say ("sketch this", "show me variants", "mockup this") are absent from the description, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The niche (disposable design-variant comparison) is fairly specific, but the terse description could still overlap with general HTML/design skills like claude-design, so it does not reach the clearly-distinct level 3.	2 / 3
	Total	8 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/creative/sketch/SKILL.md
Commit: 5be99b6

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.