CtrlK
BlogDocsLog inGet started
Tessl Logo

openclw

当用户输入以 "fy " 开头的翻译请求时使用此 skill。支持中英互译,如果是其他语种则翻译成中文。触发条件:输入 "fy" 后面跟要翻译的内容,例如 "fy test" 返回 "测试"。

66

Quality

80%

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 ./configs/microservice/bff-service/configs/agent-skills/clawhub/fy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 short, well-sectioned, and actionable, with input→output examples that cover every rule branch and an unambiguous single-task workflow. Its main flaw is redundancy — 功能说明 and 翻译规则 duplicate each other and restate things Claude already knows — which costs token efficiency.

Suggestions

Merge 功能说明 and 翻译规则 into a single rule list; they currently state the same Chinese↔English / other→Chinese logic twice.

Drop trivially known steps such as '检测输入文本的语言' and '返回翻译结果' — Claude already does these without instruction.

Clarify the expected output format (e.g., 'reply with only the translation, no explanation') to close the actionability gap.

DimensionReasoningScore

Conciseness

The 功能说明 and 翻译规则 sections restate the same language rules twice, and steps like "检测输入文本的语言" explain what Claude already knows, so the body could be meaningfully tightened; it is not 4 because the duplication is more than minor trimming, and not 2 because the body is short and mostly on-point.

3 / 5

Actionability

Four concrete input→output examples ("fy test" → 测试, "fy 你好" → hello, "fy こんにちは" → 你好, "fy Bonjour" → 你好) cover all three rule branches, giving mostly executable guidance; it falls short of 5 due to minor gaps such as no statement of output format (translation only vs. explanation) or handling of mixed-language input.

4 / 5

Workflow Clarity

This is a simple single-task skill under 50 lines whose 翻译规则 decision tree (Chinese→English, English→Chinese, other→Chinese) is complete and unambiguous over all inputs; the simple-skill exception applies, and no destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (none exist in the bundle), and is organized into clear sections (触发条件, 功能说明, 使用示例, 翻译规则), satisfying the simple-skill criterion for a top score.

5 / 5

Total

17

/

20

Passed

Description

82%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 well-constructed: it states a precise, distinctive trigger (the "fy " prefix with a worked example) and clearly defines the translation behavior for Chinese, English, and other languages. Its only weakness is limited breadth of stated capabilities, which keeps specificity at the mid tier.

DimensionReasoningScore

Specificity

The description names the translation domain and two concrete capabilities ("支持中英互译", "如果是其他语种则翻译成中文"), matching the 'names domain and 1-2 concrete actions' anchor; it does not rise to 4 because no further specific actions or coverage details are given.

3 / 5

Completeness

It explicitly answers both 'what' (中英互译, other languages to Chinese) and 'when' ("当用户输入以 'fy ' 开头的翻译请求时使用此 skill") with a concrete trigger phrase and example, matching the top anchor rather than 4 where the 'when' is merely present but less specific.

5 / 5

Trigger Term Quality

It includes the explicit "fy" trigger keyword, the natural term "翻译请求", and a concrete usage example ("fy test" 返回 "测试"), giving good keyword coverage; it falls short of 5 because no synonyms, variations, or related natural phrases are listed.

4 / 5

Distinctiveness Conflict Risk

The exact "fy " prefix trigger defines a clear niche with minimal conflict risk against other skills, since activation requires a precise input pattern; it is not 4 because the trigger is more distinctive than 'minor overlap risk' with closely related 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
UnicomAI/wanwu
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.