一键在 Manus 中运行任何 Skill

开始使用

customer-doctor

星标40

分支23

更新时间2026年7月15日 11:00

Diagnose a broken customer install and produce a redacted support report the customer can send back.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

LongNgn204

LongNgn204/local-coding-agent

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Customer Doctor

Use this when a customer says "it does not work" and you need a fast, safe diagnosis. Prefer generating a local report over pasting long logs into chat.

Rules

Never ask the customer to paste API keys, tunnel IDs, or auth tokens.
The support report is redacted automatically; still review it before sending.
Do not require the proprietary tunnel client to run these checks.

Steps

Version and runtime:
- node -v (must be >= 18)
- node scripts/local-coding-agent.mjs status
Network and ports:
- node scripts/network-doctor.mjs (DNS, TLS, ports 8787/8790, tunnel log)
Generate a support report:
- node scripts/support-report.mjs
- It writes support-report.txt and prints a compact summary + the path.
Read the summary. Common fixes:
- Health not ok: server not started, or wrong workspace path.
- Port 8787/8790 busy: another instance is running; stop it first.
- Tunnel client missing: expected in repo tests; customer must supply it.
Ask the customer to send back support-report.txt (already redacted).

Report Back

Return the single most likely cause, the exact command to fix it, and the path to the redacted support-report.txt.

同仓库更多 Skills

同仓库

release-helper

LongNgn204/local-coding-agent

Prepare a safe Local Coding Agent release build, including version checks, tests, and changelog.

2026-07-1540

repo-support

LongNgn204/local-coding-agent

Help an AI agent understand and work in this repo quickly using the low-round-trip MCP tools and the anti-lag workflow.

2026-07-1540

setup-assistant

LongNgn204/local-coding-agent

Guide a customer through installing, configuring, and verifying Local Coding Agent with safe defaults.

2026-07-1540

code-review

LongNgn204/local-coding-agent

Review the current git diff for bugs, security issues, and clarity, then summarize findings by severity.

2026-07-0140

customer-support

LongNgn204/local-coding-agent

Collect safe Local Coding Agent support context from a customer and produce a concise troubleshooting response.

2026-07-0140

debug-tunnel-network

LongNgn204/local-coding-agent

Diagnose Local Coding Agent tunnel, DNS, TCP, TLS, proxy, organization, and office-network blocking issues.

2026-07-0140

name	customer-doctor
description	Diagnose a broken customer install and produce a redacted support report the customer can send back.

Customer Doctor

Use this when a customer says "it does not work" and you need a fast, safe diagnosis. Prefer generating a local report over pasting long logs into chat.

Rules

Never ask the customer to paste API keys, tunnel IDs, or auth tokens.
The support report is redacted automatically; still review it before sending.
Do not require the proprietary tunnel client to run these checks.

Steps

Version and runtime:
- node -v (must be >= 18)
- node scripts/local-coding-agent.mjs status
Network and ports:
- node scripts/network-doctor.mjs (DNS, TLS, ports 8787/8790, tunnel log)
Generate a support report:
- node scripts/support-report.mjs
- It writes support-report.txt and prints a compact summary + the path.
Read the summary. Common fixes:
- Health not ok: server not started, or wrong workspace path.
- Port 8787/8790 busy: another instance is running; stop it first.
- Tunnel client missing: expected in repo tests; customer must supply it.
Ask the customer to send back support-report.txt (already redacted).

Report Back

Return the single most likely cause, the exact command to fix it, and the path to the redacted support-report.txt.