CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mate

Create custom desktop pet (Mate) characters with spritesheet and manifest. Use when the user asks to 'create a pet', 'make a desktop companion', 'design a mate character', 'generate a spritesheet for my pet', or wants to customize their desktop buddy. Generates a WebP spritesheet + manifest.json that can be loaded by MiMo Desktop's Mate system.

Quality

90%

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

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

A strong, self-contained skill document: everything is concrete and MiMo-specific, with a clear workflow, executable conversion commands, fallback chains, and a verification checklist. The gaps are minor — some duplicated statements, placeholder shell arithmetic, and no executable way to confirm the generated spritesheet's actual dimensions against the manifest.

Suggestions

Add an executable command to inspect the generated spritesheet's actual pixel dimensions (e.g. `sips -g pixelWidth -g pixelHeight spritesheet.webp` or `identify spritesheet.webp`) in Step 3, plus a recovery step for when the dimensions don't match the manifest (adjust manifest values or regenerate).

Replace the placeholder shell arithmetic (`WIDTH=$((frameWidth * columns))`) with an executable example using literal values consistent with the manifest example (e.g. `WIDTH=$((240 * 8))`), so the rasterize command is copy-paste ready.

Deduplicate the repeated content: state the idle-animation requirement and the delivery/refresh instructions once each instead of in both the schema/layout sections and the Constraints/Step 4 sections.

DimensionReasoningScore

Conciseness

The body is almost entirely system-specific information Claude cannot know (manifest schema, spritesheet layout rules, MiMo Desktop constraints) with no basic-concept explanations, but contains minor duplicates: the idle requirement is stated twice ("The `idle` animation is **required**" and "The `idle` animation MUST exist") and the delivery path is explained in both the Output Structure section and Step 4. These are trim candidates rather than padding, so it sits above anchor 3 but short of the every-token-earns-its-place level 5.

4 / 5

Actionability

Mostly executable guidance: complete copy-paste manifest JSON, concrete commands (`cwebp -lossless -q 100`, `sips -s format webp`, `rsvg-convert`, `brew install webp`), and an explicit no-silent-rename rule. Minor gaps keep it below anchor 5: the dimension calculation `WIDTH=$((frameWidth * columns))` uses undefined placeholder variables (not executable as written) and the SVG fallback says to "generate pixel-art frames directly as SVG" without showing how.

4 / 5

Workflow Clarity

A clear four-step sequence (understand character → generate spritesheet → write manifest → deliver) with an explicit Step 3 verification checklist ("frameWidth × columns = spritesheet total width") and error-recovery fallback chains ("If `cwebp` is not available, check for `sips`... If neither tool is available, instruct the user to install one"). It falls short of anchor 5 because there is no validate→fix→retry loop if the dimension check fails, and no command given to inspect the generated image's actual dimensions to run the checklist.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into clearly headed sections (Output Structure, Manifest Schema, Spritesheet Layout, Workflow, Constraints) with nothing buried or nested. At ~155 lines it exceeds the under-50-line simple-skill exception, and the manifest field tables are borderline content that could live in a reference file, which fits anchor 4's 'minor organization gaps' better than anchor 5.

4 / 5

Total

16

/

20

Passed

Description

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

An exemplary description: third-person voice, concrete artifacts and formats for the 'what', an explicit 'Use when' clause with five natural trigger phrases and synonyms for the 'when', and a distinct niche with minimal conflict risk. No fluff or over-claims.

DimensionReasoningScore

Specificity

"Create custom desktop pet (Mate) characters with spritesheet and manifest" and "Generates a WebP spritesheet + manifest.json that can be loaded by MiMo Desktop's Mate system" name the concrete actions, artifacts, and formats, comprehensively covering the skill's outputs. Anti-drift check against anchor 4: no coverage gap can be identified — the partial repetition of spritesheet/manifest is redundancy, not a missing action.

5 / 5

Completeness

Both questions are answered explicitly: what ("Create custom desktop pet (Mate) characters with spritesheet and manifest... Generates a WebP spritesheet + manifest.json") and when ("Use when the user asks to 'create a pet'...") with concrete trigger phrases, exactly matching the anchor 5 example pattern. Anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Five natural user phrases are quoted verbatim — "create a pet", "make a desktop companion", "design a mate character", "generate a spritesheet for my pet", "customize their desktop buddy" — with synonym coverage (pet/companion/buddy/mate) matching anchor 5's comprehensive-synonyms standard; no common user variant is missing.

5 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche ("MiMo Desktop's Mate system" custom pets) with triggers ('mate character', 'spritesheet for my pet') that are unlikely to fire for any other skill, satisfying anchor 5's minimal-conflict standard.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

XiaomiMiMo/MiMo-Code

Path

packages/cli/src/skill/builtin/.bundle/mate/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.