visual-brand-extractor

Extract visual branding (colors, typography, layout patterns) from a client's website and generate a style preset compatible with the HTML slides skill and a brand config JSON for the content asset creator. Uses WebFetch to read pages and analyzes CSS/HTML to identify the color palette, font pairings, and aesthetic patterns.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/brand/capabilities/visual-brand-extractor/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear phased workflow, concrete prompts, and a complete output template. Its main weaknesses are length/conciseness and a monolithic structure that keeps large reference tables inline rather than split into reference files.

Suggestions

Move the Tailwind CSS Color Reference and Font Fallback Table into separate reference files under ./references/ and link to them from the main body to improve progressive disclosure and reduce token load.

Tighten the longer sections (e.g., the color-role and signal tables) by trimming redundant explanation to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly earned (CSS property lists, role tables, output template), but at ~400 lines with large inline reference tables it could be tightened; it sits at "mostly efficient but could be tightened" rather than fully lean.	2 / 3
Actionability	Provides copy-paste-ready guidance: an exact WebFetch prompt, concrete CSS properties to search, a full output template with precise JSON structure, and hex lookup tables — fully executable and specific.	3 / 3
Workflow Clarity	A clear five-phase sequence (Fetch → Colors → Typography → Patterns → Generate) with edge-case recovery guidance (JS-rendered sites prompt the user, multiple color schemes, font detection failure); not a destructive/batch operation so no validation cap applies.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is monolithic; large reference material (Tailwind color tables, Font Fallback Table) that could live in separate reference files is inline, matching the "content that should be separate is inline" anchor despite good section organization.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and distinctive, naming concrete actions and a clear niche, but it omits an explicit "Use when..." trigger clause and relies on somewhat limited natural trigger terms. Adding explicit usage triggers would raise completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause stating when Claude should invoke this skill (e.g., when a user wants to extract a brand's visual identity or generate a style preset from a website).

Broaden trigger terms with natural phrasings users would actually say, such as "brand identity", "extract brand colors", "client website", or "style preset".

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Extract visual branding (colors, typography, layout patterns)", "generate a style preset", "brand config JSON", and "analyzes CSS/HTML to identify the color palette, font pairings, and aesthetic patterns" — matching the score-3 anchor.	3 / 3
Completeness	Clearly answers "what" the skill does, but the "when" is only implied with no explicit "Use when..." clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant keywords (visual branding, colors, typography, website, style preset) but lacks common natural variations like "brand identity", "extract brand", or "client website" and has no "Use when..." trigger phrase, so it sits at the some-keywords-but-incomplete anchor.	2 / 3
Distinctiveness Conflict Risk	Has a clear niche — extracting visual brand identity from a client website to produce slide presets and brand config JSON — with distinct triggers unlikely to overlap with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/brand/capabilities/visual-brand-extractor/SKILL.md
Commit: 8866b2a

Reviewed: 1 day 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.