get-brand-assets

Get company logos, brand colors, fonts, and style guides

Quality

68%

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/get-brand-assets/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 body is highly actionable with executable, copy-paste-ready commands and a clear setup sequence, but it carries redundant examples and inline reference detail that a leaner structure or a separate reference file would improve.

Suggestions

Remove the Examples section that duplicates the Usage curl commands, or replace it with genuinely distinct scenarios.

Move the per-endpoint Response field listings into a references file and link to it from the body to reduce inline bulk.

Trim the restated-capability sentence ('Extract logos, colors, fonts, and design assets...') since it repeats the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the Examples section repeats the exact curl commands already given in Usage (notion.so, linear.app, vercel.com), and the lead sentence rephrases the description — padding that could be tightened per the level-2 anchor.	2 / 3
Actionability	It provides complete, copy-paste-ready curl commands with auth headers and JSON payloads for every endpoint, matching the level-3 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	This is a simple single-task skill whose action is unambiguous, and Setup sequences credentials loading with an explicit missing-creds fallback ('tell the user to run npx gooseworks login'), satisfying the simple-skill allowance for a 3.	3 / 3
Progressive Disclosure	Sections are well-organized but the file (~145 lines) is entirely inline with no bundle files; the detailed Response field listings and the duplicated examples are content that could be split out, fitting the level-2 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

60%

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 concrete and specific about what it does but omits any explicit 'when to use' trigger guidance, capping completeness at 2 and leaving it reliant on body context for activation.

Suggestions

Add a 'Use when...' clause with explicit triggers (e.g., 'Use when the user needs a company logo, brand colors, fonts, or a style guide').

Broaden trigger coverage with natural variations like 'brand assets', 'brand guidelines', 'design system', and 'favicon'.

State the trigger in third person to reinforce distinctiveness from generic design skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions/objects — 'logos, brand colors, fonts, and style guides' — matching the level-3 anchor of multiple specific concrete items rather than a single vague domain.	3 / 3
Completeness	It clearly states what the skill does ('Get company logos, brand colors, fonts, and style guides') but has no 'Use when...' trigger clause, so 'when' is missing — the rubric caps this at 2.	2 / 3
Trigger Term Quality	It surfaces natural terms ('logos', 'brand colors', 'fonts', 'style guides') a user would say, but misses common variations like 'brand assets', 'brand guidelines', 'design system', or 'favicon', leaving coverage incomplete per the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	Brand-asset extraction is a recognizable niche, but without explicit triggers the description could overlap with general design/branding skills, matching the level-2 'somewhat specific but could still overlap' anchor.	2 / 3
	Total	9 / 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/get-brand-assets/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.