Token导航 LogoToken导航

Agent Skill · 开发

unreasonable-hospitality(不合理的招待)

unreasonable-hospitality 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

unreasonable-hospitality 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 10,203。

总安装 2,351周安装 101GitHub Stars 公开资料未说明下载 824核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.1.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:unreasonable-hospitality(不合理的招待)
来源仓库:https://github.com/zacko2o/unreasonable-hospitality
安装命令:
openclaw skills install unreasonable-hospitality
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install unreasonable-hospitality

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

应用 Will Guidara 服务理念优化 AI 产品用户体验。引入 PDCA 闭环反馈提升交互友好度与满意度。致力于将功能性工具转化为令人愉悦的服务载体。强调情感化设计与细节打磨的价值取向。unreasonable-hospitality 属于开发类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install unreasonable-hospitality;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

unreasonable-hospitality 怎么安装?

在终端执行 openclaw skills install unreasonable-hospitality。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

unreasonable-hospitality 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

unreasonable-hospitality 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

unreasonable-hospitality 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

unreasonable-hospitality 用的人多吗?

公开数据是累计安装 2,351 次,近一周安装 101 次,下载 824 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

unreasonable-hospitality 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
unreasonable-hospitality

不合理的招待 · 本页

2,351—只读MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
unreasonable-hospitality
description
Apply Will Guidara's 'Unreasonable Hospitality' + PDCA closed-loop feedback to AI product design, development, and interaction. Transforms products from functional to emotionally memorable AND sustainably excellent. Use when: designing user experiences, reviewing product quality, writing copy/microcopy, building AI assistants, creating onboarding flows, handling error states, giving feedback, building feedback loops, improving team processes, or making something 'feel better' or 'more human'. Core: Technical Excellence (95%) × Hospitality Layer (5%) × Feedback Loop = World-class that lasts. Covers: 95/5 rule, one-size-fits-one, read-and-react, earned informality, PDCA hospitality loop, closed-loop metrics, accountability without bureaucracy.

Unreasonable Hospitality for AI & Product Design

"No one who ever changed the game did so by being reasonable." — Will Guidara, *Unreasonable Hospitality*

Transform products from functional to unforgettable by applying the principles that made Eleven Madison Park the #1 restaurant in the world.

Core Equation

Unreasonable Hospitality = Technical Excellence × Emotional Intelligence × Intentional Generosity × Feedback Loop

Miss any one → the magic breaks:

  • No technical excellence → being nice but useless
  • No emotional intelligence → technically perfect but cold
  • No intentional generosity → good but forgettable
  • No feedback loop → great once, inconsistent forever

The 7 Laws (Memorize These)

1. Service is the Floor, Hospitality is the Ceiling

Service = did it work? Hospitality = how did it *feel*? Every feature, response, or screen must answer both questions.

2. The 95/5 Rule

95% engineering rigor. 5% "unreasonable" generosity. That 5% creates 50%+ of the emotional impact. Budget for delight.

3. One Size Fits One

Generic ≠ personalized. Read context, history, signals. Ask: "What does *this* user need *right now*?"

4. Read and React

Don't wait for feedback. Observe → interpret → act. Anticipate needs before they're expressed.

5. Earned Informality

Master the rules first. Then break them with intention. Playfulness without competence = sloppiness.

6. Details Are the Product

Excellence = thousands of micro-details executed perfectly. Users can't articulate why something feels premium — but they feel it.

7. Connection Over Transaction

You're not completing tasks. You're building relationships. Every interaction is a chance to make someone feel seen.

How to Apply

When Designing UI/UX

  1. Read references/checklist.md — walk through every checkpoint
  2. Map the user's emotional journey (not just the task flow)
  3. Identify 3 "hot dog moments" — unexpected delights unique to your product
  4. Apply earned informality: nail basics first, then add personality
  5. Test the Ultimate Question: Will they *remember* this?

When Writing Copy/Microcopy

  • Error messages: Empathize first, explain second, help third

- ❌ "Error 404: Page not found" - ✅ "Hmm, that page seems to have wandered off. Let's get you back on track."

  • Empty states: Guide warmly, don't just show a void

- ❌ "No results" - ✅ "Nothing here yet — but that's about to change."

  • Success states: Celebrate with the user

- ❌ "Saved." - ✅ "All set! Your changes are live."

  • Loading states: Respect their time, don't just spin
  • Tone: Warm but not sycophantic. Concise but not cold.

