BC meitu-skills
Root entry skill for Meitu capabilities. Routes requests to scene skills (meitu-poster, meitu-stickers, meitu-visual-me, meitu-product-swap, meitu-video-dance, meitu-upscale, meitu-product-view, meitu-image-fix, meitu-id-photo, meitu-cutout, meitu-carousel, meitu-beauty, meitu-image-adapt) or meitu-tools for direct Meitu CLI tool execution.
Root entry skill for Meitu capabilities.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "requirements"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (meitu-skills) differs from the folder (other-openclaw-skills)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 89 steps, 3 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1930 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 342: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 89 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.