AC xiaohongshu-note
Generate Xiaohongshu (Little Red Book) style image notes. Use when the user wants to create vertical 3:4 image posts for Xiaohongshu — knowledge cards, infographic-style notes, 干货图文, or multi-image posts with matching caption text. Produces: a set of 3:4 high-res PNG images (1080×1440 @2x) + a ready-to-post caption (title / body / hashtags). Trigger words: 小红书, xiaohongshu, 图文笔记, 干货图文, 种草图文, 知识卡片, 图文卡片. NOT for: PPT decks, course materials, or 讲师版 slides — those are separate workflows.
Generate Xiaohongshu (Little Red Book) style image notes.
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Generate Xiaohongshu (Little Red Book) style image notes. Use when… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 28 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 588 tokens
- 100Running it twice. No mutating operations
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 490: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.