company-logos

Use Iconify Simple Icons logos (64x64) instead of text logos.

Quality

66%

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 ./agent-skills/web-design/company-logos/SKILL.md

Quality

Content

78%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 an exemplar of token efficiency — short, well-sectioned, and free of filler — and its workflow is clearly sequenced. Its one real weakness is actionability: it tells Claude what to do but not how to fetch or render an Iconify Simple Icons icon.

Suggestions

Add one concrete fetch/render example (e.g. the Iconify CDN URL pattern, the @iconify-json/simple-icons package, or a tiny inline-SVG snippet) so the guidance is executable rather than directional.

Add a verification step such as 'confirm the brand exists in the Simple Icons set before falling back to typed company names' to give the workflow an explicit checkpoint.

Optionally show one example of the 64x64 box with scaled inner SVG so the sizing rule is unambiguous.

Dimension	Reasoning	Score
Conciseness	The ~20-line body is lean and assumes Claude's competence — it never explains what Iconify or Simple Icons is, and every line is directive guidance with no padding.	5 / 5
Actionability	Guidance is directionally concrete (64x64 box, monochrome default, shared baseline grid) but incomplete as an instruction-only skill: it never says how to actually obtain or render an Iconify icon (API URL, npm package, or a copy-paste snippet), so key execution details are missing rather than minor gaps.	3 / 5
Workflow Clarity	The 5-step workflow is clearly sequenced and this is not a destructive/batch operation, so the validation cap does not apply; it stops short of 5 because there is no checkpoint like 'verify the icon exists in the Simple Icons set' before the text fallback.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed, and the Use When / Workflow / Guardrails sections are well organized, meeting the simple-skill exception for a top progressive-disclosure score.	5 / 5
	Total	17 / 20 Passed

Description

53%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 and names a specific, distinguishable capability, but it omits any explicit 'when to use' trigger guidance and relies on a single action statement with limited keyword coverage. Adding a 'Use when...' clause with natural trigger phrases would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a design needs company or brand logos — logo rows, integrations grids, customer proof, partner lists, or tool badges.'

Include natural synonyms users would say, such as 'brand logos', 'company logos', 'partner marks', or 'customer logos', not just 'text logos'.

State 1-2 more concrete capabilities (e.g. 'renders monochrome 64x64 marks, aligned to a shared baseline') to broaden action coverage beyond the single 'instead of' directive.

Dimension	Reasoning	Score
Specificity	Names the domain ('Iconify Simple Icons logos') with one concrete action ('use ... instead of text logos') and a size spec ('64x64'), but does not list several specific actions, matching the 1-2-concrete-actions anchor rather than the several-actions level above.	3 / 5
Completeness	The 'what' is clear (use Iconify Simple Icons 64x64 logos instead of text logos) but there is no explicit 'Use when...' clause or trigger guidance, which per the judging guidelines caps completeness at 3; the 'when' is only weakly implied.	3 / 5
Trigger Term Quality	'logos' and 'text logos' are natural user terms, but common variations and synonyms like 'brand logos', 'company logos', 'partner marks', or 'customer proof' are absent, leaving keyword coverage incomplete.	3 / 5
Distinctiveness Conflict Risk	'Iconify Simple Icons logos' carves a fairly distinct niche against generic icon or design skills, though minor overlap risk remains with general iconography/branding guidance, so it is mostly distinct rather than a clear 5-trigger niche.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: MengTo/Skills
Path: agent-skills/web-design/company-logos/SKILL.md
Commit: 798db0a

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