CtrlK
BlogDocsLog inGet started
Tessl Logo

x-article-publisher

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

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 — every documented command is real and executable, with a clean one-click workflow and sensible safety rules (draft-only, no auto-publish). Its weaknesses are token efficiency (marketing framing, re-taught concepts, duplicated auth explanations) and progressive disclosure (undocumented bundle scripts and a dangling cross-skill reference).

Suggestions

Cut the promotional framing and emoji-laden step decoration, and deduplicate the auth-status workflow (keep it in one place); drop the '好标题的特点' tutorial since Claude already knows how to write engaging titles.

Move the smart title/cover generation guidance and the full parse_markdown.py output spec into a reference file, keeping SKILL.md as a lean overview.

Either document the debug_editor.py, debug_page.py, and site_config.py scripts or remove/clarify the broken external reference to '../skill-development-guide/technical-lessons.md', and add a verification step for leftover '@@@IMG_X@@@' markers.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections: celebratory marketing framing ('🎉 首次使用:一次认证,告别重复登录'), a title-writing tutorial ('好标题的特点:包含数字或具体细节…激发好奇心') that re-teaches what Claude already knows, and the auth-check workflow explained twice (the '自动化工作流' list and the '一键发布' auto-steps). It is not a 3 because the redundancy and emoji padding run throughout rather than being isolated instances.

2 / 5

Actionability

All commands are copy-paste ready and match the actual script CLIs (publish_article.py --file/--headless/--title, auth_manager.py setup/status/validate/clear/reauth, parse_markdown.py --output/--html-only), the parse output JSON schema is documented, and the closing Example covers the common case end-to-end with expected output.

5 / 5

Workflow Clarity

Clear sequence (one-time auth setup → run publish_article.py → script auto-executes 9 steps → draft saved with browser kept open for manual review), plus an auth-status checkpoint with an auto-recovery prompt to re-run setup. Not a 5 because verification checkpoints are implicit: Critical Rule 3 requires cleaning leftover '@@@IMG_X@@@' markers but no step shows how to check for them, and there is no explicit post-paste content verification.

4 / 5

Progressive Disclosure

Section structure is reasonable and the main scripts are documented, but 3 of the 7 bundle scripts (debug_editor.py, debug_page.py, site_config.py) are never mentioned, and the only outbound reference points outside the bundle to '../skill-development-guide/technical-lessons.md', which does not exist in this skill — buried/broken navigation. Above a 2 because the core workflow content is well organized and the primary scripts are clearly signaled.

3 / 5

Total

14

/

20

Passed

Description

78%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 specific, well-triggered description for a clearly distinct niche, with both what and when explicitly stated. It is held back from the top level by marketing fluff ('完美保留排版', '大幅提升长文分发效率') and thinner trigger-phrase coverage than the exemplar descriptions.

Suggestions

Remove the marketing claims ('完美保留排版', '大幅提升长文分发效率') and replace them with concrete capabilities, e.g., saving as draft rather than auto-publishing.

Broaden the 'when' clause with additional natural trigger phrases users might say, such as '发布长文章到 X/Twitter', 'X Articles 排版', or '.md 文件'.

DimensionReasoningScore

Specificity

Lists several concrete actions ('自动将 Markdown 转换为富文本', '持久化免密登录与封面上传', '一键完成发布') matching the several-specific-actions anchor, but marketing padding ('完美保留排版', '大幅提升长文分发效率') keeps it below the comprehensive 5.

4 / 5

Completeness

Both what (convert to rich text, persistent login, cover upload, publish) and an explicit when ('在需要将 Markdown 长文发布到 X (Twitter) Articles 编辑器时使用') are present, but the when covers only a single scenario without the multiple concrete trigger phrases of the 5 anchor; above the 3 anchor because the when clause is explicit rather than missing.

4 / 5

Trigger Term Quality

'Markdown 长文', '发布', 'X (Twitter) Articles 编辑器' are natural phrases a user would say, giving good keyword coverage, though common variations/synonyms (e.g., '长文章', '.md', 'post/publish to X') are missing — the 5 anchor requires synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche — publishing Markdown long-form to the X (Twitter) Articles editor — with distinctive platform-specific triggers, so minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

Total

15

/

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.