CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xiaohongshu-reader

Read 小红书 / RedNote posts and image notes from xhslink.com or xiaohongshu.com using available web or browser tools. Distinguish captions from image content.

62

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 ./.codex/skills/xiaohongshu-reader/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 tight, directive, safety-conscious reading workflow: every line tells Claude what to verify, what to refuse, and what to output, with clear fallbacks for restricted pages and unreadable images. The main improvements are cosmetic — section headers, a sample link/output example, and trimming the version-history footnote.

Suggestions

Add lightweight section headers (e.g., ## 读取流程 / ## 输出 / ## 边界) so the existing partitions are explicit and skimmable.

Include one concrete example of a share link (e.g., xhslink.com/xxxx format) and a minimal output template to anchor the output contract.

Trim or reframe the closing "本公开版..." paragraph as a short deprecation note so it stops consuming tokens in the main flow.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — e.g. "核对帖子身份、作者、日期、标题和正文" and "无法查看图片则明确正文未读全,不用标签编造摘要" — with no explanation of concepts Claude already knows. It falls short of anchor 5 only because the closing changelog-style note ("本公开版...不包含旧 SSR 下载脚本、固定 Node 路径或共享临时目录") is versioning commentary that could be trimmed or moved to a deprecation note.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete and directive: verification targets (identity, author, date, title, body), "短链接需读到最终帖子,不能据跳转页推断内容", explicit fallbacks ("请求用户提供正文/截图"), and a defined output contract ("输出来源、读取范围、核心内容、图片证据与未核验项"). It stops short of anchor 5 because there are no concrete examples (e.g., a sample share-link format or an output template) covering the common cases.

4 / 5

Workflow Clarity

The bullets follow a coherent input-to-output progression (enter via link → verify post → read images in order → interpret and source-check → respect scope → handle restricted pages → structured output) with real checkpoints: "短链接需读到最终帖子", "无法查看图片则明确正文未读全", and reporting "未核验项". It is not anchor 5 because the sequence is implicit in bullet order rather than explicitly ordered, and there is no re-check loop after a failed read attempt. The skill is read-only, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ are absent, consistent with the body's statement that this version ships no scripts), so no external references are needed. Structure is good — entry/security context, reading rules as bullets, output contract, scope note — but there are no section headers to signal these partitions, leaving it just short of the 'well-organized sections' bar for anchor 5.

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, distinctive description that names concrete actions, both platform names, and both source domains. Its main gap is the absence of an explicit 'Use when...' trigger clause, which caps completeness, and a few missing natural synonyms.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user shares a 小红书/RedNote link (xhslink.com or xiaohongshu.com) or asks to read or summarize a 小红书 note."

Broaden trigger coverage with common synonyms such as "笔记" (note), "XHS", and "RedNote link" so users' natural phrasings match.

Optionally state the output promise (e.g. "...and report sources, image evidence, and unverified items") to round out the 'what'.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "Read 小红书 / RedNote posts and image notes", "Distinguish captions from image content" — and grounds them in specific sources ("from xhslink.com or xiaohongshu.com") and tool modality ("using available web or browser tools"). It falls short of anchor 5 because coverage is not comprehensive (no mention of summarizing, sourcing, or output handling), but exceeds anchor 3's '1-2 concrete actions' bar.

4 / 5

Completeness

The 'what' is clear ("Read 小红书 / RedNote posts and image notes ... Distinguish captions from image content"), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the domain names only weakly imply when to invoke it. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3, which also matches the anchor 'clear what, when missing or only weakly implied'.

3 / 5

Trigger Term Quality

Includes the natural terms a user would say when sharing a link — "小红书", "RedNote", "xhslink.com", "xiaohongshu.com", "posts", "image notes", "captions". A few common variations are missing (e.g., "笔记", "XHS", "note link"), so it does not reach anchor 5's comprehensive synonym coverage, but it is well above anchor 3's partial keyword set.

4 / 5

Distinctiveness Conflict Risk

The platform names and domains ("小红书 / RedNote", "xhslink.com or xiaohongshu.com") carve out a clear niche with distinct triggers and minimal conflict risk against generic web-reading or other platform skills. It matches anchor 5; it is more targeted than anchor 4's 'minor overlap risk' example.

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

huangruiteng/CS-Notes

Path

.codex/skills/xiaohongshu-reader/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.