CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

post-to-xhs

小红书内容发布技能。支持两种发布模式:(1) 上传图文模式 - 图片+短文;(2) 写长文模式 - 长篇文章+排版模板。 支持两种输入方式:用户提供完整内容和图片/图片URL,直接发布;或提供网页URL,自动提取内容和图片。 用户说"发长文"时使用长文模式,否则默认图文模式。

Quality

78%

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/post-to-xhs/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A strong operational skill document: dense with executable commands, explicit exit-code contracts, user-confirmation checkpoints, and a real one-level-deep reference file. Weaknesses are localized — hardcoded user-specific Windows paths, no explicit post-publish success verification, some duplicated rules, and account-management content that belongs in a reference file.

Suggestions

Replace the hardcoded 'C:\Users\admin\AI\.claude\skills\post-to-xhs\scripts\...' paths with paths relative to the skill root (e.g., 'scripts/publish_pipeline.py') so the commands are copy-paste executable on any installation.

Add an explicit post-publish verification step in 4.7 — define the exact output/exit code that confirms the post went live (e.g., a PUBLISH_SUCCESS marker or post-URL check) instead of the vague '根据命令输出告知用户'.

Move the 账号管理 section into a reference file (e.g., references/account-management.md) linked from the body, and deduplicate the 无头/有窗口 mode and 1000字压缩 rules that currently appear in 2–3 places.

DimensionReasoningScore

Conciseness

The body is command-driven with almost no explanation of concepts Claude already knows — every section is either a concrete rule, a script invocation, or an exit-code contract. There is minor duplication ('长文模式...超过 1000 字需压缩到 800 字左右' appears in both Step B.4 and 重要提示, and the 无头/有窗口 mode descriptions are repeated in 4.2, 4.4, and 重要提示) that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor rather than the perfectly lean level 5.

4 / 5

Actionability

Nearly every step is an executable command with concrete flags, argument examples ('--title-file title.txt --content-file content.txt --image-urls "URL1" "URL2"'), and a defined exit-code contract (NOT_LOGGED_IN=1, READY_TO_PUBLISH=0, 2=error). The gap keeping it below 'fully copy-paste ready' is that all commands hardcode a machine-specific absolute path 'C:\Users\admin\AI\.claude\skills\post-to-xhs\scripts\...' instead of paths relative to the skill root, so they will not resolve on any other installation.

4 / 5

Workflow Clarity

The sequence is explicit (Step 1–4 with per-mode branching, B.1–B.5 for long-form), with real validation checkpoints: mandatory user confirmation via AskUserQuestion at 4.1, mode selection at 4.2, preview confirmation at 4.5, '绝不自动发布', and a feedback loop for NOT_LOGGED_IN (auto-switch to windowed mode and re-run). It falls short of level 5 because there is no post-publish verification step — 4.7 only says to report success '根据命令输出' without defining what output confirms a successful publish, and the mode-conditional skipping around 4.5/B.5 is slightly tangled.

4 / 5

Progressive Disclosure

Structure is good: the body stays an operational overview, the one external reference [references/publish-workflow.md](references/publish-workflow.md) is real, clearly signaled at Step 4, and one level deep (it references only scripts/*.py, no nested .md files). Minor gaps keep it below 5: the 账号管理 section (~35 lines of account CRUD commands) is inlined content that could live in its own reference, and the body at ~240 lines is heavier than a pure overview.

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.

A specific, well-scoped description for a niche automation task with concrete mode/input descriptions and natural trigger vocabulary. Its main weakness is the absence of an explicit 'use when' clause telling Claude when to invoke the skill, which caps completeness; the existing trigger-like sentence only disambiguates between the skill's two internal modes.

Suggestions

Add an explicit trigger clause, e.g. '当用户想要发布小红书笔记/内容时使用本技能' (Use this skill when the user wants to publish content or notes to Xiaohongshu), to lift completeness above 3.

Include natural user synonyms such as '小红书笔记', '发帖', '上传图片' alongside the existing '发长文'/'图文' terms for broader trigger coverage.

Mention supported inputs users would name when asking (e.g., '笔记链接', '网页链接转小红书') so the URL-extraction capability is triggerable by user phrasing.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities: '上传图文模式 - 图片+短文', '写长文模式 - 长篇文章+排版模板', and '提供网页URL,自动提取内容和图片'. It names the domain and multiple specific actions, but coverage is not fully comprehensive (e.g., multi-account support described in the body is absent), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive level 5 or the thinner level 3.

4 / 5

Completeness

The 'what' is clear (two publishing modes, two input methods, URL extraction), but there is no 'Use when...' or equivalent trigger clause for invoking the skill: '用户说"发长文"时使用长文模式,否则默认图文模式' selects a mode within the skill, not when to use the skill itself. Per the guideline that a missing explicit trigger clause caps completeness at 3, and the anchor 'clear what but when missing or only weakly implied' is the best fit.

3 / 5

Trigger Term Quality

Natural terms a user would say are present: '小红书', '发布', '发长文', '图文', '图片URL'. However common variations users actually use are missing — e.g., '笔记', '发帖', '上传图片到小红书' — so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym/extension coverage of level 5.

4 / 5

Distinctiveness Conflict Risk

'小红书内容发布' carves out a clear niche (publishing to Xiaohongshu's creator platform) with distinct triggers like '发长文' and '图文发布' that no other generic skill would claim, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor. Level 4's 'minor overlap risk' does not apply since no related skill territory is implicated.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

xpzouying/xiaohongshu-mcp

Path

skills/post-to-xhs/SKILL.md

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.