Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add guofu-shiqu/ux-expert-skills --skill exp-service-blueprintgit clone --depth 1 https://github.com/guofu-shiqu/ux-expert-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/guofu-shiqu/ux-expert-skills/exp-service-blueprint)<a href="https://agentmods.dev/skills/guofu-shiqu/ux-expert-skills/exp-service-blueprint"><img src="https://agentmods.dev/badge/skills/guofu-shiqu/ux-expert-skills/exp-service-blueprint/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/guofu-shiqu/ux-expert-skills/exp-service-blueprint"><img src="https://agentmods.dev/badge/skills/guofu-shiqu/ux-expert-skills/exp-service-blueprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.01267 |
| Opus 5.5 | $0.00016 | $0.00507 |
| Sonnet 5.5 | $0.00008 | $0.00253 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
exp-service-blueprint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
服务蓝图绘制
将用户行为、前台触点、员工动作、后台流程、支撑系统同步展开，识别各层的痛点和机会点。
触发条件
- 需要分析或优化一项服务的完整交付过程
- 涉及前台、后台、员工和系统的协同问题
- 需要识别服务交付中的断点和摩擦
- 需要改善服务质量和效率
核心能力
服务蓝图结构
服务蓝图是一个阶段 × 六层的矩阵：
| 层级 | 内容 | 说明 |
|---|---|---|
| 1. 用户行为层 | 用户在旅程中做什么 | 用户的实际行为序列 |
| 2. 前台触点层 | 用户直接接触的界面/人员 | 用户能看到和交互的部分 |
| 3. 后台员工层 | 员工在幕后做什么 | 支持前台交付的员工动作 |
| 4. 后台流程层 | 内部流程和协作 | 跨部门的协作和流程 |
| 5. 支撑系统层 | 系统、工具、数据 | 支撑服务交付的技术和系统 |
| 6. 证据层 | 用户带走的有形/无形证据 | 影响用户记忆和评价的证据 |
绘制步骤
- 定义服务场景 — 明确要分析的服务和边界
- 梳理用户行为 — 列出用户在旅程中做了什么
- 展开前台触点 — 列出用户直接接触的界面和人员
- 展开后台员工动作 — 列出员工在幕后做的支持动作
- 展开后台流程 — 列出内部流程和协作
- 展开支撑系统 — 列出系统、工具、数据
- 识别证据 — 列出用户带走的证据
- 识别痛点和机会 — 逐层检查问题
服务设计检查项
- 可见性 — 用户的等待是否有反馈
- 连续性 — 跨渠道、跨触点的体验是否连贯
- 可靠性 — 服务是否每次都能稳定交付
- 响应性 — 问题能否被快速解决
- 保证性 — 用户是否感到专业和可信
- 共情性 — 用户是否感到被理解和重视
输出格式：服务蓝图
【服务蓝图】
服务名称：[...]
场景边界：开始于[...]，结束于[...]
┌─────────────┬──────────────┬──────────────┬──────────────┬──────────────┬──────────────┐
│ 阶段 → │ 阶段1 │ 阶段2 │ 阶段3 │ ... │ │
├─────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ 用户行为层 │ [行为1] │ [行为2] │ [行为3] │ ... │
├─────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ 前台触点层 │ [触点1] │ [触点2] │ [触点3] │ ... │
├─────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ 后台员工层 │ [动作1] │ [动作2] │ [动作3] │ ... │
├─────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ 后台流程层 │ [流程1] │ [流程2] │ [流程3] │ ... │
├─────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ 支撑系统层 │ [系统1] │ [系统2] │ [系统3] │ ... │
├─────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ 证据层 │ [证据1] │ [证据2] │ [证据3] │ ... │
└─────────────┴──────────────┴──────────────┴──────────────┴──────────────┘
▸ 痛点识别：
用户行为层：[...]
前台触点层：[...]
后台员工层：[...]
后台流程层：[...]
支撑系统层：[...]
▸ 机会点识别：
[...]
▸ 服务设计检查：
可见性：[是/否]，问题：[...]
连续性：[是/否]，问题：[...]
可靠性：[是/否]，问题：[...]
响应性：[是/否]，问题：[...]
保证性：[是/否]，问题：[...]
共情性：[是/否]，问题：[...]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 98 lines · 40 tokens per session scan A 7a3d46497bb0
exp-service-blueprint is a skill published in the GitHub repository guofu-shiqu/ux-expert-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,267 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
open-pencil
Work with Figma .fig design files and the running OpenPencil editor — inspect structure, query nodes, analyze design tokens, export PNG/SVG/PDF/JSX, and modify designs programmatically. Use when asked to open, inspect, export, analyze, or edit .fig files, or to control the running OpenPencil app.
openclaw-carapace
Build or modify OpenClaw application UI using canonical semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives. Use for product interfaces, component styling, theme work, or design-token integration.
openclaw-design-system
Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.
openclaw-brand
Apply OpenClaw visual identity to logos, typography, imagery, voice, documents, presentations, social graphics, and launch materials. Use when the task changes brand identity rather than ordinary product UI or public-page composition.
openclaw-design-audit
Audit OpenClaw frontend code and rendered interfaces for Carapace drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.
openclaw-design
Route OpenClaw design work to canonical brand, Carapace product-interface, marketing-page, or design-audit guidance. Use when a task touches OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or Carapace compliance.