CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-keyboard-art-maker

Generate artistic top-down photos of keyboard keycaps arranged to spell out custom text messages.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary lean, single-purpose recipe: one clearly specified action with a complete prompt template, exact model and CLI details, input table, and operational fallbacks. The only flaw is trivial — a duplicated description line under the title.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and assumes Claude's competence (no library primers, no concept explanations), with only minor trimmable redundancy — the frontmatter description is restated verbatim as a bold line under the title, and "Submit the plan with ONE step" is slightly padded. This keeps it just below the "every token earns its place" level of 5.

4 / 5

Actionability

The guidance is fully executable: exact CLI command (`muapi image generate`), model id (`ideogram-v3-t2i`), a complete copy-paste prompt template with the `{{display_text}}` substitution, aspect ratio choice, auth setup (`muapi auth configure`), and a raw-endpoint curl fallback with polling. No key details are missing for the common case.

5 / 5

Workflow Clarity

This is a simple single-step skill and the single action is unambiguous: gather display_text (a table makes the single input explicit), generate via the specified model/prompt, then present the image to the user. It is not destructive or batch, so the missing-validation cap does not apply, and auth/fallback handling covers the realistic failure path.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and no bundle files exist to link — the body's well-organized sections (Inputs, Steps, Trigger Keywords, Notes) fully satisfy the simple-skill exception for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

62%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 precise, concrete, and clearly distinct from other skills, but it omits any "Use when..." trigger guidance, so it answers "what" without "when". Adding an explicit use-when clause with natural trigger phrases would lift both completeness and trigger-term quality.

Suggestions

Append a use-when clause, e.g. "Use when the user wants to spell out a message with keyboard keycaps, asks for keyboard art or a keycap image, or wants text rendered as custom keys."

Include natural trigger synonyms and phrasings users would actually say ("keyboard art", "keycap image", "spell with keys") in the description rather than only in the body's Trigger Keywords section.

Optionally mention output characteristics (e.g. square or 4:3 photo) to sharpen the "what" and further reduce ambiguity.

DimensionReasoningScore

Specificity

"Generate artistic top-down photos of keyboard keycaps arranged to spell out custom text messages" fully specifies a single concrete action with precise attributes (top-down, keycaps, spell, custom text). It is noticeably above the 3 anchor ("Names domain and 1-2 concrete actions") in precision, but does not list several distinct actions, so it does not reach 5.

4 / 5

Completeness

The "what" is clear (generate top-down keycap-art photos spelling custom text), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"keyboard keycaps" and "text messages" are natural user phrasings, but the description omits common variations and synonyms users would say ("keyboard art", "keycap image", "spell with keys"), matching the anchor for some relevant keywords with missing variations.

3 / 5

Distinctiveness Conflict Risk

The keycap-art niche is highly distinct — "top-down photos of keyboard keycaps arranged to spell out custom text messages" is unlikely to trigger for any other skill, so conflict risk is minimal.

5 / 5

Total

15

/

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/keyboard-art-maker/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.