brand-intel-branddev

Brand intelligence - logos, colors, fonts, styleguides, and company data from any domain

Quality

58%

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/brand-intel-branddev/SKILL.md

Quality

Content

50%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 highly actionable with concrete curl examples for every endpoint, but it is padded by endpoint duplication and repeated boilerplate, inlines a large API reference that belongs in separate files, and lacks validation/error-handling guidance. One example curl is also malformed.

Suggestions

Move the per-endpoint parameter reference and curl examples into a separate references/ file (e.g. ENDPOINTS.md) and keep SKILL.md as a concise overview, eliminating the Capabilities/Usage duplication.

Fix the broken 'Query website data using AI' curl block so its -d JSON payload is valid and copy-paste runnable.

Add a brief validation step, e.g. check the HTTP status / response shape and retry guidance for 401/408/422, so batch retrieval workflows have an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The 274-line body duplicates every endpoint description across both a Capabilities list and a Usage section, and repeats identical curl boilerplate 12 times; this is noticeably padded though it avoids explaining concepts Claude already knows.	2 / 5
Actionability	Most endpoints ship concrete, copy-paste-ready curl commands with real example domains and full headers, but the final 'Query website data using AI' curl block is malformed (broken JSON payload) and would fail if run verbatim.	4 / 5
Workflow Clarity	A setup sequence exists (export key -> Bearer auth -> call), but there are no validation or verification checkpoints and no error-handling guidance, which the rubric caps at 3 for batch/retrieval operations.	3 / 5
Progressive Disclosure	There is section structure (Capabilities, Usage, Use Cases), but the entire ~12-endpoint API reference is inlined in SKILL.md with no bundle files to offload it, so content that belongs in separate references is inline.	3 / 5
	Total	12 / 20 Passed

Description

66%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 clearly conveys what the skill does via concrete brand-intelligence deliverables, but omits any explicit 'when to use' trigger guidance, capping its completeness. It is specific and reasonably distinctive.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user needs brand logos, colors, fonts, or a styleguide for a domain, or wants company data from a website, email, ticker, or ISIN').

Add common synonyms and file/identifier terms (branding, visual identity, .com domain, ISIN, NAICS) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete deliverables ('logos, colors, fonts, styleguides, and company data'), though it uses output nouns rather than action verbs; fits between anchor 3 and 5, clearly above a single-action description.	4 / 5
Completeness	Provides a clear 'what' but no 'Use when...' trigger guidance; per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('logos, colors, fonts, styleguides, company data, domain') with decent coverage, though it omits common synonyms like 'branding' or 'visual identity'.	4 / 5
Distinctiveness Conflict Risk	The brand-intelligence-from-a-domain niche is mostly distinct with specific triggers, though 'company data from any domain' is somewhat broad and could overlap with lead-enrichment skills.	4 / 5
	Total	15 / 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/brand-intel-branddev/SKILL.md
Commit: 2523432

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.