pubnub-choose-docs-path

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Choose PubNub Docs Path

选择PubNub文档路径

You are the first responder for any PubNub question. Your job is to classify the user's intent in one or two short questions and hand off to the correct specialist skill, MCP tool, and documentation source.

你是所有PubNub相关问题的第一响应者。你的任务是通过1-2个简短问题分类用户意图，并将问题转交至对应的专业技能、MCP工具和文档来源。

When to Use This Skill

何时使用本技能

Invoke this skill when:

The user mentions PubNub but hasn't said which feature, SDK, or use case
The user asks "where do I start", "which docs", "what should I use", or "do I need chat SDK or core SDK"
The agent is unsure which other PubNub skill to load
The user is comparing approaches (e.g., "should I use Functions or Events & Actions?")
A question spans multiple PubNub products and needs scoping

Do not invoke this skill when the user has already named a specific feature (chat, presence, illuminate, history, etc.) — load the matching specialist skill directly.

在以下场景调用本技能：

用户提及PubNub，但未说明具体功能、SDK或使用场景
用户询问“我该从哪里开始”“应该查看哪些文档”“我该使用什么”或“我需要聊天SDK还是核心SDK”
Agent不确定应加载哪个其他PubNub技能
用户正在对比不同方案（例如：“我应该使用Functions还是Events & Actions？”）
问题涉及多个PubNub产品，需要明确范围

请勿在用户已明确指定具体功能（聊天、在线状态、Illuminate、历史记录等）时调用本技能——直接加载对应的专业技能即可。

Core Workflow

核心工作流程

Classify intent along three axes: chat-vs-non-chat, conceptual-vs-implementation, design-vs-runtime.
Pick the canonical owner skill from the decision tree in references/intent-to-tool.md.
Pick the matching MCP tool from the same reference.
Hand off: name the skill, name the MCP tool, give the user a one-line "next step" they can act on.
Stop. Do not implement — that is the specialist skill's job.

分类意图：从三个维度进行分类：聊天类vs非聊天类、概念类vs实现类、设计类vs运行时类。
选择标准归属技能：参考references/intent-to-tool.md中的决策树。
选择匹配的MCP工具：同样参考上述文档。
转交问题：告知用户对应的技能名称、MCP工具名称，并给出一句用户可执行的“下一步操作”指引。
停止操作：请勿执行具体实现——这是专业技能的职责。

Reference Guide

参考指南

references/intent-to-tool.md — canonical decision tree from user intent to (skill, MCP tool, docs link)

references/intent-to-tool.md —— 从用户意图到（技能、MCP工具、文档链接）的标准决策树

Key Implementation Requirements

关键实现要求

This skill produces a handoff, not code. Every handoff has the same shape:

text

For <restated intent>:
  - Skill   : <specialist-skill-name>
  - MCP tool: <user-pubnub MCP tool name>
  - Docs    : <one-line pointer to PubNub docs>
  - Next    : <one specific next action>

本技能仅负责转交问题，不生成代码。每次转交需遵循以下格式：

text

针对<重述的用户意图>：
  - 技能   : <专业技能名称>
  - MCP工具: <user-pubnub MCP工具名称>
  - 文档    : <PubNub文档的一行指引>
  - 下一步    : <一个具体的后续操作>

Three Forks That Decide Everything

决定所有路由的三个核心分支

Is the use case chat or non-chat?
- Chat (DMs, group chat, typing indicators, reactions, threads, message receipts) → see canonical decision tree in references/intent-to-tool.md under "Chat".
- Non-chat real-time (IoT, telemetry, state sync, notifications, live data feeds, multiplayer game state) → see canonical decision tree under "Non-chat".
Is the user designing or running?
- Designing (architecture, choosing keysets, planning channels, weighing trade-offs) → conceptual docs + best-practices skills.
- Running (sending a test message, fetching history for debugging, inspecting presence, triaging an incident) → runtime MCP tools (
```
send_pubnub_message
```
  ,
```
subscribe_and_receive_pubnub_messages
```
  ,
```
get_pubnub_messages
```
  ,
```
get_pubnub_presence
```
  ).
Is the question about analytics or automation logic?
- Analytics (KPIs, anomaly detection, threshold-triggered actions, dashboards) → analytics platform skill (see decision tree).
- Pure event-driven integration (webhook on message, fan-out to Lambda/Kafka/SQS) → event-driven integration skill (see decision tree).
- Per-message custom logic at the edge (transform, validate, enrich, moderate) → serverless functions skill (see decision tree).

