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-touchpoint-auditgit 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-touchpoint-audit)<a href="https://agentmods.dev/skills/guofu-shiqu/ux-expert-skills/exp-touchpoint-audit"><img src="https://agentmods.dev/badge/skills/guofu-shiqu/ux-expert-skills/exp-touchpoint-audit/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-touchpoint-audit"><img src="https://agentmods.dev/badge/skills/guofu-shiqu/ux-expert-skills/exp-touchpoint-audit.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.00043 | $0.01559 |
| Opus 5 | $0.00022 | $0.00779 |
| Sonnet 5 | $0.00009 | $0.00312 |
| Haiku 4.5 | $0.00004 | $0.00156 |
Grade A, and why
exp-touchpoint-audit 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
触点审计
全面盘点用户与产品/品牌的所有接触触点，评估各触点体验质量，发现覆盖盲区和体验断点。
触发条件
- 需要全面盘点用户触点
- 需要评估各触点体验质量
- 需要发现触点覆盖盲区
- 需要优化跨触点体验一致性
- 需要设计或优化触点策略
核心能力
1. 触点发现与分类
从用户视角全面发现触点，按渠道和类型分类：
| 触点类型 | 典型触点 | 用户角色 | 体验重点 |
|---|---|---|---|
| 认知触点 | 广告、搜索结果、社媒、口碑 | 潜在用户 | 第一印象、价值传达 |
| 考虑触点 | 官网、App Store、评测、对比页 | 考虑用户 | 信息充分性、决策支持 |
| 获取触点 | 注册、下载、购买、开通 | 新用户 | 流畅度、信任感 |
| 使用触点 | 核心功能、搜索、设置、通知 | 活跃用户 | 效率、易用性 |
| 服务触点 | 帮助中心、客服、社区、更新日志 | 求助用户 | 响应速度、解决效率 |
| 离开触点 | 注销、取消订阅、投诉渠道 | 流失用户 | 退出顺畅性、挽回机会 |
| 传播触点 | 分享、评价、推荐、社媒提及 | 推荐者 | 分享动力、口碑管理 |
2. 触点审计维度
对每个触点从以下维度审计：
体验质量维度
- 易用性 — 用户能否轻松完成操作
- 可用性 — 功能是否稳定可用
- 一致性 — 跨触点体验是否连贯
- 情感性 — 触发的情绪是正还是负
业务价值维度
- 覆盖广度 — 触达了多少目标用户
- 转化效率 — 从进入触点到下一触点的转化率
- 用户满意度 — 该触点的 CSAT/NPS
- 品牌印记 — 用户记住了什么
运营健康度维度
- 数据可得性 — 该触点的数据是否可追踪
- 优化频率 — 该触点多久优化一次
- 责任人 — 该触点是否有明确负责团队
- 异常监测 — 是否有异常预警机制
3. 触点矩阵分析
以"体验重要性"和"当前体验质量"为两轴，将触点定位到矩阵：
高重要性 + 低质量 → 优先改善（短板触点）
高重要性 + 高质量 → 保持优势（核心触点）
低重要性 + 低质量 → 低优先级（可维持现状）
低重要性 + 高质量 → 过度投入（可考虑降成本）
4. 跨触点一致性检查
检查跨触点体验是否连贯：
- 视觉一致性 — 品牌视觉是否统一
- 语言一致性 — 文案语气是否一致
- 数据一致性 — 用户信息是否跨触点同步
- 流程一致性 — 跨触点流程是否顺畅衔接
- 情绪一致性 — 情绪曲线是否连贯
输出格式：触点审计报告
【触点审计报告】
▸ 审计范围：[产品/服务名称]
▸ 审计时间：[...]
▸ 触点总数：[X 个]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
▸ 一、触点清单
触点类型 │ 触点名称 │ 用户角色 │ 当前质量 │ 重要性 │ 优先级
────────┼─────────┼─────────┼─────────┼─────────┼────────
认知触点 │ [名称] │ [...] │ [高/中/低]│ [高/中/低]│ [P0/P1/P2]
考虑触点 │ [名称] │ [...] │ [...] │ [...] │ [...]
获取触点 │ [名称] │ [...] │ [...] │ [...] │ [...]
使用触点 │ [名称] │ [...] │ [...] │ [...] │ [...]
服务触点 │ [名称] │ [...] │ [...] │ [...] │ [...]
离开触点 │ [名称] │ [...] │ [...] │ [...] │ [...]
传播触点 │ [名称] │ [...] │ [...] │ [...] │ [...]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
▸ 二、触点矩阵分析
高重要性 + 低质量（优先改善）：
1. [触点名称]，问题：[...]，建议：[...]
2. [...]
高重要性 + 高质量（保持优势）：
1. [触点名称]，优势：[...]，可复用：[...]
2. [...]
低重要性 + 低质量（低优先级）：
1. [...]
低重要性 + 高质量（可考虑降成本）：
1. [...]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
▸ 三、覆盖盲区分析
用户旅程中缺少的触点：
1. [场景]，缺失触点：[...]，影响：[...]
2. [...]
用户无法找到帮助的场景：
1. [...]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
▸ 四、跨触点一致性检查
视觉一致性：[一致/不一致]，问题：[...]
语言一致性：[一致/不一致]，问题：[...]
数据一致性：[一致/不一致]，问题：[...]
流程一致性：[一致/不一致]，问题：[...]
情绪一致性：[一致/不一致]，问题：[...]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
▸ 五、行动建议
紧急改善（本月）：
1. [触点]，动作：[...]，负责：[...]
中期优化（本季度）：
1. [触点]，动作：[...]，负责：[...]
长期规划（本年）：
1. [触点]，动作：[...]，负责：[...]
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 · 155 lines · 43 tokens per session scan A a851e475494a
exp-touchpoint-audit is a skill published in the GitHub repository guofu-shiqu/ux-expert-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 1,559 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
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…
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…
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…