CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xiaoyue-companion

小跃虚拟伴侣 - 使用智谱 AI 提供温暖的对话陪伴和静态图片分享

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./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.

A highly actionable, well-sectioned skill whose body is carrying too much weight: full script implementations duplicated inline, a platform table, and cost notes inflate the token budget. Routing the code to the existing scripts/ files and trimming would lift both conciseness and progressive disclosure.

Suggestions

Replace the inlined 'Node.js 实现' and '完整脚本示例' sections with brief usage of the existing bundle files (scripts/xiaoyue-chat.js, scripts/xiaoyue-companion.sh), keeping only a one-line invocation example and the scene enum table in SKILL.md.

Move the platform channel-format table and cost notes into a references/ file (e.g. references/platforms.md) referenced one level deep, or trim them to the one or two channels actually used.

Resolve the dangling asset references: either ship the assets/ images referenced by tired-rest.jpg/celebration.jpg or note clearly that the user must supply them before use.

DimensionReasoningScore

Conciseness

The body inlines the complete Node.js implementation (~75 lines, duplicated from the existing scripts/xiaoyue-chat.js) and a full bash script (~50 lines, mirrored by scripts/xiaoyue-companion.sh), plus a platform table, cost notes, and tips — clearly padded sections that belong in bundle files. It rises above score 1 because it does not explain concepts Claude already knows; it is operational throughout, just noticeably bloated by duplicated code.

2 / 5

Actionability

Everything is copy-paste executable: exact commands ('node scripts/xiaoyue-chat.js "有点累了" "work-tired"'), a complete runnable Node.js script, a complete bash wrapper, env-var setup, install steps, a channel-format table per platform, and named scene enums with meanings. Not score 4 because there are no meaningful gaps — even error paths and file-existence checks are handled.

5 / 5

Workflow Clarity

The four-step workflow (receive message → generate via glm-4.7-flash → optionally send image → send via OpenClaw) is clearly sequenced, and the scripts embed checkpoints (ZHIPU_API_KEY check, image file-existence check, response-parse error handling). It falls short of score 5 because there are no explicit validate/retry feedback loops or a documented verification step that the message actually sent, only an error-handling list of failure modes.

4 / 5

Progressive Disclosure

Section structure is good and the one referenced bundle path (scripts/xiaoyue-chat.js) is real, but the entire contents of that script and of scripts/xiaoyue-companion.sh are inlined rather than referenced, and the referenced assets/*.jpg files do not exist in the bundle. This matches 'content that should be separate is inline' with decent structure — not score 2 (structure is thorough, not minimal) but not score 4 (bulk implementation code sits in SKILL.md instead of bundle files).

3 / 5

Total

14

/

20

Passed

Description

42%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 communicates a clear identity and a modest 'what', but omits any 'when to use' guidance and the natural trigger phrases that would route users to it. It reads as a product tagline rather than a routing description.

Suggestions

Add an explicit trigger clause with the natural user phrases already listed in the body, e.g. 'Use when the user says 有点累/好累, asks 在吗/你好, requests 发张照片, or needs encouragement or company while waiting on tasks.'

State the concrete actions instead of the abstract vibe: 'Generates warm 1-2 sentence replies via Zhipu GLM-4.7-flash and shares static scene images through OpenClaw' rather than 'provides warm conversational companionship'.

Sharpen distinctiveness by mentioning the OpenClaw message-sending integration, which distinguishes this skill from generic chat/companion skills.

DimensionReasoningScore

Specificity

The description names the domain ("小跃虚拟伴侣") and two actions ("提供温暖的对话陪伴和静态图片分享") plus the provider ("使用智谱 AI"), which matches the anchor for 1-2 concrete actions without comprehensive coverage. It stops short of score 4 because it never states the actual mechanisms (generating replies via the GLM API, sending messages via OpenClaw), and 'warm companionship' is more of a vibe than a concrete action.

3 / 5

Completeness

The 'what' is present and reasonably clear (warm conversational companionship and static image sharing via Zhipu AI), but there is no 'Use when...' clause or any equivalent trigger guidance, capping completeness at 3 per the judging guidelines. It is not score 2 because the 'what' is specific rather than vague, and not score 4 because 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Only generic domain keywords appear ('对话陪伴', '静态图片分享', '智谱 AI'); the natural phrases users actually say per the skill's own body ('有点累', '在吗', '发张照片') are absent. This is above score 1 (which requires pure jargon or entirely generic language) but clearly below score 3's 'relevant keywords' bar since the missing terms are the primary way this skill would ever be triggered.

2 / 5

Distinctiveness Conflict Risk

The named persona ('小跃') and Zhipu AI/static-image specifics carve out a niche, but '提供温暖的对话陪伴' ('provide warm conversational companionship') is broad enough to overlap with any general chat or companion skill. It fits 'somewhat specific but could still overlap with similar skills' rather than score 4, which requires minimal overlap risk with closely related skills.

3 / 5

Total

11

/

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

anbeime/skill

Path

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.