CtrlK
BlogDocsLog inGet started
Tessl Logo

guest-hospitality-protocol

Use when hosting guests, managing dependents, or building loyalty through hospitality. Provides equal treatment regardless of status, records personal details via a scribe behind a screen, sends follow-up gifts to guests' families, and resolves perceived slights through transparent demonstration.

75

Quality

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and actionable with explicit validation steps, scoring high on actionability, workflow clarity, and progressive disclosure. Its only weakness is minor redundancy between the intro line and the Overview section, which slightly hurts conciseness.

Suggestions

Merge or remove the redundant opening sentence and the Overview section, which both express the same 'equal treatment plus personalized concern' idea — keep only one.

Tighten step headers so each header adds information beyond its bullets (e.g., the 'Equal Treatment' header merely labels what its bullets already state).

DimensionReasoningScore

Conciseness

The body is mostly lean bullet points, but the opening line ('A systematic approach to treating guests equally while providing personalized attention to build deep loyalty') and the Overview section restate the same idea redundantly; it is not the level below because it avoids explaining concepts Claude already knows, and not the level above because of the duplicate framing.

2 / 3

Actionability

Concrete, specific instructions throughout — 'Station a scribe behind a screen', 'send messengers to their family', 'Deliver gifts or assistance to the guest's relatives', 'show your own meal matches theirs' — giving actionable guidance appropriate for an instruction-only skill; it is not the level below because guidance is complete and specific rather than vague or pseudocode-like.

3 / 3

Workflow Clarity

A clear four-step sequence (Equal Treatment, Personal Information Recording, Follow-up Care, Conflict Resolution) is paired with a dedicated Validation section containing three explicit verification checks; it is not the level below because validation checkpoints are explicit, not implicit.

3 / 3

Progressive Disclosure

At under 50 lines with no need for external references, the well-organized sections (Overview, Steps, Expected Outcomes, Validation) satisfy the simple-skill allowance; it is not the level below because organization is clear with no nested-reference problem.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong: it opens with an explicit 'Use when...' trigger, lists several concrete capabilities in third person, and occupies a clearly distinct niche. No revisions needed for it to function well as a skill trigger.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'records personal details via a scribe behind a screen', 'sends follow-up gifts to guests' families', 'resolves perceived slights through transparent demonstration' — matching the anchor for multiple specific concrete actions; it is not the level below because it goes well beyond naming a domain.

3 / 3

Completeness

Explicitly answers both 'what' (provides equal treatment, records details, sends follow-up, resolves slights) and 'when' via the 'Use when hosting guests...' trigger clause; it is not the level below because the when-trigger is explicit, not implied.

3 / 3

Trigger Term Quality

Natural user-facing terms are present — 'hosting guests, managing dependents, or building loyalty through hospitality' — giving good coverage of phrases a user would actually say; it is not the level below because these are not generic jargon.

3 / 3

Distinctiveness Conflict Risk

A clear niche (guest hospitality protocol) with distinct triggers unlikely to collide with other skills; it is not the level below because the domain is specific rather than overlapping with broad categories.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
baojie/shiji-kb
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.