CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

article-illustrator

内容创作者与自媒体创作者在撰写长文缺乏视觉辅助时,当需要给文章配图或生成插图请使用。自动分析文章结构,精准识别位置并生成插画插入段落,将抽象概念具象化。一键完成智能图文排版,省去手动找图时间,大幅提升阅读体验!

61

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/article-illustrator/article-illustrator/SKILL.md

The canonical home for this skill is article-illustrator in anbeime/skill

SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instructional body with genuinely actionable templates, naming conventions, and insertion rules, supported by an appropriate two-file reference split. The main gaps are redundancy between the 任务目标/配图策略 sections and the workflow steps, and the absence of validation/retry checkpoints for what is a batch generate-and-modify operation.

Suggestions

Add an explicit validation checkpoint for the batch operation: after each image is generated, verify the file exists at imgs/illustration-[slug].png and that the inserted Markdown reference resolves, with a fix-and-retry loop before moving to the next image (this lifts workflow_clarity past its current batch-operation cap).

Merge or trim the redundant sections — fold 任务目标 into the opening paragraph and collapse 配图策略's 识别关键位置/优先级排序 and 风格选择原则 into 步骤二 and 步骤四 (or delegate the style mappings entirely to references/style-guide.md) — to remove the duplicated content hurting conciseness.

Make the two vague execution steps concrete: specify the actual command/approach for fetching a URL article (e.g. a curl or WebFetch call to a temp file) and state precisely which image-generation capability/parameters to use in 步骤四.

DimensionReasoningScore

Conciseness

The body is mostly lean checklists with no concept-explanation padding, but there is real redundancy: "任务目标" restates the opening line, and "配图策略" re-covers 步骤二's analysis (识别关键位置/优先级排序) and 步骤四's style rules (风格选择原则 vs. the style list in 图片属性). This puts it at anchor 3 — mostly efficient but with sections that could be merged or trimmed — rather than anchor 4's 'minor instances'.

3 / 5

Actionability

Concrete, copy-paste-level guidance dominates: the plan template, naming rule "illustration-[slug].png" with valid examples, insertion syntax "![配图描述](imgs/illustration-[slug].png)", alt-text length (5-10 字), and the final summary template. It stays at 4 rather than 5 because two execution details are underspecified — how a URL article is actually fetched ("自动下载 Markdown 内容到临时位置", no command) and how image generation is invoked ("使用图像生成能力", no tool/parameters).

4 / 5

Workflow Clarity

Six steps are clearly sequenced, but this is a batch operation (N images generated, article file modified) whose only validation is the final summary's failure list — there is no per-image verify/retry loop and no check that inserted image references resolve before declaring completion. Per the rubric's cap for batch operations without validation feedback loops, workflow clarity is capped at 3 even though the sequence itself is well ordered.

3 / 5

Progressive Disclosure

Structure is good: the body carries the workflow while style specs and the terminology table are split into real, one-level-deep files ([references/style-guide.md](references/style-guide.md) and [references/terminology.md](references/terminology.md) both exist), clearly signaled both inline (步骤四) and in a dedicated 资源索引 section. It falls short of anchor 5 because some reference-bound detail is duplicated inline (the five-mapping 风格选择原则 list and the style list in 图片属性 overlap the style guide's territory).

4 / 5

Total

14

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it explicitly states both capability (analyze, locate, generate, insert, concretize) and concrete trigger conditions in natural language, with good synonym coverage. Its only real weakness is the promotional closing sentence ("一键完成...大幅提升阅读体验!"), which adds over-claim without informational value.

DimensionReasoningScore

Specificity

The description names several concrete actions — "自动分析文章结构,精准识别位置并生成插画插入段落,将抽象概念具象化" (analyze article structure, identify positions, generate and insert illustrations, concretize abstract concepts) — but the tail "一键完成智能图文排版...大幅提升阅读体验!" is marketing fluff/over-claim that pads rather than informs, keeping it below the comprehensive-and-clean anchor 5.

4 / 5

Completeness

Both halves are explicit: the "what" is the concrete action chain (analyze structure → identify positions → generate and insert illustrations → concretize concepts), and the "when" is a concrete use-when clause — "在撰写长文缺乏视觉辅助时,当需要给文章配图或生成插图请使用". This matches the anchor-5 example's what+when-with-concrete-trigger-phrases pattern; it is well above anchor 4, where the 'when' would be only implicit or less specific.

5 / 5

Trigger Term Quality

It includes natural user phrasings with synonym coverage — "给文章配图" (add images to an article), "生成插图" (generate illustrations), "插画" (illustrations) — which are exactly what a Chinese-speaking user would say. A few natural variants are absent (e.g. "为文章生成一些图片", no file-extension or English terms), so it is not anchor 5's comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The niche — inserting generated illustrations into long-form articles — is distinct and its triggers (配图/插图/插画 for articles) are unlikely to hijack unrelated skills. Minor overlap risk remains with generic image-generation or chart/dataviz skills, which keeps it at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

anbeime/skill

Path

skills/article-illustrator/article-illustrator/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.