New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

PiDeck Environment Doctor

by ayuayue in ayuayue/PiDeck

Diagnoses problems in the PiDeck desktop app from a redacted environment report, matching health checks to known failure patterns with fix steps.

MITAuto-check passedDevelopment

SKILL.md written in Chinese; this summary is our English description.

Install PiDeck Environment Doctor

skills CLI
$ npx skills add ayuayue/PiDeck --skill pideck-doctor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ayuayue/PiDeck pideck-doctor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ayuayue/PiDeck.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/skills/pideck-doctor .claude/skills/pideck-doctor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pideck-doctor
GitHub stars
1.1k
Token cost
~566 tokens
SKILL.md length
167 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Diagnoses problems in the PiDeck desktop app from a redacted environment report, matching health checks to known failure patterns with fix steps.

  • Works in 3 steps: 描述问题现象，最好补充复现步骤； → 在「导出分享」里复制报告（Markdown 或 AI 提示词形态）； → 把报告粘贴给 AI（本会话）。
  • Diagnosing why PiDeck cannot connect to pi or start a session
  • SKILL.md covers 这是什么, 第一步：让用户生成诊断报告, 报告包含什么 and 第二步：对照故障模式库定位, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

When PiDeck misbehaves, for example pi will not connect, a session will not start, the app crashes or the model list is empty, the skill sends you through a standard path instead of asking for environment details one by one. You open the feedback entry, generate a diagnosis report, describe the problem and repro steps, copy the report as Markdown or an AI prompt and paste it to the agent. A zip with redacted logs is requested only if the report is not enough.

The report holds environment details such as PiDeck version, install type, OS and Electron, Node and Chrome versions, only on and off values for the proxy and WSL switches, health checks, and the latest redacted warnings and errors. Health checks cover whether pi is installed and its version readable, whether the pi config files parse, error counts over the last 7 days, free disk space, memory use, and proxy and WSL consistency. Home paths are shown as ~ and tokens, keys, emails and phone numbers are redacted.

A failure-pattern library maps each check to actions: reinstall or repoint pi, back up and re-enter a broken config instead of editing it, sort error scopes, free disk space when it falls below 512MB or 2GB, restart on high memory, and fix contradictory proxy or WSL settings. After each fix you regenerate the report to confirm the check turned ok. It never reads raw config files and does not debug pi's own model or tool logic. The SKILL.md is in Chinese.

When your agent uses it

  • Diagnosing why PiDeck cannot connect to pi or start a session
  • Working out why PiDeck crashes, freezes or shows an empty model list
  • Checking a PiDeck install for proxy, WSL or disk space problems

Example prompts

  • “PiDeck won't connect to pi. Here is the diagnosis report I exported.”
  • “Help me find why sessions keep failing to start in PiDeck.”
  • “After the proxy fix, here is a fresh PiDeck report. Did the proxy check turn ok?”

Requirements

  • The PiDeck desktop app with its feedback and environment diagnosis page
  • A diagnosis report exported from PiDeck

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. 描述问题现象，最好补充复现步骤；
  2. 在「导出分享」里复制报告（Markdown 或 AI 提示词形态）；
  3. 把报告粘贴给 AI（本会话）。

What it can do on your machine

Read from SKILL.md and the folder at commit 60fc189. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PiDeck Environment Doctor loads about 566 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 167 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~566

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ayuayue/PiDeck at commit 60fc189, republished under its MIT licence (© ayuayue). 167 words, ~566 tokens.