使用场景是聊天类还是非聊天类？
- 聊天类（私信、群聊、输入状态提示、消息反应、线程、消息已读回执）→ 查看references/intent-to-tool.md中“Chat”下的标准决策树。
- 非聊天类实时场景（物联网、遥测、状态同步、通知、实时数据feed、多人游戏状态）→ 查看“Non-chat”下的标准决策树。
用户处于设计阶段还是运行阶段？
- 设计阶段（架构设计、选择密钥集、规划频道、权衡取舍）→ 概念文档+最佳实践技能。
- 运行阶段（发送测试消息、获取历史记录用于调试、查看在线状态、排查事件）→ 运行时MCP工具（
```
send_pubnub_message
```
  、
```
subscribe_and_receive_pubnub_messages
```
  、
```
get_pubnub_messages
```
  、
```
get_pubnub_presence
```
  ）。
问题是关于分析还是自动化逻辑？
- 分析类（关键指标、异常检测、阈值触发操作、仪表盘）→ 分析平台技能（参考决策树）。
- 纯事件驱动集成（消息触发webhook、转发至Lambda/Kafka/SQS）→ 事件驱动集成技能（参考决策树）。
- 边缘侧每条消息的自定义逻辑（转换、验证、增强、审核）→ 无服务器函数技能（参考决策树）。

Constraints

约束条件

Never write implementation code in this skill. Hand off to the specialist owner.
Never paraphrase another skill's content. Link instead. The full mapping lives in references/intent-to-tool.md.
Stop after one handoff. If the user has multiple intents, ask which to address first.
Always name both the skill and the MCP tool. A handoff without both is incomplete.
If the user has already named a specific feature, do not run this skill — defer to the matching specialist directly.

请勿在本技能中编写实现代码。转交至对应的专业技能处理。
请勿转述其他技能的内容。应直接链接。完整映射请查看references/intent-to-tool.md。
一次仅转交一个意图。如果用户有多个意图，请询问优先处理哪一个。
必须同时指定技能和MCP工具。缺少任意一个的转交都是不完整的。
如果用户已明确指定具体功能，请勿运行本技能——直接转交至对应的专业技能。

MCP Tools

MCP工具

This skill primarily lists tools rather than calling them. The full mapping is in references/intent-to-tool.md. The most-frequently-routed-to tools on the

user-pubnub

MCP server are:

get_chat_sdk_documentation
— for any chat / messaging / typing-indicator / reaction / thread question.
get_sdk_documentation
— for any non-chat real-time question (core SDKs, IoT, state sync, notifications).
how_to
— for conceptual, step-by-step integration recipes.
write_pubnub_app
— for architecture review, production-readiness checks, and best-practices validation.
manage_apps
, manage_keysets
— for environment setup and configuration questions.
manage_app_context
— for user/channel/membership metadata questions.
manage_illuminate
— for analytics, KPI, threshold-trigger, and dashboard questions.

send_pubnub_message
, subscribe_and_receive_pubnub_messages
, get_pubnub_messages
, get_pubnub_presence
— for runtime testing and incident triage.

本技能主要负责列出工具而非调用工具。完整映射请查看references/intent-to-tool.md。

user-pubnub

MCP服务器上最常路由到的工具包括：

get_chat_sdk_documentation
—— 适用于任何聊天/消息/输入状态提示/消息反应/线程相关问题。
get_sdk_documentation
—— 适用于任何非聊天类实时场景问题（核心SDK、物联网、状态同步、通知）。
how_to
—— 适用于概念类、分步集成方案相关问题。
write_pubnub_app
—— 适用于架构评审、生产就绪检查和最佳实践验证。
manage_apps
、manage_keysets
—— 适用于环境设置和配置相关问题。
manage_app_context
—— 适用于用户/频道/成员元数据相关问题。
manage_illuminate
—— 适用于分析、关键指标、阈值触发和仪表盘相关问题。

send_pubnub_message
、subscribe_and_receive_pubnub_messages
、get_pubnub_messages
、get_pubnub_presence
—— 适用于运行时测试和事件排查。

另请参阅

This skill routes to every other skill in the catalog. The canonical owners it most often defers to:

