CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ip-as-logo

Design minimal cute IP mascot marks readable at 32px.

52

Quality

66%

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 ./optional-skills/creative/ip-as-logo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured, actionable image-generation workflow with a concrete prompt skeleton, clear step sequence, and an explicit verification checklist. Its main weaknesses are repeated constraints across sections (hurting conciseness) and the absence of any external reference files despite the skill's length.

Suggestions

De-duplicate the 32x32 readability, three-color, and no-centering rules by stating them once and having the Prompt skeleton reference them, to tighten conciseness.

Consider extracting the Prompt skeleton plus the full constraint catalog into a references/ file and pointing to it, which would lift progressive_disclosure given the skill's >50-line size.

Add a one-line cross-check in the Procedure linking each generation step to the Verification checklist so the workflow's validation is explicitly tied back to the steps.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but it repeats the same constraints (the 32x32 readability rule, the three-semantic-color rule, the no-centering rule) across the Procedure, Complexity budget, Color/canvas, and Prompt skeleton sections, so it could be tightened. It is above level 2 because the detail is largely load-bearing for image generation rather than padded explanation of known concepts.

3 / 5

Actionability

Provides a concrete, near copy-paste-ready prompt skeleton with named placeholders, named tools (image_generate, delegate_task, vision_analyze), explicit label schemes (A1..C2), and exact distribution rules. It stops short of level 5 only because the prompt template still requires placeholder substitution per candidate and a couple of edge cases are described narratively rather than templated.

4 / 5

Workflow Clarity

A clearly sequenced 13-step Procedure is followed by an explicit Verification checklist (labels, corner assignment, prompt/color mapping, file path, batch-count match), and as a batch operation it does include validation. It is not level 5 because the workflow intentionally has no error-recovery feedback loop (retries/post-processing are forbidden by design), so the checklist is verification rather than a validate-fix-retry loop.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and all content lives inline, but it is well-organized into clearly headed sections (Procedure, Complexity budget, Shape language, Prompt skeleton, Delivery behavior, Pitfalls, Verification) with easy navigation. It does not reach level 5 because the skill exceeds the ~50-line simple-skill threshold, so some of the duplicated rule content could arguably be factored into a reference file.

4 / 5

Total

15

/

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 specific and distinct, cleanly stating what the skill produces and at what scale constraint. Its main weakness is the absence of any explicit 'Use when...' trigger guidance and missing common synonyms like 'logo' or 'brand character'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a user wants a mascot, IP character, or cute logo for a product, repo, app, or community.'

Broaden trigger-term coverage by including natural synonyms such as 'logo', 'brand character', and 'cute logo' that users would actually say.

Optionally name one more concrete action (e.g. 'generate' or 'produce batches of') to lift specificity toward a fuller action list.

DimensionReasoningScore

Specificity

Names the domain ('IP mascot marks') and a concrete action ('Design') plus a tangible constraint ('readable at 32px'), but lists only one action and is not comprehensive. It fits the 'names domain and 1-2 concrete actions' anchor and falls short of the multi-action level-4 anchor.

3 / 5

Completeness

The description gives a clear 'what' ('Design minimal cute IP mascot marks readable at 32px') but contains no 'Use when...' or equivalent explicit trigger guidance, which per the rubric caps completeness at 3. It is not level 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Includes natural terms like 'cute', 'IP mascot', and 'design' but omits common synonyms a user would actually say ('logo', 'brand character', 'mascot logo'), matching the 'some relevant keywords but missing common variations' anchor. It is above level 2 because the terms present are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

'Minimal cute IP mascot marks readable at 32px' carves a clear niche with distinct triggers and minimal conflict risk, with only minor overlap against closely related skills like pixel-art (listed as related_skills). It stops short of level 5 only because the trigger surface is narrow and could still overlap generic image-generation requests.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/creative/ip-as-logo/SKILL.md

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.