CtrlK
BlogDocsLog inGet started
Tessl Logo

cherry-skill-marketplace

当用户明确要求搜索、安装、查看、卸载或创建 Skill,或内置 Skill / 工具出现能力缺口、无法完成当前任务时触发。通过 `mcp__skills__search_skills` 搜索并用 `mcp__skills__install_skill` 安装;已安装 Skill 的查看和删除通过产品清单导航到 Skills UI;没有合适结果时调用内置 `skill-creator` 创建并验证自定义 Skill,再继续原任务。普通任务仍先尝试内置能力。

71

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 well-structured, highly actionable skill body with concrete tool calls, parameter shapes, and validation checkpoints around destructive operations. The main improvement would be de-duplicating the search procedure across sections and adding an explicit error-retry loop.

Suggestions

De-duplicate the search procedure: define it once in 搜索与安装 and have 工具动作 and 内置能力不支持 reference that section instead of restating the query/install details.

Add an explicit error-recovery feedback loop in 失败与安全 (e.g., on a failed install, report the error as-is and either retry with an adjusted query or fall back to skill-creator) to push workflow_clarity toward 5.

Consider folding the repeated '不要把…当成任务完成' reminders into a single checkpoint convention to trim a few tokens.

DimensionReasoningScore

Conciseness

Lean, directive prose that assumes Claude's competence and avoids explaining known concepts, but the search procedure is restated across 工具动作, 搜索与安装, and 内置能力不支持, leaving minor redundancy that could be tightened.

4 / 5

Actionability

Fully actionable instruction-only guidance: exact tool names, concrete parameter shapes ({ "query": "…" }, { "install_source": "<搜索结果的原值>" }), and specific limits (最多展示 3 个结果, 逐字使用 install_source) cover the common cases.

5 / 5

Workflow Clarity

Clear numbered sequence with explicit checkpoints (user consent before install, re-confirm name before uninstall, verify final product after skill-creator returns); the destructive-op validation is present so the cap-3 does not apply, but no explicit error-retry feedback loop is defined.

4 / 5

Progressive Disclosure

No bundle files exist; the ~58-line body is self-contained and organized into well-signaled sections (进入条件, 工具动作, 搜索与安装, etc.) with no nested references, fitting the simple-skill exception for well-organized single-file skills.

5 / 5

Total

18

/

20

Passed

Description

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

A specific, third-person description that clearly states both what it does and when to trigger it, with concrete tool names and a complete fallback flow. Minor room to improve trigger synonym coverage and tighten the broad capability-gap trigger.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (search, install, view, uninstall, create) each bound to named tools (mcp__skills__search_skills, mcp__skills__install_skill, skill-creator, Skills UI navigation), giving comprehensive coverage of the skill-management domain.

5 / 5

Completeness

Explicitly answers both 'when' (当用户明确要求…或…能力缺口…时触发) and 'what' (named tools and the search→install→creator fallback flow) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user-facing verbs (搜索、安装、查看、卸载、创建) plus the capability-gap scenario give good coverage, but a few common synonyms (找、下载) and informal phrasings are missing, short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The skill-marketplace niche is clear and mostly distinct, but the secondary '能力缺口/无法完成当前任务' trigger is broad enough to create minor overlap risk with other fallback-oriented skills.

4 / 5

Total

18

/

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
CherryHQ/cherry-studio
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.