CtrlK
BlogDocsLog inGet started
Tessl Logo

consultation-scripts

海岚旅行接待话术(HL-CS-SCR-03 V3.1):问候与身份说明、需求确认、产品推荐、报价、拒绝折扣、投诉接待(一般与紧急)、转交、方案 PPT 交付、结束语。照意思说,不整段照抄。

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./experimental/simulation/scenarios/travel_agency/materials/consultation-scripts/SKILL.md
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 lean, highly actionable set of scenario scripts that reads like a conversation playbook: verbatim lines, concrete deadlines, escalation rules, and a customer-confirmation checkpoint, organized in natural consultation order. The only notable gap is the undefined '报价单格式' the quote section depends on.

DimensionReasoningScore

Conciseness

Every section is a compact script block with zero concept explanation, padding, or filler — the body assumes competence and every token (verbatim lines, rules like '不争辩、不解释、不承诺赔偿') earns its place, matching the lean-and-efficient anchor.

5 / 5

Actionability

Provides copy-adaptable verbatim scripts with concrete specifics (response deadlines of 2/24/48 hours, escalation targets, example quote number HL-Q-1202-3P) covering the common cases. Not 5 because '按报价单格式发出' references a quote-sheet format that is never defined anywhere in the skill — a minor executable gap.

4 / 5

Workflow Clarity

Sections are ordered along the actual consultation flow (greeting → needs confirmation → recommendation → quote → discount refusal → complaints → phone → handover → PPT → closing) with checkpoints like asking the customer to confirm ('我确认一下…对吗?') and explicit urgent-complaint detection criteria. Not 5 because there is no feedback guidance for off-script turns (e.g., what to do when the customer objects to a confirmation).

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (none exist in the bundle) and is cleanly organized into well-labeled per-scenario sections, which per the scoring notes earns a 5 for simple skills.

5 / 5

Total

18

/

20

Passed

Description

71%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 highly specific, comprehensive 'what' for a travel-reception script skill, but it omits any explicit 'when to use' trigger guidance, capping completeness. Distinctiveness is good thanks to the company-scoped niche and scenario-specific vocabulary.

Suggestions

Append an explicit trigger clause such as '当接待海岚旅行客户咨询、报价、砍价、投诉或转交时使用' (use when handling customer greeting, quoting, discount requests, complaints, or handovers) to raise completeness.

Add common trigger variations users would actually say (e.g., '客户要打折', '客人要投诉', '怎么回复砍价') to broaden natural keyword coverage.

State the capabilities as third-person actions (e.g., '提供…话术' / 'provides scripts for...') rather than a bare topic list, matching the good-overall examples' style.

DimensionReasoningScore

Specificity

Enumerates ten concrete, distinct capabilities ('问候与身份说明、需求确认、产品推荐、报价、拒绝折扣、投诉接待(一般与紧急)、转交、方案 PPT 交付、结束语') — comprehensive coverage of the domain's actions, matching the multiple-specific-actions/comprehensive anchor. Not 4 because coverage of the reception workflow is complete rather than having minor gaps.

5 / 5

Completeness

The 'what' is clear (reception scripts covering the listed scenarios, plus the directive '照意思说,不整段照抄'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains natural user-facing keywords like '报价' (quote), '折扣' (discount), '投诉' (complaint), 'PPT 交付' that users would plausibly say. Not 5 because it lacks synonyms/variations and is a topic list rather than phrased triggers; not 3 because keyword coverage is good, not merely partial.

4 / 5

Distinctiveness Conflict Risk

The company-specific niche (海岚旅行 reception scripts, document code HL-CS-SCR-03 V3.1) makes it largely distinct with scenario-specific terms. Not 5 because the keywords are generic travel-domain terms that could overlap with other hospitality/travel consultation skills.

4 / 5

Total

16

/

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
EverMind-AI/Raven
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.