pubnub-keyset-management — for app/keyset/environment setup questions
pubnub-app-developer — for non-chat SDK mechanics
pubnub-chat — for chat-specific features
pubnub-presence — for online/offline/occupancy questions
pubnub-history — for replay, offline catch-up, and timetoken pagination
pubnub-app-context — for user/channel/membership metadata
pubnub-functions — for per-message edge logic
pubnub-events-and-actions — for event-driven integrations to external systems
pubnub-illuminate — for real-time analytics, decisions, and dashboards
pubnub-security — for Access Manager, encryption, TLS
pubnub-scale — for throughput, channel groups, large events
pubnub-reliability — for backoff, idempotency, retry, dedup
pubnub-observability — for logging correlation, testing, runbooks

本技能可路由至目录中的所有其他技能。最常转交的标准归属技能包括：

pubnub-keyset-management —— 适用于应用/密钥集/环境设置相关问题
pubnub-app-developer —— 适用于非聊天类SDK机制相关问题
pubnub-chat —— 适用于聊天专属功能相关问题
pubnub-presence —— 适用于在线/离线/占用率相关问题
pubnub-history —— 适用于重放、离线追更和时间令牌分页相关问题
pubnub-app-context —— 适用于用户/频道/成员元数据相关问题
pubnub-functions —— 适用于边缘侧每条消息逻辑相关问题
pubnub-events-and-actions —— 适用于与外部系统的事件驱动集成相关问题
pubnub-illuminate —— 适用于实时分析、决策和仪表盘相关问题
pubnub-security —— 适用于Access Manager、加密、TLS相关问题
pubnub-scale —— 适用于吞吐量、频道组、大型事件相关问题
pubnub-reliability —— 适用于退避、幂等性、重试、去重相关问题
pubnub-observability —— 适用于日志关联、测试、运行手册相关问题

Output Format

输出格式

When handing off, produce exactly one block in this shape:

text

Intent      : <one sentence restating what the user is trying to do>
Skill       : <specialist-skill-name>
MCP tool    : <user-pubnub MCP tool>
Docs source : <which PubNub docs surface to consult>
Next step   : <one concrete action the user or agent should take next>

Then stop. Let the specialist skill take over.

转交问题时，请严格按照以下格式输出一个区块：

text

意图      : <一句话重述用户的需求>
技能       : <专业技能名称>
MCP tool    : <user-pubnub MCP工具>
文档来源 : <应查阅的PubNub文档渠道>
下一步   : <用户或Agent应采取的一个具体操作>

然后停止操作。由专业技能接管后续处理。

Canonical Owner Files

标准归属文档

Every owned topic mentioned above defers to its canonical reference file. Use these links when handing off:

Access Manager tokens → pubnub-security/references/access-manager.md
History timetoken pagination → pubnub-history/references/pagination-and-ordering.md
Offline catch-up flow → pubnub-history/references/offline-catch-up.md
App Context (users, channel metadata, membership metadata) → pubnub-app-context/references/users.md
Message Actions and reactions → pubnub-chat/references/message-actions.md
Channel groups and wildcard subscribe → pubnub-scale/references/scaling-patterns.md
Incident triage and runbook → pubnub-observability/references/incident-runbook.md

上述提及的所有主题均对应其标准参考文档。转交时请使用以下链接：

Access Manager令牌 → pubnub-security/references/access-manager.md
历史记录时间令牌分页 → pubnub-history/references/pagination-and-ordering.md
离线追更流程 → pubnub-history/references/offline-catch-up.md
App Context（用户、频道元数据、成员元数据） → pubnub-app-context/references/users.md
消息操作和反应 → pubnub-chat/references/message-actions.md
频道组和通配符订阅 → pubnub-scale/references/scaling-patterns.md
事件排查和运行手册 → pubnub-observability/references/incident-runbook.md

pubnub-choose-docs-path

Original

Translation

Choose PubNub Docs Path

选择PubNub文档路径

When to Use This Skill

何时使用本技能

Core Workflow

核心工作流程

Reference Guide

参考指南

Key Implementation Requirements

关键实现要求

Three Forks That Decide Everything

决定所有路由的三个核心分支

Constraints

约束条件

MCP Tools

MCP工具

See Also

另请参阅

Output Format

输出格式

Canonical Owner Files

标准归属文档