CtrlK
BlogDocsLog inGet started
Tessl Logo

search-web

使用内置 search_web.py 脚本进行联网搜索问答,准备清晰具体的问题。

59

Quality

68%

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 ./.trae/openclaw-skills/search-web/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.

A concise, well-structured, mostly actionable skill doc: the command and example are executable and the output contract is clearly specified. The main weaknesses are undocumented prerequisites (SEARCH_BOT_ID/API key env vars), vague setup instructions ('cd到对应的目录'), and advanced features (model=thinking, console toggles) with no explanation of how to actually enable them.

Suggestions

Document required environment variables up front (e.g., '运行前需设置 SEARCH_BOT_ID 和 MODEL_SEARCH_API_KEY/ARK_API_KEY'), since the script exits without them — the most common failure is currently undiscoverable.

Make setup concrete: state the exact directory (skill root) instead of 'cd到对应的目录', and show how model=thinking is actually set (command flag, env var, or payload field) in the 示例.

Add a brief error-recovery note (e.g., 'SEARCH_BOT_ID 未设置时会提示;请在控制台获取后重试') so the error path has a fix-and-retry loop instead of just 'prints error info'.

DimensionReasoningScore

Conciseness

The body is ~40 lean lines of pure operational content (sections: 适用场景, 使用步骤, 输出格式, 示例, 高级功能) with zero padding and no explanation of concepts Claude already knows, matching 'every token earns its place'. It is not merely a 4 because there is no over-explanation anywhere to trim.

5 / 5

Actionability

The core command `python scripts/search_web.py "<question>"` plus a runnable example is concrete, matching 'concrete code or commands with minor gaps'. The gaps: the script requires `SEARCH_BOT_ID`/API-key env vars (verified in scripts/search_web.py) that are never documented, '运行之前cd到对应的目录' is vague about which directory, and '通过设置 model=thinking 开启' gives no actual mechanism. These are gaps, not absence of guidance, so not a 3.

4 / 5

Workflow Clarity

The 3-step sequence (prepare question → run script → read answer incl. error output) is clear and unambiguous for a simple skill, matching 'clear sequence with most checkpoints present; minor validation gaps'. Not a 5 because error handling stops at '若调用失败,将打印错误信息' with no fix-and-retry guidance (e.g., missing SEARCH_BOT_ID is the most likely failure but unmentioned).

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections and a real, existing referenced script (scripts/search_web.py verified), so structure is good — matching 'good structure; most content appropriately placed; minor organization gaps'. Not a 5 because advanced options (thinking mode mechanism, console toggles, stream flag) have no documented path — neither in SKILL.md nor via a reference — leaving those features undiscoverable.

4 / 5

Total

17

/

20

Passed

Description

53%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 states a concrete 'what' (web-search Q&A via the built-in search_web.py script) but omits any 'when to use' trigger guidance and most of the capability list, making it terse rather than complete. Keywords are natural but lack synonyms and common user phrasings.

Suggestions

Add an explicit trigger clause, e.g. '当用户需要联网搜索、查询最新信息或获取带引用来源的回答时使用' (Use when the user needs live web search, up-to-date info, or cited answers).

List 1-2 more concrete capabilities from the body (returns reference sources, follow-up suggestions, mixed-media cards) so the 'what' is comprehensive, not just one action.

Include natural synonyms users would actually say ('搜一下', '查资料', '最新动态', 'search the web') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("联网搜索问答" — web-search Q&A) and one concrete action ("使用内置 search_web.py 脚本"), matching the anchor 'names domain and 1-2 concrete actions, but not comprehensive'. It does not list the fuller capability set shown in the body (references, follow-up suggestions, mixed-media output), so it is not a 4.

3 / 5

Completeness

The 'what' is present and reasonably clear (web-search Q&A via the built-in search_web.py script), but there is no 'when' / 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is above a 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

It includes the natural phrase "联网搜索" (web search) and "问答" (Q&A), but misses common variations users would say ("搜索一下", "查一下最新...", "search the web", "online lookup"). This matches 'some relevant keywords but missing common variations or synonyms'; it is above a 2 because the terms present are natural, not jargon.

3 / 5

Distinctiveness Conflict Risk

Naming the specific built-in script ("内置 search_web.py 脚本") and the web-search Q&A niche makes it mostly distinct, with only minor overlap risk against other search/retrieval skills. It is not a 5 because no trigger phrases further separate it from generic 'search' skills.

4 / 5

Total

13

/

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