CtrlK
BlogDocsLog inGet started
Tessl Logo

cherry-assistant-guide

从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本,或报告运行错误、连接失败、配置异常并需要诊断时触发。

74

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An excellent instruction-only skill body: every tool call is concrete with exact parameters, the decision workflow is unambiguous with explicit failure handling, and there is no token waste on concepts Claude already knows. The only minor gap is a slightly dangling build-script reference and a body a touch over the compact-skill line count.

Suggestions

Trim or clarify the generated-file header comment: the referenced scripts/generate-cherry-assistant-knowledge and pnpm build target do not exist in this bundle, so either drop the comment or note it applies only to the source repo.

Consider moving the five "回答时遵守以下规则" interpretations into a short reference file if the skill grows, keeping SKILL.md under the ~50-line compact threshold.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains what MCP or a manifest is, and every sentence adds a constraint or instruction Claude could not infer (e.g., "routes.all 还可能包含内部页、参数路由或兼容跳转,不能无条件推荐"). No padded or tutorial-style sections exist, matching the lean-and-efficient anchor.

5 / 5

Actionability

Fully executable guidance: exact tool calls with parameters are given for each question type (e.g., mcp__assistant__product_info({ source: "manifest", section: "routes" })), plus a concrete index-first fallback and a numbered rule list for interpreting results. This is copy-paste-ready for an instruction-only skill.

5 / 5

Workflow Clarity

The decision procedure is clearly sequenced with explicit checkpoints: question→section mapping, index call when the section is unknown, navigate in the same turn before manual steps, and failure handling ("工具未调用或失败时,不得声称已经生成入口"; fallback to official docs when the manifest lacks the capability). The only deliberate restriction on section: "all" prevents context blowup, showing error-avoidance rather than missing validation.

5 / 5

Progressive Disclosure

Well-organized single-level sections with no nested references, and content is appropriately inlined for a compact instruction skill. It falls just short of the top anchor because the body slightly exceeds the ~50-line simple-skill threshold and the header comment cites a generator script (scripts/generate-cherry-assistant-knowledge) that is not present in the bundle, leaving a dangling reference.

4 / 5

Total

19

/

20

Passed

Description

90%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 strong description: it clearly states what the skill does and gives an explicit, comprehensive trigger clause covering both feature questions and error-report phrasings in users' natural vocabulary. The only soft spot is that the "what" portion names just two actions rather than enumerating several specific capabilities.

Suggestions

Enumerate the concrete query capabilities in the first sentence (e.g., look up routes/pages, shortcuts, providers, languages, and agents from the installed manifest) to raise specificity from two named actions to several.

Mention the actual data source name (the packaged product manifest / product-manifest.json) in the description so the "what" is even more concrete.

DimensionReasoningScore

Specificity

The description names the domain (Cherry Studio product info from the installed package) and two concrete actions — "查询 Cherry Studio 产品信息" and "排查运行问题" — which matches the anchor for domain plus 1-2 concrete actions. It does not enumerate several specific actions (anchor 4), and it is well above the vague/generic-only anchors.

3 / 5

Completeness

It explicitly answers both "what" (query Cherry Studio product info from the currently installed package and troubleshoot runtime problems) and "when" via the explicit trigger clause "当用户询问...或报告...并需要诊断时触发". Both are concrete and clearly stated, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms users would actually say: "功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本" plus problem phrasings "运行错误、连接失败、配置异常". Coverage includes synonyms and both feature queries and error reports, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — querying Cherry Studio's installed-package manifest and diagnosing its runtime issues — with trigger terms (routes, providers, Code CLI, scheduled tasks) that would not fire for unrelated skills, so conflict risk is minimal.

5 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.