x-article-publisher

内容创作者在需要将 Markdown 长文发布到 X (Twitter) 时，使用此技能一键将 Markdown 自动转换为富文本并发布至 X Articles，完美保留排版，免去手动调整与重复登录烦恼，让长文分发更高效。

Quality

72%

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/qiaomu-x-article-publisher-github/SKILL.md

Quality

Content

75%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 clear workflows, but carries promotional padding that hurts conciseness, and some detail that belongs in reference files is inlined.

Suggestions

Remove marketing fluff and decorative emoji headings (e.g. "🎉 首次使用：一次认证，告别重复登录") to improve token efficiency toward anchor 4–5.

Move the full parse_markdown.py JSON output schema and cover-image prompt templates into a separate reference file linked from the body, strengthening progressive disclosure.

Add an explicit validate/feedback step for the manual workflow (e.g. verifying the draft loaded correctly before handoff) to push workflow clarity to anchor 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes promotional fluff and emoji-heavy headings ("🎉 首次使用：一次认证，告别重复登录") and over-explanation of auth benefits that could be trimmed, matching anchor 3 rather than the lean anchor 4.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (e.g. `python publish_article.py --file article.md --title "..."`) with documented CLI flags, JSON output schema, and expected output, matching anchor 5.	5 / 5
Workflow Clarity	Clear numbered sequences for both auth setup and the publish flow with most checkpoints present; the manual-workflow fallback is vague ("手动操作浏览器发布") and error-recovery feedback loops are largely implicit, so it sits at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Scripts referenced in the body are real files (auth_manager.py, parse_markdown.py, copy_to_clipboard.py, publish_article.py all exist in scripts/) and the one external reference is clearly signaled, but the full JSON output schema and cover-generation prompt templates are inlined rather than split into reference files, leaving minor organization gaps at anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

70%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 communicates a specific niche and several concrete actions but omits an explicit "Use when..." trigger clause, capping completeness. Trigger-term coverage is good though not comprehensive.

Suggestions

Add an explicit trigger clause such as "Use when the user wants to publish long-form Markdown content to X (Twitter) Articles" to lift completeness to anchor 4–5.

Include natural synonyms and a file extension (e.g. "Markdown, .md, long-form posts, X Articles") to broaden trigger-term coverage.

Tighten marketing phrasing ("完美保留排版", "让长文分发更高效") into concrete capabilities to maximize specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — "将 Markdown 自动转换为富文本并发布至 X Articles，完美保留排版" — listing convert/publish/preserve-format actions with only minor coverage gaps, matching anchor 4 rather than the more comprehensive anchor 5.	4 / 5
Completeness	Has a clear "what" (convert Markdown to rich text and publish to X Articles) but no explicit "Use when..." trigger clause — the trigger is only implied — so per the missing-trigger guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ("Markdown 长文", "X (Twitter)", "X Articles", "发布") with good coverage, but lacks synonyms and file extensions, falling short of the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (publishing Markdown to X Articles) with distinct, low-conflict triggers, matching anchor 5's "clear niche with distinct triggers; minimal conflict risk."	5 / 5
	Total	16 / 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/qiaomu-x-article-publisher-github/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.