CtrlK
BlogDocsLog inGet started
Tessl Logo

booking-policy

海岚旅行预订规则(HL-CS-POL-02 V3.1):合同与生效、预付款与尾款、取消与改期、折扣、儿童与长者、保险、个人信息、人数上限。对客人做付款、退改、合同方面的说明只以此为准。

69

Quality

85%

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

100%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 exemplary single-file policy skill: lean, information-dense, precisely quantified, and cleanly organized into eight self-contained sections. It teaches only what Claude could not know (the company's specific rules) and every rule is directly answerable to a guest.

DimensionReasoningScore

Conciseness

Every line is a load-bearing policy fact (percentages, day thresholds, price ratios, caps) with zero padding and no explanation of concepts Claude already knows. The version/date line ('V3.1,2026年9月15日起执行') identifies the policy rather than issuing time-conditional instructions, so it does not trigger the date-penalty.

5 / 5

Actionability

As an instruction-only skill the guidance is fully concrete and directly usable: exact figures such as '20%作为预付款,尾款于出发前30天付清', a cancellation fee table (不扣除/20%/40%/60%), '儿童基础价按成人基础价的70%', '每人60元', '每团最多8人/6人', with explicit boundaries ('不打折、不比价、不抹零').

5 / 5

Workflow Clarity

This is a single-purpose reference skill under 50 lines with no multi-step process; the per-topic sections (付款, 取消与改期, 折扣...) make the single action — answer a guest question from the matching section — unambiguous, and no destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

The skill has no bundle files and needs none — all content fits in a short body with eight clearly numbered sections, satisfying the simple-skill exception (well-organized sections, no external references required).

5 / 5

Total

20

/

20

Passed

Description

70%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, well-bounded description with strong distinctiveness and good natural trigger terms, weakened only by the absence of an explicit 'Use when...' trigger clause and an action-verb framing. It clearly communicates scope but leaves invocation timing implicit.

Suggestions

Add an explicit trigger clause, e.g. append 'Use when answering guest questions about payment (付款/尾款), cancellation or rescheduling (取消/退改), contracts, discounts, child/senior pricing, or group size limits.'

Reframe the topic list with action verbs (e.g., 'Answers and explains... / Calculates deposit, balance, and cancellation fees...') to move from a domain enumeration to concrete capabilities.

Include a couple of common user synonyms such as 退款 and 报价/优惠 so natural guest phrasings match the description.

DimensionReasoningScore

Specificity

The description enumerates concrete, well-scoped capability areas — '合同与生效、预付款与尾款、取消与改期、折扣、儿童与长者、保险、个人信息、人数上限' — with a specific document identity ('HL-CS-POL-02 V3.1'). It is a topic list rather than a list of actions, and verbs are minimal, which keeps it at 4 rather than 5.

4 / 5

Completeness

The 'what' is clear (the eight policy areas), and the closing sentence '对客人做付款、退改、合同方面的说明只以此为准' gestures at when to use it, but there is no explicit 'Use when...' trigger clause; per the judging guidelines, a missing explicit trigger clause caps completeness at 3 rather than 4.

3 / 5

Trigger Term Quality

Natural terms a user would say are present: '付款', '退改', '合同', '取消', '折扣', '保险', '儿童', '人数上限', plus '预订' itself. A few common synonyms/variations (e.g., 退款, 报价, 尾款 vs. 全款) are missing, so it falls just short of the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The description is tied to a named company policy ('海岚旅行预订规则(HL-CS-POL-02 V3.1)') with a clear niche — answering guest questions about payment, cancellation/rescheduling, and contracts — so it is highly unlikely to trigger for the wrong skill.

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