Knowledge comic creator supporting multiple art styles and tones. Creates original educational comics with detailed panel layouts and sequential image generation. Use when user asks to create "知识漫画", "教育漫画", "biography comic", "tutorial comic", or "Logicomix-style comic".
85
85%
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 its purpose, lists concrete capabilities, and provides explicit trigger terms in both Chinese and English. It effectively distinguishes itself from generic image generation or generic comic skills by specifying educational/knowledge comics with panel layouts and sequential generation. The inclusion of specific comic subtypes as trigger terms is particularly effective.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'supporting multiple art styles and tones', 'creates original educational comics', 'detailed panel layouts', and 'sequential image generation'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates educational comics with detailed panel layouts and sequential image generation) and 'when' (explicit 'Use when' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms in multiple languages: '知识漫画', '教育漫画', 'biography comic', 'tutorial comic', 'Logicomix-style comic'. These are terms users would naturally say when requesting this type of content. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining educational content with comic creation, specific art styles, and panel layouts. The bilingual trigger terms and specific comic types like 'Logicomix-style' make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%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, comprehensive skill with excellent workflow clarity and progressive disclosure. Its main weaknesses are redundancy (the workflow is described three different ways in the main file) and incomplete actionability (key operations like image generation invocation and PDF merging lack concrete, executable examples). Trimming duplicate workflow representations and adding specific command examples would significantly improve it.
Suggestions
Consolidate the three workflow representations (checklist, flow diagram, step summary table) into one authoritative format to reduce redundancy and improve conciseness.
Add concrete, executable command examples for key operations like invoking the image generation skill and running the merge-to-pdf script (e.g., `bun {baseDir}/scripts/merge-to-pdf.ts comic/alan-turing-bio/`).
Move the detailed art style, tone, and compatibility matrix tables to reference files since they are lookup data, keeping only a brief summary in the main SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) with significant redundancy — the workflow is described three times (checklist, flow diagram, step summary table), and Step 7 details are repeated in both the step summary and a dedicated section. The compatibility matrix and style/tone tables are useful reference but could be offloaded to reference files. However, it does avoid explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete file structures, CLI options, and step sequences, but lacks executable code examples for key operations. Image generation delegates to an external skill without showing exact invocation syntax. The merge-to-PDF script is referenced but never shown with a concrete command. Many steps say 'invoke an installed image generation skill' without specifying the exact call pattern. | 2 / 3 |
Workflow Clarity | The workflow is exceptionally well-structured with a progress checklist, flow diagram, step summary table, blocking indicators (⛔), required markers (⚠️), and conditional steps clearly labeled. Validation checkpoints are present (character sheet before pages, EXTEND.md blocking check, backup rules before overwriting). Error recovery is addressed with backup naming conventions and auto-retry on failure. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in SKILL.md and well-signaled one-level-deep references to specific files (references/workflow.md, references/auto-selection.md, references/config/*, references/art-styles/*, etc.). The References section is well-organized by category. Content is appropriately split between the main file and detailed reference documents. | 3 / 3 |
Total | 10 / 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 | |
9eb032a
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.