External System Debugging

by doccker

External System Debugging is a Quality skill for Claude Code, published by doccker in cc-use-exp.

1K stars105 forkson doccker/cc-use-expAdded 2026/08/21Repository updated 2026/06/30

View source on GitHub Download repo ZIP

antigravityclaude-codecodexcursorgemini-cligithub-copilot

Install in seconds

Install External System Debugging

Copy External System Debugging into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/doccker/cc-use-exp/tree/main/.antigravity/skills/external-system-debugging ~/.claude/skills/external-system-debugging

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/doccker/cc-use-exp.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .antigravity/skills/external-system-debugging/SKILL.md in doccker/cc-use-exp
Installs to: ~/.claude/skills/external-system-debugging
Collection: One of 23 skills cataloged from this repository
Category: Quality — 1354 skills

What External System Debugging does

External System Debugging helps debug code that depends on browsers, editors, CDNs/WAFs, IM platforms, clipboards, or third-party SaaS. It requires collecting real environment data first, then using that evidence to diagnose paste, rendering, API, and cross-platform issues.

External System Debugging is cataloged under Quality on DirSkills. External System Debugging comes from a repository tagged antigravity, claude-code, codex, cursor and gemini-cli.

Documentation

README

Excerpt

外部黑盒系统调试方法论

"代码没说谎,但黑盒系统的行为不在代码里。"

涉及代码以外的环境(浏览器、编辑器、CDN、IM 平台、第三方 API),编码和调试都必须先抓真实数据,再做推理。

何时触发

写代码场景

输出会被第三方平台消费的内容(HTML 推送到 CSDN/微信/Notion/钉钉/飞书)
集成浏览器/操作系统 API(Clipboard / Drag-Drop / File System)
调用经过 CDN/WAF/反代的第三方 HTTP API
在 IM / 富文本编辑器中渲染内容

调试场景

跨浏览器/跨设备/跨终端表现不一致
粘贴/复制行为异常
第三方 API 返回怪结果(body 空、headers 不全、200 但 error)
本地复现失败但线上有问题
连续 2 轮"凭代码推理"的修复都 no-op(最强信号)

黑盒判定清单

维度	不是黑盒	是黑盒(触发本 skill)
控制权	自己写的代码	第三方/平台/浏览器实现
文档完备性	有完整 API 文档	文档不全或有未文档化行为
可调试性	能加日志、断点	只能从外部观察输入输出
行为可预测	给定输入必然得到给定输出	同一输入在不同环境表现不同

满足任意 2 项 → 走本 skill 方法论。

数据采集模板(核心)

不同黑盒类型,第一步该让用户抓什么:

This is the opening of the README. Read the full README on GitHub.

Frequently asked about External System Debugging

What else does doccker publish alongside External System Debugging?
External System Debugging is one of 23 skills that DirSkills catalogs from doccker/cc-use-exp, the repository it ships in. Its siblings there include API Design Safety, Api Design Safety and Api Proxy Safety. Each one is a separate skill with its own page in this directory, installs the same way External System Debugging does, and is maintained by doccker in that same repository. The rest of the collection is listed on the doccker/cc-use-exp page.
How does External System Debugging compare to other Quality skills?
External System Debugging ranks #835 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of External System Debugging against them. Open each page to compare what they document and how they install.