external-system-debugging

Diagnose bugs in external black-box systems by capturing real environment data before reasoning.

1.0k|109|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/doccker/cc-use-exp --skill external-system-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-system-debugging
Source: https://github.com/doccker/cc-use-exp/tree/main/.cursor/skills/external-system-debugging
Command: npx skills add https://github.com/doccker/cc-use-exp --skill external-system-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debugging issues involving browsers, editors, CDN/WAF layers, IM platforms, OS clipboards, or third-party SaaS often fails because the behavior lives outside your code. This Skill stops the cycle of repeated code-reasoning fixes that do nothing by forcing real environment data capture first.

Core Features & Use Cases

  • Black-box identification checklist: Determines whether a system qualifies as a black box based on control, documentation, debuggability, and predictability criteria.
  • Data collection templates: Provides per-system capture recipes, such as reading all clipboard MIME types via navigator.clipboard.read(), diffing outerHTML before and after paste, and using curl -v to inspect CDN/WAF headers.
  • Case library with naming conventions: Ships real cases (CSDN paste list bug, HTTP CDN/WAF interception) plus templates for documenting new findings in references/.
  • Use Case: When a copied article renders as four separate "1." list items in CSDN but works in WeChat, use this Skill to capture the actual DOM structure, identify the undocumented HTML-to-Markdown start-attribute loss, and apply a verified single-variable fix.

Quick Start

Ask the AI to debug a paste or third-party API issue using the external-system-debugging skill and have it capture real environment data before proposing any fix.

Frequently Asked Questions about external-system-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug clipboard paste issues across browsers?

Capture the actual clipboard contents first using navigator.clipboard.read() to list all MIME types and print each payload, or log e.clipboardData.getData(type) inside a paste event handler. Compare the raw HTML between source and target editors before changing any code.

How to tell if a CDN or WAF is blocking my API request?

Check for an empty response body combined with minimal headers, which is a strong interception fingerprint. Inspect Server, Via, and cf-ray headers with curl -v, and compare GET versus POST behavior on the same endpoint to isolate client compatibility issues.

Why does my HTML list render differently in CSDN versus WeChat?

CSDN's editor converts pasted HTML to Markdown and drops the ol start attribute, so multiple lists relying on start for continuous numbering all reset to 1. Merge adjacent lists into a single ol before writing to the clipboard to avoid the conversion loss.

When should I stop reasoning from code and capture real data?

Stop after two consecutive code-reasoning fixes produce no observable change. At that point the third attempt must collect real environment data, such as DOM structure, network traces, or clipboard payloads, before forming any new hypothesis.

What counts as a black-box system in debugging?

A system qualifies as a black box when at least two of these hold: you do not control its implementation, documentation is incomplete or behavior is undocumented, you can only observe inputs and outputs, or the same input behaves differently across environments.