Back to Details

proxyman-debugging-tools

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Proxyman Debugging Tools And Documentation

Proxyman 调试工具与文档

Use official Proxyman documentation to teach or plan a debugging workflow. This skill is documentation-first: it does not assume that a similarly named MCP or CLI action exists.
Use 
proxyman-traffic-debugging
when the main task is to operate MCP now. Use 
proxyman-app-settings
for a Settings-tab audit or preference change, 
proxyman-certificates-recovery
for local root/custom certificate lifecycle or Help-menu Debug Mode/Factory Reset, 
proxyman-https-capture
for device/runtime capture configuration, 
proxyman-cli
for shell automation, and 
proxyman-license-management
for licensing.
使用官方 Proxyman 文档来讲解或规划调试工作流。本 Skill 以文档优先：不会假定存在功能相似的 MCP 或 CLI 操作。
当主要任务是立即执行 MCP 操作时，使用 
proxyman-traffic-debugging
。使用 
proxyman-app-settings
审核 Settings 标签页或更改偏好设置，使用 
proxyman-certificates-recovery
管理本地根证书或自定义证书的生命周期，以及使用 Help 菜单中的 Debug Mode/Factory Reset。使用 
proxyman-https-capture
配置设备或运行时的抓包，使用 
proxyman-cli
进行 shell 自动化，使用 
proxyman-license-management
管理许可证。

Get The Current Documentation

获取当前文档

For every task where current behavior matters:
  1. Fetch 
    https://docs.proxyman.com/llms.txt
    .
  2. Match the user's feature or symptom to one or more official 
    .md
    entries.
  3. Fetch the selected 
    .md
    page directly. Do not reconstruct a page path from memory when the index provides it.
  4. Cite the public HTML URL by removing only the final 
    .md
    from the fetched URL.
  5. If the page links a prerequisite or troubleshooting page that materially changes the steps, fetch that page too.
Use official Proxyman-owned domains 
docs.proxyman.com
, 
docs.proxyman.io
, 
proxyman.com
, 
proxyman.io
, and the live Proxyman MCP server as authorities. A freshly fetched official page may link to an external destination, but treat that destination as authoritative only for its own product or service unless the user asks for third-party guidance.
If internet access is unavailable, say that the latest page could not be verified. You may use the bundled debugging tool index as a navigation fallback, but label it as a snapshot.
对于每项需要确认当前行为的任务：
  1. 获取 
    https://docs.proxyman.com/llms.txt
    。
  2. 将用户的功能或问题匹配到一个或多个官方 
    .md
    条目。
  3. 直接获取选定的 
    .md
    页面。当索引提供页面路径时，不要凭记忆重建路径。
  4. 通过仅移除所获取 URL 末尾的 
    .md
    ，引用公开的 HTML URL。
  5. 如果页面链接的前置条件或故障排查页面会实质性地改变操作步骤，也应获取该页面。
将官方 Proxyman 所属域名 
docs.proxyman.com
、
docs.proxyman.io
、
proxyman.com
、
proxyman.io
以及当前在线的 Proxyman MCP server 视为权威来源。新获取的官方页面可能会链接到外部目标，但除非用户要求第三方指南，否则该目标仅对其自身产品或服务具有权威性。
如果无法访问互联网，请说明无法验证最新页面。可以使用随附的 调试工具索引 作为导航后备方案，但必须将其标注为快照。

Understand Built-In MCP Documentation

了解内置 MCP 文档

search_docs
, 
answer_setup_question
, 
docs://search/{query}
, and the static MCP resources search Proxyman's bundled setup and troubleshooting knowledge base. They are version-matched and ideal for capture diagnosis, but they do not represent the full 
docs.proxyman.com
catalog.
For a product-wide feature question, fetch the public index even if 
search_docs
returns a result. For exact MCP inputs, trust 
tools/list
, not the public MCP page or this skill.
search_docs
、
answer_setup_question
、
docs://search/{query}
以及静态 MCP resources 会搜索 Proxyman 内置的 设置与故障排查知识库。这些内容与版本匹配，非常适合用于诊断抓包问题，但并不代表完整的 
docs.proxyman.com
文档目录。
对于覆盖整个产品的功能问题，即使 
search_docs
返回了结果，也要获取公开索引。对于确切的 MCP 输入，应以 
tools/list
为准，而不是公开 MCP 页面或本 Skill。

Build The Answer Or Guide

构建答案或指南

  1. Identify the user's goal, target traffic, platform, and whether they want explanation, GUI steps, MCP execution, or CLI automation.
  2. Read the current official page and extract prerequisites, supported platforms, limits, and verification behavior.
  3. Inspect debugging tool index to map the feature to interfaces.
    • For Breakpoint, Map Local, Map Remote, Scripting, or interaction among those rules, read request and response modification.
    • For Compose or Repeat, Network Conditions, or Reverse Proxy, read replay and routing workflows.
    • For Protobuf or TLS Key Logging, read protocol decoding and key logging.
  4. Present only supported routes:
    • GUI: menu/screen and ordered user steps from the current page.
    • MCP: current tool names, discovery requirement, state read, mutation, and verification.
    • CLI: route to 
      proxyman-cli
      ; discover installed help before giving exact flags.
  5. Include a concrete verification: expected flow, rule inventory, status field, response change, or exported artifact.
  6. Include rollback for persistent rules, proxy changes, certificate trust, or capture automation.