Download SKILL.mdSave it as .claude/skills/pideck-doctor/SKILL.md (or your agent's skills folder).
name
pideck-doctor
description
排查 PiDeck 桌面应用的问题。当用户说「PiDeck 出问题了」「帮我诊断 PiDeck」「会话起不来」「pi 连不上」「应用报错」等时使用。引导用户在「问题反馈」页生成环境诊断报告并导出，读取诊断报告定位根因，结合故障模式库给出可执行的修复步骤。报告含脱敏后的环境信息、体检项、最近报错日志，不接触任何原始配置文件内容。

PiDeck 环境诊断（pideck-doctor）

这是什么

用户在 PiDeck 里遇到问题（pi 连不上、会话起不来、卡顿、闪退、模型列表为空等）时， 本技能引导用户走一条标准排障路径，用一份脱敏诊断报告替代反复追问环境细节， 快速定位根因。

第一步：让用户生成诊断报告

请用户打开 PiDeck 的**「问题反馈」入口（侧边栏/帮助菜单 → 意见反馈 → 环境诊断 tab）， 点击「生成诊断报告」**，然后：

  1. 描述问题现象，最好补充复现步骤；
  2. 在「导出分享」里复制报告（Markdown 或 AI 提示词形态）；
  3. 把报告粘贴给 AI（本会话）。

用户也支持直接导出 zip（含脱敏日志），但尽量先拿 Markdown 报告，zip 仅在报告不足以 定位时再要求（zip 里是逐行脱敏的日志，同样不含原始配置内容）。

报告包含什么

  • 环境信息：PiDeck 版本、安装形态（安装版/便携版/开发态）、OS 版本、Electron/Node/Chrome 版本、 locale、时区、WSL/代理等开关状态（只给开关布尔值，不给代理地址）；
  • 体检项：pi 是否已装且可读版本、pi 配置（models/auth/settings.json）是否可解析、 最近 7 天 error/warn 条数、数据盘剩余空间、主进程常驻内存、代理配置是否自洽、 WSL 兜底是否自洽；
  • 最近报错日志：脱敏后的最新 warn/error（时间/级别/作用域/消息）。

所有路径都把 home 目录替换成 ~，token/Key/邮箱/手机号一律替换为 [redacted]。

第二步：对照故障模式库定位

pi 未安装 / 版本读不出来
  • 现象：体检项 pi.installed 为 error/warn。
  • 处置：引导用户检查自定义 pi 路径设置（可能指到了非 pi 程序）；安装正式 pi；Windows 上用 WSL 兜底时确认发行版已填。定位到 ~/.pi/agent 目录存在且 models.json 在。
配置损坏（models/auth/settings 解析失败）
  • 现象：体检项 config.parsable 为 error，模型列表为空、会话起不来。
  • 处置：不要直接改配置原文（可能含 apiKey）。先建议备份对应 json 到别处， 再让用户在「配置管理」界面重新填写/重置。若 JSON 明显缺字段导致解析失败， 可重建最小结构，但保留原有 key 值不动。
报错密度高（logs.errors 异常）
  • 现象：logs.errors 为 error/warn，且 recent 里能看到具体错误作用域。
  • 处置：读取 recent 报错，按作用域归类（rpc / agent / terminal / git / web 等）， 定位具体异常类型。若错误消息里出现路径/Key，已由脱敏替换，需结合上下文推断。
磁盘不足
  • 现象：disk.space 为 error（< 512MB）或 warn（< 2GB）。
  • 处置：引导清理数据目录（userData）或系统磁盘；会话/日志写不进去是闪退常见根因。
内存过高
  • 现象：memory.rss 为 error（≥ 3GB）。
  • 处置：多为内存泄漏或超大会话，建议重启应用、关闭大会话后复测。
代理自相矛盾
  • 现象：proxy.consistency 为 warn（开了代理却没填地址）。
  • 处置：在设置里填代理地址或关闭对应代理开关。
WSL 兜底失效
  • 现象：wsl.config 为 warn（开了 WSL 却没填发行版）。
  • 处置：在设置里填发行版名，或关闭 WSL 兜底用原生 pi。

第三步：给出修复并复测

  • 每给一条修复建议，都让用户重新生成一次诊断报告，对比相关体检项是否从 error/warn 变为 ok——用数据验证修复是否生效，而不是猜。
  • 若修复后仍异常，导出 zip 日志包，@群内支持者继续排查。

边界与隐私

  • 只读诊断报告，不读原始配置：报告已脱敏，绝不要求用户把 auth.json/models.json 原文贴出来。
  • 不代替 pi 做 Agent 行为：本技能只管 PiDeck 应用自身的安装/配置/环境问题，不处理 pi 内部的模型调用/工具逻辑（那些属于 pi 自身的排障）。
  • 报告里的路径是 ~ 缩写：需要真实路径定位时，请用户在应用内通过「设置 → 打开数据目录」 查看，而不是要求贴完整路径。

© ayuayue, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/skills/pideck-doctor of ayuayue/PiDeck.

Open the folder on GitHubat commit 60fc189

Compare with similar skills

PiDeck Environment Doctor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PiDeck Environment Doctor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PiDeck Environment Doctor this skillayuayue/PiDeck1.1k—~566Automated safety check: PassMIT
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Graph-Based Bug Tracingtirth8205/code-review-graph32k1 repos~287Automated safety check: PassMIT
Systematic DebuggingChrisWiles/claude-code-showcase6.1k3 repos~1.2kAutomated safety check: PassNone

Similar skills

  • OpenLogi macOS Permissions Triage

    AprilNEA/OpenLogi

    Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes

  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed

  • Systematic Debugging

    ChrisWiles/claude-code-showcase

    Applies a four-phase debugging routine that finds the root cause of a bug or failing test before any fix is written.

    6.1k GitHub starsUsed in 3 repos~1.2k tokens
    DevelopmentAuto-check passed

  • Debugging and Error Recovery

    addyosmani/agent-skills

    Applies a stop-the-line rule and a step-by-step triage when tests fail, builds break or something stops working, aiming at the root cause instead of guesses.

    105k GitHub starsUsed in 1 repo~2.6k tokens
    DevelopmentAuto-check passed

More from ayuayue/PiDeck

  • PiDeck Image Generation Connector

    ayuayue/PiDeck

    Calls an OpenAI-compatible image generation API using PiDeck's separate image-provider config, then saves the result as a local file.

    1.1k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • MCP Setup

    ayuayue/PiDeck

    帮用户接入/配置 MCP（Model Context Protocol）服务。当用户说「帮我接 MCP」「连上某个服务的 MCP」「配置 Model Context Protocol」「加个工具服务器」「为什么 MCP 连不上」等时使用。按服务官方文档把配置写进 pi 的 mcp.json，并用 pi mcp list 验证连接，全程不破坏用户已有配置。

    1.1k GitHub stars~650 tokensUpdated today
    Auto-check passed

  • PiDeck Usage Probe Helper

    ayuayue/PiDeck

    Helps show a model provider's usage, balance or quota in PiDeck: checks built-in support, points to the dialog templates, or writes a custom probe entry.

    1.1k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Categories

Questions about PiDeck Environment Doctor

What does PiDeck Environment Doctor do?

Diagnoses problems in the PiDeck desktop app from a redacted environment report, matching health checks to known failure patterns with fix steps. When PiDeck misbehaves, for example pi will not connect, a session will not start, the app crashes or the model list is empty, the skill sends you through a standard path instead of asking for environment details one by one. You open the feedback entry, generate a diagnosis report, describe the problem and repro steps, copy the report as Markdown or an AI prompt and paste it to the agent.

When should I use PiDeck Environment Doctor?

PiDeck Environment Doctor fits situations like: diagnosing why PiDeck cannot connect to pi or start a session; working out why PiDeck crashes, freezes or shows an empty model list; checking a PiDeck install for proxy, WSL or disk space problems.

How do I install PiDeck Environment Doctor in Claude Code?

Run `npx skills add ayuayue/PiDeck --skill pideck-doctor -a claude-code`. Or copy the skill folder (resources/skills/pideck-doctor in ayuayue/PiDeck) into .claude/skills/pideck-doctor in your project. Claude Code loads it when a task matches its description.

How do I install PiDeck Environment Doctor in Codex?

Run `npx skills add ayuayue/PiDeck --skill pideck-doctor -a codex`. Or copy the skill folder (resources/skills/pideck-doctor in ayuayue/PiDeck) into .agents/skills/pideck-doctor in your project. Codex loads it when a task matches its description.

Can I use PiDeck Environment Doctor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ayuayue/PiDeck --skill pideck-doctor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pideck-doctor, .gemini/skills/pideck-doctor, .github/skills/pideck-doctor and .opencode/skills/pideck-doctor in your project.

What does PiDeck Environment Doctor need to run?

SKILL.md names no scripts, command-line tools or credentials: PiDeck Environment Doctor is instructions for the agent only. Our summary lists: The PiDeck desktop app with its feedback and environment diagnosis page; A diagnosis report exported from PiDeck.

Does PiDeck Environment Doctor access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is PiDeck Environment Doctor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PiDeck Environment Doctor use?

PiDeck Environment Doctor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PiDeck Environment Doctor use?

About 566 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PiDeck Environment Doctor?

Skills that share tags, products or a category with PiDeck Environment Doctor: OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Graph-Based Bug Tracing (tirth8205/code-review-graph, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PiDeck Environment Doctor?

ayuayue (a GitHub user) maintains it in ayuayue/PiDeck, which has 1,050 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 11, 2026.

Source: ayuayue/PiDeck on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.