CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

value-package

海岚旅行经济游产品说明(HL-P-01):基础3晚,适用对象、包含与不含、目的地清单、每日安排框架、人数上限。

62

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/value-package/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 an exemplary lean data-sheet: fully tabular, unpadded, and concrete about constraints, inclusions, and the day-by-day framework. The only weaknesses are minor — a dangling reference to an unprovided SOP selection matrix and a few unspecified details (departure cities, exact lodging standard, total price).

Suggestions

Either inline the relevant rule from the SOP 选择矩阵 or drop the "(按 SOP 选择矩阵)" qualifier, since the referenced artifact is not part of the skill bundle.

Specify the departure-city scope (or state how it is determined) and the per-person package price or price range, which a customer-facing spec will almost always be asked for.

DimensionReasoningScore

Conciseness

The body is dense tabular data ("3晚,可加晚,不可减晚", "每团8人") with zero concept explanations or padding, and the closing scope note "每日安排只写到框架这一层,不写具体餐馆、景点开放时间或价格" efficiently sets boundaries. Every token earns its place.

5 / 5

Actionability

Guidance is concrete: "高铁二等座或经济舱", "单程超过6小时的,首末日为交通日", "接送站(可加购)" give executable constraints and add-on options. Not a 5 because departure cities are unspecified, lodging is only loosely defined ("经济型酒店或精品青旅"), and no total price is given — minor gaps for a spec whose job is answering customer questions.

4 / 5

Workflow Clarity

This is a single-purpose reference skill, and the daily framework ("第1天…第2天…第3天…加晚的每一天…最后一天") is an unambiguous, clearly sequenced structure; no destructive or batch operations exist, so no validation checkpoints are needed. The simple-skill exception applies.

5 / 5

Progressive Disclosure

Sections (包含/不含/目的地清单/每日安排框架) are well organized and the skill is self-contained and under 50 lines. Not a 5 because "(按 SOP 选择矩阵)" points to an external artifact that is neither bundled nor explained — an unclear reference and minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

58%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 specific about what the skill contains (product HL-P-01's coverage areas) and distinct due to the named company and product code. Its main weaknesses are the complete absence of any 'when to use' trigger guidance and thin natural-keyword coverage, which together keep completeness and trigger quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "当客人咨询经济游、低价套餐、HL-P-01 或人均预算500元以内的行程时使用", to answer 'when' as well as 'what'.

Include natural synonyms users would actually say — 低价游、穷游、特价、省钱游 — so the skill triggers on real phrasings, not just the formal product name.

Lead with a capability-style verb phrase (e.g. "提供…产品要素,用于报价、行程推荐与客人答疑") instead of a pure table-of-contents listing, to make the skill's purpose actionable at a glance.

DimensionReasoningScore

Specificity

The description enumerates six concrete content items — "基础3晚", "适用对象、包含与不含", "目的地清单", "每日安排框架", "人数上限" — plus the product code HL-P-01. It lists several specific items with minor gaps, but describes contents rather than concrete actions/capabilities, so it is not a 5.

4 / 5

Completeness

The 'what' is explicit and specific (a product spec covering nights, inclusions/exclusions, destinations, itinerary framework, group size), but there is no 'Use when…' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 2 because the 'what' is clear, not vague.

3 / 5

Trigger Term Quality

Relevant domain keywords are present ("经济游", "产品说明", "HL-P-01"), but common natural variations a customer or agent would actually say (e.g. 低价游, 穷游, 特价, 省钱) are missing, matching the 'some relevant keywords but missing synonyms' anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

"海岚旅行经济游产品说明(HL-P-01)" names a unique company and product code, giving a clear niche with minimal generic conflict. Not a 5 because it lacks explicit trigger phrases to distinguish it from sibling product skills (e.g. comfort/premium tiers HL-P-02+) in the same line.

4 / 5

Total

14

/

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/value-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.