Generate professional infographics with 21 layout types and 21 visual styles. Analyzes content, recommends layout×style combinations, and generates publication-ready infographics. Use when user asks to create "infographic", "信息图", "visual summary", "可视化", or "高密度信息大图".
91
92%
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 clearly communicates specific capabilities (infographic generation with defined layout and style options), provides explicit trigger guidance with a 'Use when' clause, and includes bilingual trigger terms for broader coverage. The description is concise, uses third-person voice correctly, and carves out a distinct niche that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete capabilities: 'Generate professional infographics with 21 layout types and 21 visual styles', 'Analyzes content', 'recommends layout×style combinations', and 'generates publication-ready infographics'. These are specific, actionable descriptions. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate infographics with 21 layouts and 21 styles, analyze content, recommend combinations) and 'when' (explicit 'Use when' clause with specific trigger phrases in multiple languages). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms in both English and Chinese: 'infographic', '信息图', 'visual summary', '可视化', '高密度信息大图'. These cover common ways users would phrase requests for infographic creation. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused specifically on infographic generation. The mention of '21 layout types and 21 visual styles' and bilingual trigger terms make it very unlikely to conflict with general visualization or charting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent progressive disclosure and clear workflow sequencing. Its main weakness is verbosity—several policy sections (Confirmation Policy, Image Generation Tools, User Input Tools) are repeated or cross-referenced redundantly, and the overall length could be reduced by 15-20% without losing clarity. The tables, galleries, and step-by-step workflow are strong and provide concrete, executable guidance.
Suggestions
Consolidate the Confirmation Policy into a single authoritative section and replace repeated references with a brief one-liner pointing to it, reducing redundancy.
Tighten the Image Generation Tools and User Input Tools sections—the priority-order resolution logic is over-specified for Claude's reasoning ability and could be condensed to a simple ordered list with fewer edge-case elaborations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300+ lines) with some sections that could be tightened—e.g., the detailed Image Generation Tools resolution logic, the User Input Tools section, and the Confirmation Policy are verbose for what they convey. However, most content is genuinely informational (tables, galleries, workflow steps) rather than explaining things Claude already knows. The repetition of confirmation policy references across multiple sections adds bloat. | 2 / 3 |
Actionability | The skill provides highly concrete guidance: specific CLI options, exact file paths and naming conventions, detailed workflow steps with explicit outputs at each stage, complete output directory structure, keyword shortcut tables with mapped behaviors, and clear fallback chains for tool selection. Every step produces a named artifact. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with explicit validation checkpoints: Step 4 is a hard confirmation gate before generation, backup rules are specified for existing files, retry logic on failure is included, and the confirmation policy creates a clear feedback loop. The workflow handles edge cases (file conflicts, missing backends, language mismatches) with explicit instructions. | 3 / 3 |
Progressive Disclosure | The skill is an excellent overview that keeps galleries and options as concise tables while pointing to one-level-deep references for full definitions (e.g., `references/layouts/<layout>.md`, `references/styles/<style>.md`, `references/base-prompt.md`, `references/config/preferences-schema.md`). Navigation is clear and references are well-signaled throughout. | 3 / 3 |
Total | 11 / 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.