CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

premium-package

海岚旅行定制游产品说明(HL-P-03):基础5晚,适用对象、包含与不含、规划通话流程、常见目的地(含高原标记)、每日安排框架、人数上限。

66

Quality

83%

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

82%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: terse tables carry all product facts and the planning-call workflow is concrete with explicit prohibitions. The main gaps are unresolved external references (the SOP 选择矩阵 and the 转交单 submission mechanics), which keep actionability and workflow clarity just below top marks.

Suggestions

Bundle or link the SOP 选择矩阵 (or inline its first two criteria) so '按 SOP 选择矩阵第1、2条' is resolvable — this is the single biggest actionability gap.

Specify the 转交单 submission step (form location/system and required fields) so the planning-call workflow is fully executable.

Add a fallback checkpoint for the planning call, e.g., what to do if the 资深顾问 cannot reach the customer within 2 个工作日, to round out workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean and table-driven — '基础晚数 | 5晚,可加晚,不可减晚', '不含: 加晚、加向导日、旅游意外险、个人消费' — with no padding and nothing explained that Claude would already know. Every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Mostly concrete, actionable guidance: exact inclusions ('两天私人向导', '一项特别体验...三选一'), a specific planning-call procedure ('采集联系电话,提交规划通话转交单,不提交占位申请', '不得先行承诺'), and a day-by-day table. It falls short of 5 because '按 SOP 选择矩阵第1、2条' references a matrix that is not bundled or linked, and the 转交单 submission mechanics (where/how) are unspecified.

4 / 5

Workflow Clarity

The 规划通话 section gives a clear sequence — 报起价 → 客人接受 → 采集联系电话 → 提交转交单(不提交占位申请)→ 资深顾问2个工作日内致电 → 通话后办理合同 — with an explicit boundary rule ('在线顾问不得先行承诺'). Not 5 because there are no checkpoints for edge cases (e.g., what to do if the customer cannot be reached) and the 转交单 step lacks detail; not a destructive/batch operation so no cap applies.

4 / 5

Progressive Disclosure

A single ~50-line file with well-organized sections (包含, 不含, 规划通话, 常见目的地, 每日安排框架) and no nested or buried references, which fits the simple-skill pattern. Docked one point because 'SOP 选择矩阵' is referenced but not present in any bundled file, leaving a dangling pointer.

4 / 5

Total

17

/

20

Passed

Description

75%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, distinctive description that comprehensively enumerates the skill's content with concrete facts, but it entirely lacks a 'when to use' trigger clause, which caps its usefulness for invocation. Adding an explicit use-condition would resolve the main weakness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a customer asks about 海岚旅行定制游, product HL-P-03, premium customized tour pricing, or planning-call handling' — this lifts completeness from 3 to 5.

Include a few more natural synonyms users would say, such as '报价/起价', '私人向导', or '5晚行程', to improve trigger-term coverage from good to comprehensive.

State the role context (for the online advisor answering 定制游 inquiries) so the 'when' is anchored to a concrete usage situation rather than only 'what'.

DimensionReasoningScore

Specificity

The description names the exact product ('定制游产品说明(HL-P-03)') and enumerates concrete content areas with hard facts — '基础5晚', '包含与不含', '规划通话流程', '常见目的地(含高原标记)', '每日安排框架', '人数上限' — comprehensively covering every section of the body. It is not score 4 because coverage has no visible gaps.

5 / 5

Completeness

The 'what' is explicit and detailed (product spec for HL-P-03 covering inclusions, exclusions, planning call, destinations, itinerary), but there is no 'Use when...' clause or equivalent trigger guidance telling Claude when to consult this skill. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: '定制游', '产品说明', 'HL-P-03', '规划通话', '高原', '人数上限' — terms a travel advisor would naturally say. A few natural synonyms are missing (e.g., '报价/起价', '私人向导', '行程'), so it falls just below the comprehensive-with-synonyms anchor of 5.

4 / 5

Distinctiveness Conflict Risk

The company name '海岚旅行' plus the unique product code 'HL-P-03' carve out a clear niche with minimal conflict risk against any other skill — a user mentioning these terms can only mean this skill.

5 / 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

EverMind-AI/Raven

Path

experimental/simulation/scenarios/travel_agency/materials/premium-package/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.