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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 a well-organized, concise instruction skill with a clear sequenced workflow and validation section. The main improvements would be removing the intro/overview redundancy and tightening a few abstract bullets into more prescriptive guidance.

Suggestions

Remove the redundancy between the opening sentence and the Overview paragraph, which both state the equal-treatment-plus-personal-attention idea.

Tighten abstract bullets like 'Treat all guests with the same level of respect' into more prescriptive guidance (e.g., specify how equality is verified per guest).

Interleave validation checkpoints within the Steps rather than only at the end, so each step has an explicit verify-before-proceeding cue.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with no padding about concepts Claude already knows, but the opening line and the Overview paragraph restate the same idea ('treating guests equally while providing personalized attention'), a minor redundancy. Not a 5 because of that duplication; not a 3 because the rest is efficient.	4 / 5
Actionability	Concrete, specific instructions such as 'Station a scribe behind a screen', 'send messengers to their family', and 'show your own meal matches theirs' give actionable guidance. Not a 5 because some bullets ('Treat all guests with the same level of respect') stay somewhat abstract rather than fully prescriptive.	4 / 5
Workflow Clarity	Four steps are clearly sequenced and a dedicated Validation section provides verification checkpoints for equal treatment, follow-up care, and conflict resolution. Not a 5 because validation is a separate trailing section rather than interleaved per-step checkpoints with explicit feedback loops.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, with well-organized sections (Overview, Steps, Expected Outcomes, Validation) and no need for external references — meeting the simple-skill exception for a top score.	5 / 5
	Total	17 / 20 Passed

Description

92%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 strong: it opens with an explicit 'Use when' trigger, enumerates four concrete capabilities, and occupies a distinctive niche. The only minor gap is a lack of synonyms or variations in trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Provides equal treatment', 'records personal details via a scribe behind a screen', 'sends follow-up gifts', 'resolves perceived slights through transparent demonstration' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (the four concrete actions) and 'when' ('Use when hosting guests, managing dependents, or building loyalty through hospitality') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases like 'hosting guests', 'managing dependents', and 'building loyalty through hospitality' are terms a user might say, but coverage lacks synonyms or common variations of the domain. Not a 3 because the terms are genuinely natural; not a 5 because no synonyms/extensions are present.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (hospitality/guest management) with distinct triggers that are unlikely to fire for unrelated skills, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: baojie/shiji-kb
Path: kg/ontology/ontology-v1/skus/procedural/skill_150/SKILL.md
Commit: 6b836e3

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.