CtrlK
BlogDocsLog inGet started
Tessl Logo

content-creation-publisher

内容创作者与自媒体创作者在需要将网页素材转化为多平台图文时,使用本技能可自动完成网页提取、Markdown排版美化、智能配图,并一键发布至微信公众号与X/Twitter,轻松实现从采集到发布的一站式自动化工作流。

48

Quality

53%

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/content-creation-publisher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%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 body is a well-organized but heavily padded orchestration overview: it clearly maps modules and workflows yet gives Claude almost nothing executable to run them, and it inlines content that belongs in reference files. The skill reads more like documentation about a pipeline than instructions for operating it.

Suggestions

Add executable invocations for each module (e.g. the actual command or script call for baoyu-url-to-markdown and the API-mode flow with WECHAT_APP_ID/WECHAT_APP_SECRET), turning the descriptive 操作步骤 into runnable ones.

Insert an explicit validation checkpoint into each publishing workflow (human review of rendered output before release) — required since publishing and the 批量处理 section are outward-facing/batch operations, and currently the review advice is only in a separate notes section.

Cut redundancy and move detail out of SKILL.md: the module list appears three times, and the 协同技能组合, 更新日志, 故障排查, and example sections could be collapsed into one concise overview plus one-level-deep reference files in a references/ directory.

DimensionReasoningScore

Conciseness

The ~430-line body has several padded and redundant sections: the module list is repeated three times (核心功能模块, 资源索引, 技能组成), plus 协同技能组合 enumerating dozens of combinations, a changelog, and a marketing footer. Not a 1 because the module descriptions themselves stay at overview level rather than explaining concepts Claude already knows.

2 / 5

Actionability

Almost everything describes what each module does rather than how to execute it — the only runnable commands are version checks and 'npm install'. There are no invocations of the referenced scripts (e.g. baoyu-url-to-markdown/scripts/main.ts), no API-mode usage example despite mentioning WECHAT_APP_ID/WECHAT_APP_SECRET, and no content-generation prompts for article-illustrator. The structure of steps exists but the specifics needed to actually run anything are missing.

2 / 5

Workflow Clarity

The four workflows and per-module 操作步骤 give a clear sequence, but none includes a validation checkpoint — publishing is an outward-facing operation and the 高级功能 section adds batch/scheduled publishing, and the batch-ops cap applies (validation is only suggested in a separate 注意事项 section, not embedded in any workflow). Not a 2 because the sequences themselves are coherent and complete.

3 / 5

Progressive Disclosure

Structure is decent (clear section headers, a 资源索引 pointing one level deep into sub-skill files), but no bundle files (references/, scripts/, assets/) exist — all module details, troubleshooting, examples, and prerequisite content are inlined in one long file that should largely live in separate reference files. The references that do exist point outside the skill, so navigation depends on skills not bundled here.

3 / 5

Total

10

/

20

Passed

Description

71%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 solid description that names four concrete pipeline actions and includes an explicit when-clause with natural Chinese trigger terms. Its main weaknesses are overlap with the sub-skills it composes and a scope-of-triggers gap between the description and the broader capabilities the body claims.

Suggestions

Add a distinguishing cue such as '完整工作流编排' or '整合采集、排版、配图、发布全流程' so the description doesn't collide with the individual baoyu-* sub-skills on the same trigger words.

Broaden the when-clause to include partial-use triggers (仅排版优化、仅配图、仅发布) that the body explicitly supports, matching the anchor-5 'what AND when with concrete trigger phrases' pattern.

Drop the marketing filler ("轻松实现...一站式自动化工作流") — it adds tokens without adding capability or trigger information.

DimensionReasoningScore

Specificity

The description lists several specific concrete actions — "网页提取、Markdown排版美化、智能配图,并一键发布至微信公众号与X/Twitter" — covering the full pipeline. It falls short of a 5 because trailing marketing filler ("轻松实现从采集到发布的一站式自动化工作流") pads rather than adds capability detail.

4 / 5

Completeness

Both 'what' (extract, format, illustrate, publish to WeChat and X) and 'when' ("在需要将网页素材转化为多平台图文时") are explicit, so it clears the missing-trigger cap. Not a 5 because the when-clause covers only the collection-to-post scenario and omits the formatting-only, illustration-only, and publish-only triggers the body claims.

4 / 5

Trigger Term Quality

It includes natural phrases users would actually say: 微信公众号, X/Twitter, 网页, 排版, 配图, 发布. Not a 5 because common variations (e.g. 发推, 推文, 公众号文章) are missing and the opener addresses a user persona rather than natural query phrasing.

4 / 5

Distinctiveness Conflict Risk

The niche (web-material-to-WeChat/X publishing pipeline) is somewhat specific, but the description uses the exact same trigger vocabulary as the sub-skills it orchestrates (baoyu-url-to-markdown, baoyu-post-to-wechat, baoyu-post-to-x), creating real overlap risk. Not a 4 because nothing in the description disambiguates it from those closely related skills.

3 / 5

Total

15

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 8 missing, 4 deeper-than-1-level, 1 suspicious

Warning

Total

14

/

16

Passed

Repository
anbeime/skill
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.