CtrlK
BlogDocsLog inGet started
Tessl Logo

company-logos

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

59

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is concise and well-structured with a clear workflow for a simple single-purpose skill. Its main gap is actionability: it describes treatment rules but gives no concrete, executable mechanism for sourcing or rendering the Iconify logos. Adding a minimal code/markup snippet would close that gap.

Suggestions

Add a minimal executable example showing how to fetch/render an Iconify Simple Icons logo (e.g. the @iconify-json/simple-icons usage or the <icon> markup) so the guidance is copy-paste ready.

Specify the exact default sizing approach ('render at 64x64 then scale via CSS width/height') rather than leaving 'scale the inner SVG to the composition density' implicit.

Show one concrete logo-row example with alignment so the baseline/center-grid rule is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean (~23 lines) with no padding and no explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Guidance is specific (64x64 box, monochrome by default, baseline/center grid) but stops short of executable detail, e.g. the exact Iconify fetch mechanism, package, or markup to render a logo.

2 / 3

Workflow Clarity

A clear, ordered 5-step sequence for a single-purpose task with unambiguous steps and no destructive/batch operation requiring validation.

3 / 3

Progressive Disclosure

Under 50 lines, single-purpose, with well-organized sections (Use When, Workflow, Guardrails) and no need for external references.

3 / 3

Total

11

/

12

Passed

Description

50%

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 identifies a clear, specific niche but omits a 'Use when...' trigger clause and natural user-facing keywords. This limits triggerability and completeness. Adding explicit trigger conditions and common user phrasings would raise it to the top level.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when adding company logos, brand marks, integrations grids, partner lists, or tool badges.'

Include natural user keywords such as 'company logos', 'brand icons', and 'integrations' alongside 'logos' to improve trigger term coverage.

Mention a second concrete capability (e.g. scaling logos to composition density or rendering them monochrome) to lift specificity above a single action.

DimensionReasoningScore

Specificity

Names the domain ('Iconify Simple Icons logos (64x64)') and one concrete action ('instead of text logos'), but lists a single behavior rather than multiple specific actions.

2 / 3

Completeness

Answers 'what' (use Iconify Simple Icons 64x64 logos instead of text logos) but lacks any 'when' / 'Use when...' trigger clause, which caps completeness at 2.

2 / 3

Trigger Term Quality

Includes the relevant keyword 'logos' but omits common natural variations users would say such as 'company logos', 'brand icons', 'integrations', or 'partner logos'.

2 / 3

Distinctiveness Conflict Risk

The niche (Iconify Simple Icons 64x64 logos) is reasonably specific but, without explicit triggers, could still overlap with general icon/branding skills.

2 / 3

Total

8

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
Reviewed

Table of Contents

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.