When Building AI Assistants

  • First response: Make it feel like a warm welcome, not a form fill
  • Understand intent: Read what they *mean*, not just what they *typed*
  • Anticipate: Offer the next step before they ask
  • Remember: Use context and history — don't make them repeat themselves
  • Know when to shut up: Hospitality includes not overwhelming people
  • Fail gracefully: "I'm not sure about that, but here's what I can do" > "Error"
  • The 5%: Occasionally surprise with something above and beyond the ask

When Reviewing Product Quality

Read references/principles.md for the 12 principles, then score:

DimensionQuestionScore
TechnicalDoes it work flawlessly?/10
SpeedDoes it respect the user's time?/10
ClarityIs it immediately understandable?/10
EmpathyDoes it understand the user's emotional state?/10
DelightIs there at least one "unreasonable" moment?/10
MemoryWill the user remember this experience?/10

Score < 50 → Fix the basics (service) Score 50-70 → Good but forgettable Score 70-85 → Strong — add more 5% moments Score 85+ → World-class hospitality

When Giving Feedback

  • Praise publicly, criticize privately
  • Frame criticism as investment: "I believe you can do better"
  • Be specific and immediate
  • Suggest, don't command — make it feel like a gift

The Hospitality Closed Loop (PDCA)

Hospitality isn't a one-time act — it's a system. Without a feedback loop, even the best intentions decay into inconsistency. Apply the PDCA cycle to sustain and improve hospitality:

Plan → Do → Check → Act → Repeat

┌─────────────────────────────────────────────────────────┐
│  PLAN: Define the experience standard                   │
│  • What should the user feel at each touchpoint?        │
│  • Who owns each part of the experience?                │
│  • What signals will we read? (SMART goals for UX)      │
├─────────────────────────────────────────────────────────┤
│  DO: Execute with standard + hospitality                │
│  • Follow the 95% foundation rigorously                 │
│  • Apply the 5% improvisational hospitality             │
│  • Every team member knows their "ownership zone"       │
├─────────────────────────────────────────────────────────┤
│  CHECK: Feedback must flow — fast, honest, structured   │
│  • Measure: task completion, user sentiment, delight    │
│  • 48h rule: feedback within 48 hours or it's stale     │
│  • Bilateral: team → user AND user → team               │
│  • Quantify: not just "users liked it" but NPS, scores  │
├─────────────────────────────────────────────────────────┤
│  ACT: Improve based on what you learned                 │
│  • Retrospective: what worked, what didn't, what's next │
│  • Knowledge capture: write it down or it never happened│
│  • Process refinement: simplify, don't accumulate       │
│  • Promote insights to the Plan phase → loop restarts   │
└─────────────────────────────────────────────────────────┘

5 Metrics That Matter:

  1. Task Completion Rate — Does the core function work? (Service baseline)
  2. Feedback Timeliness — How fast do we learn from users? (<48h = healthy)
  3. Issue Resolution Rate — Problems found → fixed → verified closed
  4. Response Time — How fast does the team/product react to signals?
  5. Rework Rate — How often do we redo things? (Lower = better system)

Closed-Loop Anti-Patterns:

Anti-PatternSymptomFix
Pseudo-loopFeedback collected but never acted onAssign owner + deadline to every insight
Filtered feedbackOnly good news reaches decision-makersCreate safe channels for honest feedback
Fragmented flowInfo scattered across tools/peopleSingle source of truth (one board/doc)
All process, no soulPerfect PDCA but zero emotional impactPDCA is the skeleton; hospitality is the heart

The key insight: PDCA keeps the machine running. Hospitality gives the machine a soul. You need both.

Anti-Patterns (What NOT to Do)

Anti-PatternWhy It FailsFix
Fake personalization"Hi {firstName}!" feels roboticUse real context, not mail-merge
Over-helpingConstant popups/tooltips = annoyingHelp when needed, disappear when not
Forced delightConfetti on a 500 error? No.Match tone to emotional context
Sycophantic praise"Great question!" on every inputBe genuine or be quiet
Feature over feeling"We added 47 features!""Here's one thing that'll change your day"
Ignoring the basicsFun animations but slow loading95% must be solid before the 5%
One-size-fits-allSame onboarding for everyoneAdapt to context, skill level, goals

Quick Reference

For the full 12 principles with examples → references/principles.md For the design & development checklist → references/checklist.md

The Bottom Line

"It was our pursuit of excellence that brought us to the table, but it was our pursuit of Unreasonable Hospitality that took us to the top."

Build things that work perfectly. Then make them feel like magic.

平台分布

OpenClaw

96.12%
按下载量换算792

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills