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-employee-diagnosisgit 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-employee-diagnosis)<a href="https://agentmods.dev/skills/guofu-shiqu/ux-expert-skills/exp-employee-diagnosis"><img src="https://agentmods.dev/badge/skills/guofu-shiqu/ux-expert-skills/exp-employee-diagnosis/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-employee-diagnosis"><img src="https://agentmods.dev/badge/skills/guofu-shiqu/ux-expert-skills/exp-employee-diagnosis.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.00035 | $0.00805 |
| Opus 5 | $0.00017 | $0.00402 |
| Sonnet 5 | $0.00007 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
exp-employee-diagnosis 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 12d 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.
What it actually says
员工体验诊断
分析员工 JTBD、服务目标与用户期待的匹配度，评估员工体验如何传导到客户体验。
触发条件
- 客户体验问题可能源于员工侧
- 员工能力、工具、权限、信息或情绪压力有问题
- 需要分析员工体验对客户体验的影响
- 需要改善员工支持和赋能
核心能力
1. 分析员工 JTBD
理解员工的工作任务和目标：
- 员工想要完成什么任务（功能任务）
- 员工想要感受到什么（情绪任务）
- 员工想要在同事/客户眼中呈现什么（社会任务）
2. 检查服务目标匹配度
评估员工的服务目标与用户期待是否匹配：
- 员工理解的用户目标是什么
- 员工实际交付的是什么
- 差距在哪里
3. 评估支持度
从以下维度评估员工是否得到足够支持：
| 支持类型 | 检查内容 |
|---|---|
| 信息支持 | 员工是否能方便获取用户信息、产品信息、政策信息 |
| 工具支持 | 员工使用的系统/工具是否好用、高效、稳定 |
| 知识支持 | 员工是否得到足够的培训、知识库、最佳实践 |
| 权限支持 | 员工是否有足够权限快速解决用户问题 |
4. 评估情绪压力
评估员工的情绪压力和倦怠风险：
- 工作量是否合理
- 是否有情绪疏导机制
- 是否感到被支持和赋能
5. 评估协作成本
评估跨部门协作是否顺畅：
- 员工是否需要协调多个部门才能解决用户问题
- 协作流程是否清晰高效
6. 分析传导机制
分析员工体验如何传导到客户体验：
- 员工情绪 → 服务态度 → 客户感受
- 员工工具效率 → 响应速度 → 客户满意度
- 员工信息获取 → 问题解决质量 → 客户信任
输出格式：员工体验分析报告
【员工体验分析报告】
▸ 员工任务：
功能任务：[帮我...]
情绪任务：[让我感到...]
社会任务：[让我看起来...]
▸ JTBD：[员工的 JTBD]
▸ 服务目标：[员工理解的服务目标]
▸ 用户期待：[用户实际期待的是什么]
▸ 支持度评估：
信息支持：[充足/不足]，问题：[...]
工具支持：[充足/不足]，问题：[...]
知识支持：[充足/不足]，问题：[...]
权限支持：[充足/不足]，问题：[...]
▸ 情绪压力：[高/中/低]，问题：[...]
▸ 协作成本：[高/中/低]，问题：[...]
▸ 对客户体验的影响：
[员工体验问题如何传导到客户体验]
▸ 改善机会：
1. [...]
2. [...]
...
使用方法
当客户体验问题可能源于员工侧时，调用本 skill 进行员工体验诊断，找出根本原并提供改善方向。
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.
- 12d ago First seen · 99 lines · 35 tokens per session scan A 81c6189ca97c
exp-employee-diagnosis is a skill published in the GitHub repository guofu-shiqu/ux-expert-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 805 once invoked, about $0.0002 per session on Opus 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
api-design
Design public interfaces for libraries and tools that other people depend on. Use when designing or reviewing a public API surface, deciding what to export, naming functions and CLI flags, adding configuration options, planning deprecations, or when the user asks "is this a good API" or "how do I change this without…
code-review
Review a pull request the way a good open-source maintainer does. Use when reviewing an incoming PR, when the user asks "review this PR" or "is this ready to merge", when triaging a stale PR queue, or when writing review feedback to an external contributor. Covers what to check and in what order, severity levels…
governance-and-sustainability
Keep a project and its maintainers alive over years. Use when deciding how decisions get made, writing GOVERNANCE.md or a code of conduct enforcement process, adding or removing maintainers, handling burnout or stepping away, setting up funding (GitHub Sponsors, Open Collective, a foundation), handling a fork or a…
open-source
Generates the complete open-source governance of a repository: README, LICENSE, REUSE.toml and SPDX headers, CONTRIBUTING, SECURITY, CODEOFCONDUCT, GOVERNANCE, CHANGELOG, .github issue/PR templates, GitHub Actions, Dependabot, conventional commits, GPG/DCO signing, git flow and ADRs. Use whenever the user wants to…
contributor-experience
Turn users into contributors and make their first PR succeed. Use when a project gets stars but no contributions, when first-time PRs stall or get abandoned, when writing or improving CONTRIBUTING.md, when setting up a dev environment that works on the first try, or when the user asks "how do I get contributors" or…
dependency-hygiene
Manage a project's dependencies so they stay small, current, and safe. Use when deciding whether to add a dependency, auditing an existing dependency tree, configuring Dependabot or Renovate, dealing with upgrade churn or a flood of bot PRs, resolving version conflicts, choosing between dependency ranges and pinning…