CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-logo-branding

Design a professional logo with full branding package — primary logo, variations (dark/light/icon-only), color palette, and real-world application mockups.

Quality

75%

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 ./library/visual/logo-branding/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, fully actionable recipe: concrete CLI commands, model choices with rationale, prompts, and fallback instructions leave nothing vague. Its only weaknesses are cosmetic — a redundant description restatement, two overlapping Notes sections, and no explicit retry loop for the brand-name spelling check.

DimensionReasoningScore

Conciseness

The body is efficient: an inputs table, four generation steps with exact commands, and terse model-specific Notes ("Ideogram v3 excels at text legibility") that provide genuinely non-obvious information. Minor trimmable padding exists — the bold restatement of the frontmatter description and two separate "Notes" sections — keeping it just below the lean anchor of 5.

4 / 5

Actionability

Fully executable throughout: exact `muapi image generate` commands with model IDs, complete copy-paste prompts with {{placeholder}} substitution guidance, aspect ratios per step, auth setup ("muapi auth configure"), a raw curl fallback with headers, and `muapi predict wait <request_id>` for polling. Everything needed to run the skill is concrete.

5 / 5

Workflow Clarity

Phases A/B are clearly sequenced with a post-generation checkpoint ("Present all 3 logo concepts and ask user to pick a favorite") and a validation note ("Always check that the brand name text is correctly spelled"). It is below 5 because the spelling check has no explicit failure-recovery loop (regenerate or retry guidance), leaving a minor validation gap.

4 / 5

Progressive Disclosure

The skill is a single well-sectioned file (Inputs, Steps, Notes, Trigger Keywords, agent notes) with no bundle files, and all content appropriately lives inline — matching the anchor of good structure with minor organization gaps. The duplicated "## Notes" and "## Notes for the Executing Agent" headings and the trailing horizontal-rule split keep it from a 5.

4 / 5

Total

17

/

20

Passed

Description

58%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 does a good job stating concrete deliverables for the logo/branding niche, but it omits any explicit "when to use" trigger guidance, which both caps completeness and weakens trigger-term quality. Adding a "Use when..." clause with natural user phrases would resolve the two lowest-scoring dimensions at once.

Suggestions

Append a trigger clause such as: "Use when the user asks for a logo, logo design, brand identity, or a full branding package for a company or product."

Include natural user phrasings and synonyms in the description itself (e.g. "logo design", "brand identity", "make/create a logo"), not just in the body's Trigger Keywords section.

State the action per deliverable (e.g. "Generates primary logo concepts, dark/light/icon-only variations, a color palette, and application mockups") so multiple concrete actions are explicit rather than one verb covering a list.

DimensionReasoningScore

Specificity

The description enumerates concrete deliverables — "primary logo, variations (dark/light/icon-only), color palette, and real-world application mockups" — listing several specific outputs. It falls short of a 5 because it relies on a single action verb ("Design") rather than multiple distinct concrete actions, and phrases like "full branding package" are partially redundant with the enumerated list.

4 / 5

Completeness

The "what" is clear and specific (design a logo with enumerated branding deliverables), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is above a 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ("logo", "branding package", "brand") but common natural variations users would say — "logo design", "brand identity", "create a logo for my..." — are absent from the description. It matches the anchor of having some relevant keywords while missing common variations or synonyms, and is below a 4 because there is no natural trigger phrasing at all.

3 / 5

Distinctiveness Conflict Risk

Logo/branding design is a well-defined niche with distinct triggers ("logo", "branding package"), giving mostly distinct behavior with minor overlap risk against general design or brand-guideline skills. It is not a 5 because without a "Use when" clause, broader design requests (e.g. general brand style work) could pull this skill in.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

SamurAIGPT/Generative-Media-Skills

Path

library/visual/logo-branding/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.