[Deprecated: use baoyu-image-cards] Generates Xiaohongshu (Little Red Book) image card series with 12 visual styles, 8 layouts, and 3 color palettes. Breaks content into 1-10 cartoon-style image cards optimized for XHS engagement. Use when user mentions "小红书图片", "XHS images", "RedNote infographics", "小红书种草", "小绿书", "微信图文", "微信贴图", or wants social media infographic series for Chinese platforms.
82
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that excels across all dimensions. It provides specific capabilities (styles, layouts, palettes, card counts), comprehensive bilingual trigger terms covering natural user phrases, and a clear 'Use when' clause. The deprecation notice is a minor concern as it adds noise, but the core description is well-crafted and highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and parameters: 'Generates Xiaohongshu image card series', '12 visual styles, 8 layouts, and 3 color palettes', 'Breaks content into 1-10 cartoon-style image cards optimized for XHS engagement'. These are highly specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates Xiaohongshu image card series with specific styles/layouts/palettes, breaks content into cartoon-style cards) and 'when' (explicit 'Use when' clause with detailed trigger terms and use cases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms in both Chinese and English: '小红书图片', 'XHS images', 'RedNote infographics', '小红书种草', '小绿书', '微信图文', '微信贴图', and 'social media infographic series for Chinese platforms'. Covers multiple natural variations users would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting Xiaohongshu/XHS platform specifically with Chinese social media terms. The deprecation notice even points to a successor skill, and the trigger terms are very specific to this platform, making conflicts with other skills unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with excellent workflow clarity, clear validation gates, and comprehensive branching paths. However, it severely suffers from verbosity — the main SKILL.md inlines extensive reference material (preset tables, compatibility matrices, palette specs, auto-selection tables) that it already points to via external reference files, making it far too long for a top-level skill document. The progressive disclosure structure exists but is undermined by the redundant inline content.
Suggestions
Move the full preset tables, Style × Layout compatibility matrix, auto-selection signal table, and palette hex codes into their respective reference files, keeping only a 1-2 line summary with a link in the main SKILL.md.
Consolidate the Styles, Layouts, and Palettes sections to brief one-line-per-item lists with pointers to the detailed reference files that already exist.
The 'User Input Tools' and 'Image Generation Tools' preamble sections are generic infrastructure concerns — consider moving them to a shared config or EXTEND.md reference rather than occupying ~40 lines of the main skill body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~400+ lines. It includes extensive tables, matrices, preset lists, and configuration details that could easily be offloaded to reference files. Much of the content (e.g., the full Style × Layout compatibility matrix, all preset tables, palette hex codes, auto-selection signal tables) belongs in reference docs, not the main SKILL.md body. | 1 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific CLI options, exact file naming conventions, explicit workflow steps, concrete prompt file requirements, specific directory structures, and detailed examples of completion reports and confirmation displays. The instructions are copy-paste ready and leave little ambiguity. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Steps 0-4) with explicit blocking gates (Step 0 BLOCKING, Step 2 REQUIRED), validation checkpoints (confirmation policy, backup rules before overwrites), feedback loops (auto-retry on failure), and clear branching paths (A/B/C). The image-1 anchor chain is called out as critical. Destructive operations have backup rules. | 3 / 3 |
Progressive Disclosure | The skill does reference 15+ external files appropriately and has a clear references table. However, the main SKILL.md inlines far too much detail that should live in those reference files — the full preset tables, compatibility matrix, auto-selection table, palette hex codes, and outline strategy details all bloat the main file when they could be summarized with pointers to the referenced docs. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
505a7e1
Table of Contents
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.