CtrlK
BlogDocsLog inGet started
Tessl Logo

logo-generator

Deprecated compatibility entry for Logo construction. This component is now maintained in Bricks; install and use component-builder to build a new Logo.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/components/branding/logo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%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 a well-executed redirect stub: maximally lean, fully actionable, and unambiguous about where Logo construction now lives and how to get it. Its only structural weakness is that everything of substance is delegated to an external repository rather than organized bundle files.

DimensionReasoningScore

Conciseness

The body is ~10 lines and every token serves the redirect: where the component moved, the install command, and the closing note that 'This compatibility entry contains no component rules and is no longer maintained.' Lean and efficient, matching anchor 5.

5 / 5

Actionability

Provides the copy-paste-ready command 'npx skills add kostja94/bricks --skill component-builder' plus an explicit instruction ('Ask the agent to use component-builder to build a new Logo') and a direct link to the Logo reference. Fully executable for the skill's single purpose.

5 / 5

Workflow Clarity

A simple, single-action skill (redirect to the successor); the single action is unambiguous — install the named skill, then use it. The simple-skill exception applies and no destructive or batch operation is involved, so no validation step is required.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files, and its one reference is clearly signaled and one level deep. However, the core content lives at an external GitHub URL rather than any bundled file and section structure is minimal, leaving a minor organization gap that fits anchor 4 rather than 5.

4 / 5

Total

19

/

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 honest and specific about the skill's deprecation status and redirect target, but it functions as a tombstone rather than a discovery description: it lacks any 'use when' trigger guidance and the natural phrasings a user would say when they need a logo built. As a redirect stub it communicates its purpose, yet it underperforms as a triggerable skill description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create, build, or design a logo' — the missing 'Use when...' guidance currently caps completeness at 3.

Include natural user phrasings and synonyms ('logo', 'create a logo', 'logo design', 'brand mark') so the skill surfaces when users ask in their own words.

State the concrete capability once redirected (e.g. 'component-builder constructs Logo components following the Bricks component rules') so the 'what' is more than a pointer.

DimensionReasoningScore

Specificity

Names the domain ('Logo construction') and one concrete action ('install and use component-builder to build a new Logo'), but coverage is not comprehensive. Fits anchor 3 (domain plus 1-2 concrete actions); not 4 because only a single action is listed rather than several.

3 / 5

Completeness

The 'what' is explicit and clear (deprecated compatibility entry; successor is component-builder), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps this dimension at 3. Not 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ('Logo', 'Logo construction', 'component-builder', 'Bricks'), but common natural variations a user would say ('create a logo', 'logo design', 'brand mark') are missing. Matches anchor 3; not 4 because natural-term coverage is thin.

3 / 5

Distinctiveness Conflict Risk

'Logo construction' is a clear niche and the specific successor skill is named, giving a distinct trigger surface. Minor overlap risk remains with component-builder itself for logo-related requests, matching anchor 4 rather than 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
kostja94/marketing-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.