CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

guide-interaction

场景引导交互模式:当用户在询问某项功能的使用/配置流程时, 先判断该直接解释还是进入交互引导;当系统已注入 Guide Matched / Guide Pending / Guide Selection / Guide Active / Guide Completed 时, 按状态驱动回复并使用对应 guide MCP 工具。 Use when: 系统注入了 Guide Matched / Guide Pending / Guide Selection / Guide Active / Guide Completed,或用户明确在问某项功能怎么操作。 Not for: 普通闲聊、代码实现、没有流程诉求的概念讨论。

Quality

82%

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

75%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 a well-organized, tool-grounded instruction skill: a quick-reference table ties each MCP tool to its trigger condition, and each guide state has a terse, unambiguous workflow with explicit do/don't guidance. Weaknesses are modest — some repeated admonitions, no full example tool calls, and no error/edge-case checkpoints in the workflows.

Suggestions

Consolidate the repeated 'don't re-match / don't fabricate a guide' guidance into a single 核心边界 item and reference it from the state workflows to trim redundant tokens.

Add one complete example call for cat_cafe_create_rich_block and cat_cafe_update_guide_state (full argument shapes) so the two most central tools are copy-paste executable.

Add a checkpoint in workflow 1 for the empty/error result of cat_cafe_get_available_guides (what to say and whether any state should be persisted), and note how to confirm the rich block was created before calling update_guide_state.

DimensionReasoningScore

Conciseness

The body is lean — a tool quick-reference table, terse per-state bullets, no padding and no explanation of concepts Claude already knows. Minor repetition keeps it from a 5: the instruction not to re-match or fabricate guides appears in the 核心边界 ("不要因为看到了关键词就擅自造一个引导"), workflow 1 step 5 ("没有合适候选时,直接回答,不要伪造 guide"), and Guide Selection ("不要重新用关键词匹配一次 guide").

4 / 5

Actionability

Concrete and executable for an instruction-only skill: five named MCP tools in a lookup table mapped to when-to-use, exact state-injection formats, and concrete call details like "cat_cafe_update_guide_state(..., status='offered')" and "cat_cafe_guide_control(action='exit')". Not a 5 because no complete example call (full argument list for cat_cafe_create_rich_block or cat_cafe_update_guide_state) is shown, leaving minor execution gaps; not a 3 because the guidance is specific and directly executable, not pseudocode.

4 / 5

Workflow Clarity

All six states get a clearly sequenced workflow, including an explicit decision tree for the no-state case ("先判断:用户是要一个简短解释,还是要一步一步带着做") and explicit ordering constraints ("在 rich block 之后调用 cat_cafe_update_guide_state"). Not a 5 because there are no verification/checkpoint steps (e.g., how to confirm the rich block was created before persisting state, or what to do if cat_cafe_get_available_guides returns an error/empty set beyond '直接回答'); not a 3 because the sequences themselves are complete and unambiguous with explicit do/don't guardrails per state.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and none are needed: every section (role, boundaries, injection formats, tool table, six state workflows) is core runtime guidance that belongs in SKILL.md, organized under clear headers. Not a 5 because at ~84 body lines it exceeds the under-50-line simple-skill case where organization alone earns top marks, and the six per-state workflows could plausibly live in a reference file; not a 3 because nothing that belongs elsewhere is inlined and navigation is easy.

4 / 5

Total

16

/

20

Passed

Description

82%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 well-constructed: it states capabilities in neutral third-person voice, provides an explicit 'Use when' clause with concrete system-injection and user-intent triggers, and adds a 'Not for' clause that sharply bounds the skill. Main weakness is specificity — the concrete MCP tool actions are referenced only in aggregate rather than enumerated.

Suggestions

Enumerate one or two of the key MCP tool actions (e.g., 查询可用 guide 目录、发送交互选择卡片) in the description itself instead of the generic '使用对应 guide MCP 工具'.

Add a few natural trigger variations such as '如何使用' / '怎么设置' to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ("场景引导交互模式") and a few concrete actions ("先判断该直接解释还是进入交互引导", "按状态驱动回复并使用对应 guide MCP 工具") but coverage is not comprehensive — the individual guide MCP tools and state-specific behaviors are only implied, not listed. Not a 4 because the actions described are fewer and more general than 'several specific actions'; not a 2 because it does go beyond naming the domain.

3 / 5

Completeness

Explicitly answers 'what' ("按状态驱动回复并使用对应 guide MCP 工具" when states are injected; judge direct explanation vs interactive guidance) and 'when' with concrete trigger conditions ("Use when: 系统注入了 ... 或用户明确在问某项功能怎么操作") plus a 'Not for' exclusion clause. Not a 4 because the when-clause is already explicit and concrete, matching the anchor-5 example structure of capability statement + explicit triggers.

5 / 5

Trigger Term Quality

Includes natural user-facing phrases users would actually say — "怎么配置", "怎么操作", "用户明确在问某项功能怎么操作" — plus explicit system-injection triggers (Guide Matched/Pending/Selection/Active/Completed). Not a 5 because common synonyms/variations (e.g., "如何使用", "怎么设置", "不会用") are missing; not a 3 because the natural phrasing present is genuinely what users say, not jargon.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche keyed to distinctive trigger tokens (the five named Guide states) and explicitly excludes adjacent domains ("Not for: 普通闲聊、代码实现、没有流程诉求的概念讨论"), minimizing overlap with general Q&A or coding skills. Not a 4 because the 'Not for' clause plus unique state markers leave only minimal, not 'minor', overlap risk.

5 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

zts212653/clowder-ai

Path

cat-cafe-skills/guide-interaction/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.