CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xhs-live

小红书公开直播文字评论与文字帧发送;房间、商品和事件监听使用 xhs-hunter live。

Quality

77%

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 ./crews/main/skills/expert-bd/tools/xhs-live/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

An exceptionally lean, high-signal skill body: concrete commands, hard boundaries on unsupported operations, and real safety checkpoints (preview-by-default, --confirm, verify-before-resend, account acceptance). The main gaps are cosmetic — full syntax for the secondary send methods and a resolvable pointer for the referenced Live Interaction workflow.

Suggestions

Show the full command syntax for room-text and send-captured-frame (or state that `xhs-live methods` prints them) so all send paths are copy-paste ready.

Link or inline the 'Live Interaction workflow' checklist (target/copy/authorization verification) since no bundle file currently backs that reference.

DimensionReasoningScore

Conciseness

The body is ~8 lines of dense, operational guidance — every sentence carries a rule Claude could not infer ("不混用 Creator Cookie", "不支持直播点赞,不用赠礼接口代替", "call 不允许查询方法"). No concept explanations or padding; matches 'lean and efficient; every token earns its place'.

5 / 5

Actionability

Concrete executable commands are given ("xhs-live send '真实room_id' '评论文本' --host-id '主播user_id'", "xhs-live methods") with the confirm flag and preview semantics specified. Not 5 because full syntax for room-text and send-captured-frame invocations is absent — they appear only as method names in "send、room-text、send-captured-frame room 和 call send_comment 默认预览", leaving minor gaps.

4 / 5

Workflow Clarity

The sequence is traceable with strong checkpoints for an outward-facing operation: verify per workflow first ("先按本包 Live Interaction workflow 核对目标、文案与既有授权"), default preview with "实际执行加 --confirm", and on failure "先核实,不自动重发" plus real-account acceptance. Not 5 because steps are prose-scattered and "本包 Live Interaction workflow" is referenced without any file or inline checklist, leaving a small gap in the pre-send verification path.

4 / 5

Progressive Disclosure

At under 50 lines with no bundle files, everything lives appropriately inline with a single command block — largely meeting the simple-skill standard. One notch below 5 because "本包 Live Interaction workflow" is a dangling pointer (no such file exists in the bundle and no link is given), a minor organization gap against 'well-organized sections'.

4 / 5

Total

17

/

20

Passed

Description

61%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 is concise, concrete, and cleanly delineated from the sibling xhs-hunter live skill, but it lacks any 'use when' trigger guidance, which limits discoverability. Trigger keyword coverage is good though missing common synonyms. Adding an explicit when-clause with natural trigger phrases would lift the two heaviest dimensions.

Suggestions

Append a when-clause with concrete triggers, e.g. "Use when 用户要在小红书直播间发评论、发弹幕或发送已捕获的文字帧时使用".

Add common synonyms such as 弹幕/互动 and English variants (XHS, RedNote live) to broaden natural trigger matching.

Enumerate additional capabilities of the skill itself (e.g. listing available send methods via `xhs-live methods`) to round out specificity.

DimensionReasoningScore

Specificity

"小红书公开直播文字评论与文字帧发送" names the domain plus exactly two concrete actions (text comment sending, text-frame sending); the delegated listening capabilities ("房间、商品和事件监听使用 xhs-hunter live") belong to another skill, so coverage is not comprehensive. Matches anchor 3 ('names domain and 1-2 concrete actions') rather than 4, which expects several actions of the skill itself listed.

3 / 5

Completeness

The 'what' is clear (send text comments and captured text frames to public XHS live rooms), but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3. It sits above anchor 2 (vague what / only when) because the what is concrete, but below anchor 4 which requires an explicit when.

3 / 5

Trigger Term Quality

Good natural keywords a user would say: "小红书", "直播", "评论", "文字帧", "房间", "商品", "事件监听" — closer to 'good keyword coverage; a few natural terms missing' than anchor 3's single-keyword example. Not 5 because common synonyms like "弹幕", "互动", or English variants (XHS/RedNote) are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche — sending in 小红书 public live rooms — and it explicitly delegates adjacent capabilities to "xhs-hunter live", reducing conflict. Not 5 because trigger terms like "小红书直播" overlap heavily with the closely related xhs-hunter skill family, so a user's phrasing could plausibly pull the sibling skill instead.

4 / 5

Total

14

/

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

TeamWiseFlow/xiaobei

Path

crews/main/skills/expert-bd/tools/xhs-live/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.