web-debug-search

Searches GitHub, Stack Exchange, and developer communities for error reports and workarounds.

15.6k|1.4k|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep --skill web-debug-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-debug-search
Source: https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep/tree/main/skills/web-debug-search
Command: npx skills add https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep --skill web-debug-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you hit a cryptic error, version conflict, or API usage question, manually hunting through GitHub Issues, Stack Overflow, and community forums is slow and unstructured. This Skill runs a disciplined, budgeted web search across those sources and returns classified, deduplicated findings you can act on.

Core Features & Use Cases

  • Multi-source routing: Searches GitHub Issues/Discussions, Stack Exchange, Chinese technical communities (SegmentFault, V2EX, Zhihu, CSDN, Juejin), and general web sources including official documentation, with automatic or explicit source selection.
  • Four-axis evidence classification: Labels every result by match quality (exact/normalized/contextual), finding type (error/compatibility/API-usage/workaround), evidence use, and authority (official/maintainer/community/blog).
  • Bounded, safe searching: Enforces query budgets, deduplicates reposts and shared citations, treats all fetched content as untrusted, and never executes commands found online.
  • Use Case: You encounter "CUDA error: invalid device ordinal" after upgrading a library. The Skill searches the repository's issues and Stack Overflow, finds a maintainer-confirmed regression and a community workaround, and reports both with version details and an explicit evidence boundary.

Quick Start

Ask the agent to run web-debug-search with your exact error message, package name, and versions, optionally restricting sources such as github and stackexchange.

Frequently Asked Questions about web-debug-search

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

FAQPage Schema
How do I search GitHub issues for an exact error message?

Provide the exact error string and the repository in owner/name form. The Skill searches repository-scoped Issues and Discussions first with the quoted error, then broadens to normalized and global queries within a fixed budget.

What sources does web-debug-search cover for debugging?

It covers four source profiles: GitHub Issues and Discussions, Stack Exchange sites, Chinese technical communities like SegmentFault, V2EX, Zhihu, CSDN, and Juejin, plus general web sources such as official documentation, Hacker News, Reddit, and blogs.

Can I restrict the search to specific sources or languages?

Yes. Pass a comma-separated sources list such as github,stackexchange and a language option of en, zh, or both. Explicit values override automatic routing, and unsupported values fall back to auto with a notice.

Does web-debug-search execute workarounds it finds online?

No. It never runs commands, installs packages, or edits files based on search results. Workarounds are summarized as unverified candidates and become confirmed only after explicit user-side reproduction.

Can I use web-debug-search results as citations in a research paper?

No. All results are labeled for debugging and discovery only and must not be added to a bibliography or used as standalone support for a research claim. Use a dedicated literature and citation-verification workflow instead.

What happens when web search is unavailable or a page cannot be fetched?

If WebSearch is unavailable the Skill stops with a BLOCKED status rather than fabricating results. If WebFetch cannot read a candidate, it labels the result as an unverified search snippet and uses it only as a lead.