Analyzes article structure, identifies positions requiring visual aids, generates illustrations with Type × Style two-dimension approach. Use when user asks to "illustrate article", "add images", "generate images for article", or "为文章配图".
Install with Tessl CLI
npx tessl i github:jimliu/baoyu-skills --skill baoyu-article-illustratorOverall
score
92%
Does it follow best practices?
Validation for skill structure
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 well-crafted skill description that excels across all dimensions. It provides specific actions, includes natural trigger terms in both English and Chinese, explicitly states when to use it, and carves out a distinct niche for article-specific illustration generation. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyzes article structure', 'identifies positions requiring visual aids', 'generates illustrations with Type × Style two-dimension approach'. The methodology is explicitly named. | 3 / 3 |
Completeness | Clearly answers both what (analyzes structure, identifies positions, generates illustrations) AND when (explicit 'Use when' clause with specific trigger phrases). Meets all completeness criteria. | 3 / 3 |
Trigger Term Quality | Includes natural user phrases like 'illustrate article', 'add images', 'generate images for article', plus Chinese equivalent '为文章配图'. Good coverage of how users would naturally request this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on article illustration with a distinct methodology (Type × Style approach). Unlikely to conflict with general image generation skills due to the article-specific context and positioning analysis. | 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 workflow clarity and progressive disclosure. The main weakness is moderate verbosity - while the tables and structure are helpful, some content could be consolidated (e.g., Type/Style galleries and Auto Selection have overlapping information). The skill excels at providing concrete, executable guidance with clear validation checkpoints.
Suggestions
Consolidate the Type Gallery, Style Gallery, and Auto Selection tables into a single reference, as they contain overlapping information about when to use each type/style combination.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient with good use of tables, but includes some redundancy (e.g., the Type and Style galleries repeat information that could be consolidated, and some workflow steps have verbose explanations). The checklist and step structure add overhead that could be tightened. | 2 / 3 |
Actionability | Provides highly concrete guidance with specific file paths, exact markdown syntax for image insertion, clear YAML frontmatter examples, bash commands for checking files, and explicit AskUserQuestion prompts. The workflow is copy-paste ready with specific filenames and directory structures. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit checkpoints (Step 3 marked as REQUIRED), clear sequencing with numbered steps and sub-steps, validation points (checking existing images, confirming settings before proceeding), and error handling guidance (retry once, then log and continue). | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview in main file and one-level-deep references to detailed materials (styles.md, prompt-construction.md, usage.md, etc.). The References table provides clear navigation, and detailed specs are appropriately externalized to reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
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.