get-brand-assets

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

Quality

76%

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

81%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 highly actionable, with executable commands for every endpoint, a clear setup sequence with error recovery, and clean section organization appropriate for a single-file skill. The main cost is token efficiency: the Examples section duplicates the Usage commands verbatim and one paragraph re-states the frontmatter description. Splitting endpoint/response detail into a reference file and de-duplicating examples would tighten it further.

Suggestions

Remove the duplicated Examples section (or replace it with one-line mappings like "'Get Notion's logo' → use retrieve-simplified") since the commands already appear in full under Usage.

Delete the restated purpose paragraph after Setup ("Extract logos, colors, fonts, and design assets...") — it repeats the frontmatter description.

Consider moving the Response field enumerations for the five endpoints into a references/ file (e.g. RESPONSE.md) to reduce inline token load.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the "Examples" section repeats three curl commands verbatim from "Usage" (~25 duplicated lines), and the paragraph after Setup ("Extract logos, colors, fonts, and design assets from any company's brand...") re-states the description, so it could be tightened more than a 4 would allow.	3 / 5
Actionability	All five endpoints are given as complete, copy-paste-ready curl commands with concrete example domains, auth headers, and JSON bodies; credential setup includes an executable extraction step plus a fallback login path, covering the common cases fully.	5 / 5
Workflow Clarity	This is a simple single-purpose API skill and the single action is unambiguous: set up credentials (with an explicit check-and-recover path if the file is missing), pick the endpoint, run the command. No destructive or batch operations apply, so the simple-skill exception to the validation requirement holds.	5 / 5
Progressive Disclosure	No bundle files exist and the content is organized into clear, well-labeled sections (Setup, When to Use, Usage, Parameters, Response, Examples, Tips) with everything at one level. It falls short of a 5 because the body exceeds 50 lines and the endpoint catalog plus response-field enumerations could be split into referenced files.	4 / 5
	Total	17 / 20 Passed

Description

61%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 concise, in third person, and clearly communicates what the skill retrieves, with good natural trigger terms. Its main weakness is the missing 'Use when...' clause, which leaves the 'when' half of completeness unanswered and caps that dimension. Adding an explicit usage-trigger sentence would lift completeness and trigger-term coverage to the top anchors.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a company's logo, brand colors, fonts, or design system, or when preparing pitch decks or partnership materials."

Replace the single generic verb with more specific actions to sharpen capability description, e.g. "Extract company logos, brand color palettes, fonts, and design-system style guides from any company website."

Include common synonyms users say, such as "branding", "design system", or "visual identity", to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"Get company logos, brand colors, fonts, and style guides" names concrete deliverables but relies on a single generic verb; it does not list multiple distinct actions, matching the 'names domain and 1-2 concrete actions' anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	The "what" is clear (get logos, colors, fonts, style guides), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines; a 4 would require an explicit 'when' to be present.	3 / 5
Trigger Term Quality	Terms like "logos", "brand colors", "fonts", and "style guides" are natural phrases users would say, but common synonyms such as "branding", "design system", or "visual identity" are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The company-brand-asset scope ("company logos, brand colors, fonts, and style guides") is a mostly distinct niche with only minor overlap risk against general design or internal-brand-style skills, fitting the 'mostly distinct' anchor.	4 / 5
	Total	14 / 20 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: cc3e518

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