CtrlK
BlogDocsLog inGet started
Tessl Logo

ask-echo

使用火山引擎 Ask-Echo 融合信息搜索 API 进行 web 搜索、web 搜索总结版和图片搜索。

60

Quality

70%

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/ask-echo/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.

The body is concise, actionable, and well-structured for a simple single-purpose skill, with executable examples and a real bundled script. Adding light error/auth-failure guidance and cleaning up the API-doc reference path would push it to full marks.

Suggestions

Add a short note on handling common failure modes (missing API key/auth error, rate limits, empty results) so the workflow has an explicit feedback checkpoint.

Replace the bare absolute path '/root/api-docs/ask-echo.md' with a clearly signaled, portable reference (e.g., a bundled references/ file) or mark it explicitly as an optional deep-dive.

Trim the slight overlap between the '适用场景' section and the frontmatter description to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with minimal padding, though the '适用场景' section lightly restates the frontmatter description, leaving minor trim potential short of the level-5 anchor.

4 / 5

Actionability

It provides copy-paste-ready executable commands (`python scripts/ask_echo.py "..." --type ...`) backed by a real bundled script, with examples covering the web, web_summary, and image cases.

5 / 5

Workflow Clarity

The three-step sequence is clear and unambiguous for a simple single-action skill, but it lacks any guidance on handling API/auth errors, leaving a minor validation gap below the level-5 anchor.

4 / 5

Progressive Disclosure

Content is organized into clear sections appropriate for a sub-50-line simple skill, but the API doc reference is a bare absolute path (/root/api-docs/ask-echo.md) rather than a well-signaled one-level reference, slightly below the level-5 anchor.

4 / 5

Total

17

/

20

Passed

Description

58%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 specific and names concrete capabilities but omits any 'Use when...' trigger guidance, which caps its completeness. Adding an explicit trigger clause and common search synonyms would materially raise the score.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user needs web/image search via Volcengine Ask-Echo').

Broaden trigger terms with natural synonyms such as '搜索', 'search', '图片/image search', and '网页搜索' to improve trigger term coverage.

Clarify the distinctiveness from generic web-search skills by emphasizing the Ask-Echo fusion/summary capabilities in the description.

DimensionReasoningScore

Specificity

Names the Ask-Echo API domain and lists three concrete actions (web 搜索, web 搜索总结版, 图片搜索), though all are search variants rather than comprehensively distinct capabilities, so it falls just short of the level-5 anchor.

4 / 5

Completeness

It clearly states what the skill does but provides no 'Use when...' trigger clause, and the rubric explicitly caps completeness at 3 when such trigger guidance is missing.

3 / 5

Trigger Term Quality

Includes natural terms like 'web 搜索' and '图片搜索' that users would say, but misses common synonyms/variations and leans on the technical API name, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Ask-Echo vendor API gives it a clear niche with mostly distinct triggers, though generic 'web search'/'image search' phrasing creates minor overlap risk with other search skills.

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.

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