CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

huashu-image-upload

文章配图一键生成并上传图床,自动插入Markdown链接。当用户提到"配图"、"插图"、"上传图片"、"文章配图"时使用。

Quality

75%

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 ./huashu-image-upload/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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.

The content has a clear sequenced workflow with a checklist, verification step, and concrete upload/insert commands, but is dragged down by padding (promo footer, success cases, dated metadata), vague image-acquisition steps, inconsistent script paths, and external absolute-path references instead of a proper bundle structure.

Suggestions

Remove the promotional footer, maintainer block, '成功案例' section, and the '最后更新' date to cut padding; if version-specific details like doubao-seedream-4-0-250828 matter, put them in a dedicated reference file rather than the body.

Make the image-acquisition steps executable: add a concrete doubao-seedream API call example and a concrete WebFetch/Wikimedia Commons lookup procedure, and use one consistent script path for upload_image.py throughout.

Move detailed material (image source priority details, image specs, FAQ) into reference files inside the skill bundle (e.g. references/sources.md, references/faq.md) and link them clearly from a lean SKILL.md overview instead of pointing at absolute paths on the author's machine.

DimensionReasoningScore

Conciseness

The body is mostly efficient structured guidance, but contains clear padding: a "成功案例" section, a promotional footer ("花叔出品 | 公众号「花叔」| 30万+粉丝 | 代表作…"), maintainer/last-updated metadata, and time-sensitive details (model version "doubao-seedream-4-0-250828", "最后更新: 2025-11-07") that are not in a deprecated section. This fits anchor 3 ('mostly efficient but some unnecessary explanation or could be tightened'), not anchor 4's 'minor instances'.

3 / 5

Actionability

The upload and insertion halves are concrete and copy-paste ready (`python3 …/tools/upload_image.py <URL>`, the `![图片描述](…)` template, `grep -n "!\["`), but the image-acquisition half stays high-level ("调用API生成图片", "WebFetch获取") with no executable API-call example, and the script path is inconsistent (`/tools/upload_image.py` on line 75 vs the full `/Users/alchain/…` path elsewhere). This lands between anchors 3 and 4 — incomplete concrete guidance — so 3.

3 / 5

Workflow Clarity

The 5-step standard flow is clearly sequenced, preceded by a pre-flight checklist, and ends with an explicit verification step (Step 5 grep + '所有图片链接验证通过'), plus a documented failure fallback ('上传失败时,自动使用原链接作为fallback'). Not anchor 5 because there is no validate→fix→retry loop for the batch upload operation (the grep check only inspects link syntax, not accessibility); clearly above anchor 3's 'checkpoints missing or implicit'.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the referenced materials (`/tools/README.md`, `/公众号写作/AI文生图API调用.md`, `配图Best Practice总结.md`) are external machine-specific absolute paths rather than well-signaled one-level-deep bundle links. The ~210-line body inlines content (image specs, FAQ, source-priority details) that could be split out, matching anchor 3 ('some structure… references present but not clearly signaled') rather than anchor 4.

3 / 5

Total

13

/

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: third-person voice, concrete actions covering the generate→upload→insert pipeline, and an explicit 'use when' clause with natural trigger phrases. Only minor improvements possible — drop the marketing-flavored "一键" and add one or two more trigger synonyms.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "一键生成并上传图床" (generate and upload to image host) and "自动插入Markdown链接" (auto-insert Markdown links) — covering the full pipeline with only a minor gap (verification is not mentioned, and "一键" is slightly promotional). This matches anchor 4 ('several specific actions; minor gaps') better than anchor 5, and is far above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

It explicitly answers both questions: what ("文章配图一键生成并上传图床,自动插入Markdown链接") and when ("当用户提到'配图'、'插图'、'上传图片'、'文章配图'时使用") with concrete trigger phrases — a direct match for anchor 5. It is not anchor 4 because the 'when' clause is already explicit and specific, not merely adequate.

5 / 5

Trigger Term Quality

Trigger terms "配图", "插图", "上传图片", "文章配图" are natural phrases a Chinese-speaking user would say, giving good keyword coverage. Not anchor 5 because common variations like "加图片"/"添加配图"/"生成图片" are missing; clearly above anchor 3's 'some relevant keywords but missing variations'.

4 / 5

Distinctiveness Conflict Risk

The niche (article illustration generation + image-host upload + Markdown insertion) is distinct with dedicated triggers, but terms like "上传图片" could also fire on a generic image-upload or general image-generation skill — minor overlap risk, matching anchor 4 rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alchaincyf/huashu-skills

Path

huashu-image-upload/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.