If the docs describe a GUI-only feature, say so. Do not invent MCP/CLI parity.
  1. 确定用户的目标、目标流量、平台，以及用户希望获得说明、GUI 步骤、MCP 执行还是 CLI 自动化。
  2. 阅读当前官方页面，并提取前置条件、受支持的平台、限制和验证行为。
  3. 查看 调试工具索引，将功能映射到相应接口。
    • 对于 Breakpoint、Map Local、Map Remote、Scripting 或这些规则之间的交互，请阅读 请求与响应修改。
    • 对于 Compose 或 Repeat、Network Conditions 或 Reverse Proxy，请阅读 重放与路由工作流。
    • 对于 Protobuf 或 TLS Key Logging，请阅读 协议解码与密钥日志。
  4. 仅介绍受支持的执行路径：
    • GUI： 根据当前页面提供菜单或界面以及有序的用户操作步骤。
    • MCP： 提供当前工具名称、发现要求、状态读取、状态变更和验证方式。
    • CLI： 引导至 
      proxyman-cli
      ；先查看已安装 CLI 的帮助信息，再给出准确的 flags。
  5. 包含具体的验证方式：预期流程、规则清单、状态字段、响应变化或导出的产物。
  6. 对于持久化规则、代理变更、证书信任或抓包自动化，包含回滚方式。
如果文档说明某项功能仅支持 GUI，请明确指出。不得虚构 MCP 或 CLI 的同等能力。

Guide Shape

指南结构

Use this compact structure:
text
Goal
Prerequisites
GUI steps
MCP steps (if exposed)
CLI steps (if exposed)
How to verify
How to undo
Limits / platform notes
Official docs
Skip empty interface sections rather than padding the answer.
使用以下紧凑结构：
text
Goal
Prerequisites
GUI steps
MCP steps (if exposed)
CLI steps (if exposed)
How to verify
How to undo
Limits / platform notes
Official docs
如果某个接口部分没有相关内容，应跳过该部分，不要用填充内容扩展答案。

Safety

安全要求

  • Start with read-only discovery and traffic inspection.
  • Obtain confirmation before changing proxy routing, trust stores, global tool state, external proxy credentials, or other applications.
  • Obtain confirmation immediately before deletes, session clearing, certificate uninstall, destructive imports, or irreversible portal actions.
  • Keep MCP redaction enabled. Warn that exported original traffic is not sanitized by MCP preview redaction.
  • Never paste license keys, TLS session-key logs, tokens, passwords, cookies, or captured secrets into a guide or tool input unless the user explicitly requires it and understands the exposure.
  • Do not claim a page is current unless it was fetched during this task.
  • 首先进行只读发现和流量检查。
  • 在更改代理路由、信任存储、全局工具状态、外部代理凭据或其他应用之前，应获得确认。
  • 在删除、清除会话、卸载证书、执行破坏性导入或不可逆的 portal 操作之前，必须立即获得确认。
  • 保持 MCP redaction 启用。警告用户：导出的原始流量不会经过 MCP preview redaction 脱敏。
  • 除非用户明确要求并理解由此造成的敏感信息暴露，否则绝不要将许可证密钥、TLS 会话密钥日志、令牌、密码、Cookie 或捕获到的敏感信息粘贴到指南或工具输入中。
  • 除非页面是在当前任务中获取的，否则不要声称其为最新版本。

Coverage

覆盖范围

The reference maps capture/view/filter tools, Repeat/Compose, Breakpoint, Map Local/Remote, Block/Allow List, Scripting, No Caching, External/Reverse/SOCKS proxy, SSL Proxying, certificates, WebSocket, Protobuf/GraphQL, Network Conditions, DNS Spoofing, exports, code generation, diff, OpenAPI, TLS Key Logging, and adjacent GUI tools.
When a current index adds a new debugging page, use it even if it is absent from the snapshot, then state which interfaces the live product exposes.
该参考文档涵盖了抓取、查看和过滤工具，Repeat/Compose、Breakpoint、Map Local/Remote、Block/Allow List、Scripting、No Caching、External/Reverse/SOCKS proxy、SSL Proxying、证书、WebSocket、Protobuf/GraphQL、Network Conditions、DNS Spoofing、导出、代码生成、diff、OpenAPI、TLS Key Logging 以及相关 GUI 工具。
当当前索引新增调试页面时，即使该页面未出现在快照中，也应使用它，然后说明当前产品开放了哪些接口。