content-creation-publisher

内容创作与发布全流程技能，整合网页采集、Markdown格式化、智能配图、多平台发布（微信公众号、X/Twitter）功能，实现从内容获取到发布的一站式解决方案

Quality

45%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/content-creation-publisher/SKILL.md

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 well-structured with clear modules, workflows, prerequisites, and troubleshooting, but it is notably verbose with repeated sub-skill lists and vague high-level steps rather than executable guidance, and its publishing/batch workflows lack the validation checkpoints the rubric requires. It functions as an overview/index but earns little per-token efficiency.

Suggestions

Collapse the repeated sub-skill listings (核心功能模块 / 资源索引 / 协同技能 / 技能组成) into a single authoritative index to remove redundancy.

Add executable invocation examples for the referenced scripts (e.g. how to run baoyu-url-to-markdown/scripts/main.ts with a URL) instead of only high-level operation steps.

Insert validation checkpoints into the publishing and batch workflows (e.g. preview → human review confirm → publish) so workflow_clarity can exceed the destructive/batch cap of 3.

Dimension	Reasoning	Score
Conciseness	Several padded/redundant sections — the sub-skill list recurs in 核心功能模块, 资源索引, 协同技能, and 技能组成, plus vague 高级功能/模板系统 fluff and an emoji footer — fitting 'noticeably verbose; several unnecessary explanations or padded sections'; not a 3 because the redundancy is substantial rather than incidental.	2 / 5
Actionability	操作步骤 are high-level hints ('提供网页URL'、'自动提取并转换为Markdown') with no executable invocation of the referenced scripts, and the only concrete commands are `node/chrome --version` and `npm install`; matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute'.	2 / 5
Workflow Clarity	Four workflows are clearly sequenced with arrow diagrams, but publishing and batch operations are outward-facing/irreversible with no validation checkpoints, so per the rubric cap workflow_clarity cannot exceed 3 — 'steps listed but validation gaps; checkpoints missing'.	3 / 5
Progressive Disclosure	No bundle files exist; the body is well-sectioned and points one-level-deep to sibling skill SKILL.md files in a 资源索引, but large inlined blocks (44协同技能 list, four example workflows, 高级功能) that could be separate are kept inline, fitting 'some structure but could be better organized'.	3 / 5
	Total	10 / 20 Passed

Description

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

The description clearly conveys the skill's scope (content collection → formatting → illustration → multi-platform publishing) with concrete named functions and platforms, but it omits any explicit 'Use when...' trigger guidance and leans on buzzword fluff like '一站式解决方案'. As an aggregator it also carries notable overlap risk with its constituent sub-skills.

Suggestions

Add an explicit trigger clause, e.g. '当用户需要采集网页、格式化Markdown、为文章配图或发布到微信公众号/X时使用本技能'.

Trim the marketing filler '全流程技能' and '一站式解决方案' to keep the description concise and concrete.

Clarify how this aggregator differs from invoking its sub-skills directly, to reduce conflict risk with the wrapped skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete functions (网页采集、Markdown格式化、智能配图、多平台发布到微信公众号和X/Twitter), matching the 'lists several specific actions' anchor; not a 5 because '一站式解决方案' is fluffy and coverage of each action is shallow.	4 / 5
Completeness	Clearly states what the skill does, but there is no 'Use when...' or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3 (clear 'what', 'when' missing/weakly implied).	3 / 5
Trigger Term Quality	Contains relevant natural terms (微信公众号、X/Twitter、Markdown、配图、采集) but is feature-list styled rather than trigger-phrase styled and misses common user variations; fits 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming specific platforms gives it a somewhat distinct niche, but as an aggregator it overlaps heavily with the very sub-skills it wraps and the 44协同技能, fitting 'somewhat specific but could still overlap with similar skills'.	3 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

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
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
Path: skills/content-creation-publisher/SKILL.md
Commit: e768930

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.