CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cherry-skill-marketplace

用户要求搜索、安装、查看或卸载 Skill,或内置能力不足时使用:先 search_skills,再 install_skill;无结果用 skill-creator 创建。

Quality

84%

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

78%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 tight, well-structured instruction-only skill that provides concrete tool calls with parameter shapes, explicit consent/verification checkpoints, and sensible safety boundaries, all in one appropriately sized file. The main gaps are an unspecified navigate argument, absent install-failure recovery beyond honest reporting, and some repeated refrains that could be consolidated.

Suggestions

Specify the concrete argument shape for the mcp__assistant__navigate call (e.g., where the route value from product_info's routes section goes), so the uninstall-management path is fully executable.

Add a brief recovery step for a failed mcp__skills__install_skill call (retry once, or fall through to the skill-creator path) instead of only summarizing the error honestly.

Consolidate the repeated 'install/registration success is not task completion' refrain and the duplicate search-parameter detail into a single place to trim tokens without losing the behavioral rule.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what Skills or MCP tools are and jumps straight to tool names, parameters, and routing rules. Minor redundancy could be trimmed: the 'do not treat install/registration success as task completion' refrain repeats ~3 times, and the search tool's parameters are spelled out in two separate sections, keeping it at anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Concrete, executable guidance throughout: exact tool names with parameter shapes ('mcp__skills__search_skills' with '{ "query": "1-3 个聚焦关键词" }', the install_source opacity rule, product_info → routes → navigate). It falls short of anchor 5 because the 'mcp__assistant__navigate' call's actual argument is never specified, so that step is not fully copy-paste ready.

4 / 5

Workflow Clarity

The flow is clearly sequenced with conditional branches (entry gate → search → present ≤3 results → consent → install → return to task; capability-gap path; creator handoff) and explicit checkpoints: user consent before install, source-trust matching, post-install verification ('使用新 Skill 完成并验证最终产物'), and re-confirming before uninstall. It sits at anchor 4 rather than 5 because recovery from a failed install is limited to honest error reporting ('工具错误原样概括') with no retry or fallback loop specified.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed: the ~50-line body is self-contained, split into well-organized sections (进入条件, 工具动作, 搜索与安装, 内置能力不支持, 移交 Skill Creator, 失败与安全) that each fully cover their flow. Under the simple-skill scoring note, a short single-file skill with no need for external references and clean section organization scores 5.

5 / 5

Total

17

/

20

Passed

Description

83%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 concise, well-structured description that clearly states both the trigger conditions and the concrete tool orchestration, with good natural-language trigger terms. Its only weaknesses are a slightly broad 'insufficient built-in capability' trigger that overlaps with skill-creator, and a few missing synonyms such as 'marketplace'.

DimensionReasoningScore

Specificity

The description names several concrete actions ('搜索、安装、查看或卸载 Skill') with an explicit tool sequence ('先 search_skills,再 install_skill;无结果用 skill-creator 创建'). It lists multiple specific actions with minor gaps in coverage (e.g., managing installed skills via the UI is not mentioned), matching anchor 4 rather than the comprehensive coverage of anchor 5.

4 / 5

Completeness

It explicitly answers 'what' (orchestrate search_skills → install_skill, fall back to skill-creator creation) and 'when' ('用户要求搜索、安装、查看或卸载 Skill,或内置能力不足时') with concrete trigger phrases, matching the anchor-5 example structure. It is not anchor 4 because the 'when' is not merely implied or generic — it enumerates the specific user intents.

5 / 5

Trigger Term Quality

Natural trigger phrases like '搜索、安装、查看或卸载 Skill' are exactly what a user would say when needing this skill, and the capability-gap condition ('内置能力不足') adds a second trigger path. A few natural synonyms are missing (e.g., 市场/marketplace, '找 Skill'), placing it at anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The skill has a clear niche (marketplace skill sourcing/install) with distinct triggers, but the broad '内置能力不足时使用' condition and the explicit mention of the closely related 'skill-creator' create minor overlap risk with that sibling skill. This fits 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

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

Path

resources/builtin-agents/cherry-assistant/.claude/skills/cherry-skill-marketplace/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.