CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-logo-creator

Engineer professional-grade brand logos using geometric primitives and negative space — generates minimalist, scalable vector-style marks via muapi.ai

Quality

63%

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 ./.opencode/skills/muapi-logo-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 well-sectioned and mostly lean, with a genuinely useful taxonomy table and one concrete invocation example. However, the mandated briefing workflow is underspecified, the flat-design constraints are stated three times, and the central script reference points at a file that is not in the bundle. Fixing the dangling script reference and showing the actual brief format are the highest-impact improvements.

Suggestions

Ship the referenced scripts/create-logo.sh (and the core/media/generate-image.sh primitive it wraps) in the bundle, or remove the invocation example if the script does not exist — a dangling path to the core component breaks the whole skill.

Consolidate the flat-design/no-gradient/no-3D constraint into a single section; it currently appears in Branding Directives, the Prompt Optimization Protocol, and Constraints & Guardrails.

Show a concrete example of the required 'Geometric Minimalist Brief' (or the argument that carries it) so the agent knows exactly what to pass to the script, and add a post-generation validation step (e.g., check the output is a centered flat mark on a plain background).

DimensionReasoningScore

Conciseness

The body is mostly efficient (compact taxonomy table, bullet directives), but 'flat design only / no gradients or 3D' is repeated three times — in Branding Directives ('Flat design ONLY. No gradients, 3D effects, or photorealistic textures'), in the Prompt Optimization Protocol ('Flat design only. NO gradients or 3D effects'), and in Constraints & Guardrails — and the opening line restates the frontmatter description. This lands between the mostly-efficient 3 anchor and the minor-trim 4 anchor; the triple repetition makes it a 3.

3 / 5

Actionability

There is one concrete bash example ('bash scripts/create-logo.sh --brand "Aura" --concept ... --style minimalist --color "black and gold"'), but the 'Geometric Minimalist Brief' the protocol mandates is never shown or parameterized, the script's outputs and full argument set are undocumented, and the invoked script file is absent from the bundle. Concrete-but-incomplete matches anchor 3, not the mostly-executable 4.

3 / 5

Workflow Clarity

A two-step sequence exists ('Step 1: Define the Brand Brief' → 'Step 2: Invoke the Script') but there are no validation checkpoints (e.g., verifying the generated mark meets the constraints or is legible at small sizes) and the middle is ambiguous — how the refined brief actually reaches the script is unstated. Sequence present with missing checkpoints is anchor 3; it is not 2 because the steps that do exist are clearly written.

3 / 5

Progressive Disclosure

Sections are well organized with clear headers, but the skill is ~75 lines (beyond the under-50-line simple-skill exception) and both referenced paths — 'scripts/create-logo.sh' and 'core/media/generate-image.sh' — do not exist in the bundle, so navigation to the load-bearing component is broken. Good inline structure with a dangling primary reference sits at anchor 3 rather than 4.

3 / 5

Total

12

/

20

Passed

Description

61%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.

A reasonably specific, third-person description with natural trigger terms, but it omits any 'Use when...' trigger guidance and misses common synonyms like 'logo design' or 'brand identity'. It is distinctive within the logo-design niche. Adding an explicit use-when clause and broader natural phrasing would lift it to the top tier.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to create, design, or redesign a logo, brand mark, monogram, or brand identity.'

Include natural synonyms users would say — 'logo design', 'brand identity', 'icon/mark' — to broaden trigger coverage.

Drop the buzzword 'professional-grade' in favor of one more concrete capability (e.g., outputs production-ready flat vector marks suitable from favicon to billboard).

DimensionReasoningScore

Specificity

The description names the domain and a couple of concrete actions/techniques — 'Engine professional-grade brand logos using geometric primitives and negative space', 'generates minimalist, scalable vector-style marks' — but stops short of the comprehensive action list of the level-4 anchor. It reads like 'Processes PDF files and extracts content': domain plus 1-2 actions, with the actual workflow (briefing, generation, iteration) uncovered.

3 / 5

Completeness

The 'what' is clear (engineer logos via geometric primitives, negative space, and muapi.ai generation), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when' is at best weakly implied by 'via muapi.ai'. Per the judging guidelines, a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

It contains natural phrases users would actually say — 'brand logos', 'logos', 'minimalist', 'vector', 'brand' — matching the 'good keyword coverage' anchor. It is not a 5 because common variations and synonyms like 'logo design', 'create a logo', 'brand identity', 'brand mark', or 'icon design' are missing.

4 / 5

Distinctiveness Conflict Risk

Logo/brand-mark creation is a clear niche with distinct triggers, so it would rarely fire for the wrong skill. It is not a 5 because it overlaps with generic image-generation skills — the body itself says it is a layer over a generate-image primitive.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

SamurAIGPT/Generative-Media-Skills

Path

.opencode/skills/muapi-logo-creator/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.