skills.rest
doccker
docckerCOMMUNITY
Explore all skills by this author →
GitHub

cc-external-system-debugging

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

1.0k|109|Updated Jan 4, 2026
Search Tags:#Debugging#Root Cause Analysis#browser compatibility#third-party API#clipboard api#black-box systems#cdn waf
One-click install
npx skills add https://github.com/doccker/cc-use-exp --skill cc-external-system-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-external-system-debugging
Source: https://github.com/doccker/cc-use-exp/tree/main/.codex/skills/cc-external-system-debugging
Command: npx skills add https://github.com/doccker/cc-use-exp --skill cc-external-system-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debugging issues that involve 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 produce no-ops by forcing real environment data capture first.

Core Features & Use Cases

  • Black-box identification checklist: Classifies whether a system is a black box based on control, documentation, debuggability, and predictability criteria.
  • Data collection templates: Provides per-system capture recipes, such as reading 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, CDN/WAF empty-body interception, proxy keyword misjudgment) plus templates for documenting new findings.
  • Use Case: When a copied article renders as four "1." list items in CSDN but works in WeChat, use this Skill to capture the actual pasted HTML, discover the HTML-to-Markdown conversion drops the start attribute, and fix by merging adjacent lists before writing to the clipboard.

Quick Start

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

Frequently Asked Questions about cc-external-system-debugging

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

FAQPage Schema
How do I debug copy-paste issues across browsers and editors?▼

Capture the actual clipboard contents first using navigator.clipboard.read() to list all MIME types and print the HTML via outerHTML. Compare the DOM before and after pasting in the target editor to find undocumented conversion behavior, such as dropped start attributes on ordered lists.

Why does a third-party API return an empty body with a 4xx or 5xx status?▼

An empty response body with minimal headers is a strong fingerprint of CDN or WAF interception rather than a business error. Check Server, Via, and cf-ray headers with curl -v, and compare GET versus POST behavior to isolate HTTP client compatibility issues.

What should I do when two rounds of code-based fixes produce no effect?▼

Stop reasoning from code and capture real environment data instead. Two consecutive no-op fixes are the strongest signal that the behavior lives in a black-box system, so request actual clipboard data, DOM snapshots, or full request and response captures before attempting a third fix.

How do I tell whether a system counts as a black box for debugging?▼

Evaluate four dimensions: whether you control the code, whether documentation is complete, whether you can add logs or breakpoints, and whether identical inputs produce identical outputs across environments. Meeting any two criteria means the system should be treated as a black box.

Can keyword matching on response bodies detect upstream proxy errors reliably?▼

Pure substring matching on terms like Cloudflare or 502 Bad Gateway misjudges legitimate long-form content containing those technical terms. Combine HTTP status, headers, Content-Type, and business JSON structure first, and treat keywords only as weak heuristic evidence.

Related Skills

Explore More Software Engineering Skills→
nth5693nth5693
370

debug

Reproduce issues and trace root causes through structured debugging workflows.

Community
Intermediate
ArthTech-AIArthTech-AI

qa-incident

Log QA incidents with issue details, affected files, root cause, and fix.

Official
Basic
NlightNFotisNlightNFotis
2

reverse-engineering

Probe opaque systems to build confidence-rated behavioral models.

Community
Advanced
logo-solutionslogo-solutions

debugging-and-error-recovery

Guide systematic root-cause debugging of failing tests and build errors.

Official
Advanced