x-article-publisher

自媒体创作者与内容创作者在需要将 Markdown 长文发布到 X (Twitter) Articles 编辑器时使用。技能自动将 Markdown 转换为富文本并完美保留排版，支持持久化免密登录与封面上传，一键完成发布，大幅提升长文分发效率。

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/qiaomu-x-article-publisher/SKILL.md

Quality

Content

68%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 highly actionable with executable commands and a clear sequenced workflow, supported by a real, well-referenced scripts bundle. Its main weaknesses are decorative verbosity and the absence of an explicit validation checkpoint in the publishing workflow.

Suggestions

Add an explicit validation/verification step to the publish workflow (e.g., 'After draft save: confirm draft exists in editor; if save failed, re-paste and retry') to lift workflow clarity above 3.

Trim emoji decoration and marketing headlines ('一次认证，告别重复登录') to reduce token overhead without losing information.

Consider moving the lengthy smart title/cover generation guidance into a referenced file to tighten SKILL.md while keeping it discoverable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and a documented JSON schema, but emoji-laden marketing headers ('🎉 首次使用：一次认证，告别重复登录', '🧠 智能增强功能') and redundant phrasing add padding that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready, executable commands for every script (e.g., 'python publish_article.py --file article.md --headless'), documents parse_markdown.py's JSON output fields, and includes a concrete cover-image prompt template.	5 / 5
Workflow Clarity	The auto-publish workflow is clearly numbered (steps 1–9) and the Critical Rules enforce draft-only safety, but there is no explicit validate→fix→retry checkpoint; verification is left implicit/manual ('请在浏览器中检查'), which caps an outward-facing publishing workflow at 3.	3 / 5
Progressive Disclosure	Good section structure with a dedicated Scripts section listing each real bundle file (publish_article.py, parse_markdown.py, etc.) one level deep and one external guide link; minor organization gaps remain since the smart title/cover guidance is fairly long inline.	4 / 5
	Total	15 / 20 Passed

Description

87%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, explicit description that clearly states both capability and trigger conditions in third person, with a well-scoped niche. It is held back only by marketing-style over-claims and slightly thin synonym coverage.

Suggestions

Drop over-claims and fluff ('完美保留排版', '大幅提升长文分发效率') in favor of concrete, verifiable phrasing.

Add common synonyms and the file extension users might mention (e.g., '.md', 'Markdown 文件', 'X 长文') to broaden trigger coverage.

Lead with the trigger phrase rather than the audience ('自媒体创作者...') so the 'Use when' guidance reads as a natural user utterance.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('自动将 Markdown 转换为富文本', '持久化免密登录', '封面上传', '一键完成发布'), but over-claims like '完美保留排版' and fluff like '大幅提升长文分发效率' keep it just below the comprehensive, clean anchor 5.	4 / 5
Completeness	Explicitly answers both what ('自动将 Markdown 转换为富文本并...支持持久化免密登录与封面上传') and when ('...在需要将 Markdown 长文发布到 X (Twitter) Articles 编辑器时使用'), with a concrete 'Use when'-equivalent trigger clause.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('Markdown 长文', 'X (Twitter) Articles', '发布'), but is missing common synonyms/extensions and leans on user-type phrasing ('自媒体创作者与内容创作者') over pure trigger keywords.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — publishing Markdown to the X Articles editor — with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing, 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: anbeime/skill
Path: skills/qiaomu-x-article-publisher/SKILL.md
Commit: d9e888d

Reviewed: 2 days 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.