web-investigation

Inspect website HTML and debug web scraping with Chrome DevTools.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rosssaunders/coincise --skill web-investigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-investigation
Source: https://github.com/rosssaunders/coincise/tree/main/.claude/skills/web-investigation
Command: npx skills add https://github.com/rosssaunders/coincise --skill web-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand how a website is built, debug extraction issues, and identify documentation frameworks (like Redocly or Swagger UI) using Chrome DevTools, reducing guesswork and speeding up QA.

Core Features & Use Cases

  • HTML structure exploration: Inspect DOM and network activity to map content.
  • Debug extraction issues: Identify why selectors fail or data isn't captured.
  • Framework identification: Determine if a site uses Redocly, Swagger UI, or custom docs, to tailor scraping strategies.
  • Authentication pattern checks: Spot auth requirements and patterns in endpoints.

Quick Start

Start by opening the target site in Chrome DevTools and run a guided investigation to map structure and endpoints, e.g., navigate to the documentation site and run a DOM inspection task.

Frequently Asked Questions about web-investigation

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

FAQPage Schema
How do I debug web scraping issues with Chrome DevTools?

Debugging web scraping with Chrome DevTools involves inspecting DOM elements to validate selectors, monitoring network activity to detect API calls, and evaluating scripts to understand dynamic content loading. Use element inspection to confirm selectors target the correct data, check the Network tab for endpoint patterns, and run console scripts to test extraction logic before deploying scrapers.

Can I identify whether a site uses Redocly or Swagger UI?

Framework identification using Chrome DevTools examines HTML structure, CSS class names, and network requests to detect documentation frameworks. Redocly and Swagger UI have distinct DOM markers and bundle signatures visible in the Sources and Elements tabs, allowing you to tailor scraping strategies and understand authentication patterns specific to each framework.

What's the best way to inspect HTML structure and validate selectors?

Inspect HTML structure by opening Chrome DevTools, navigating the Elements panel to map DOM hierarchy, and testing CSS or XPath selectors in the Console to confirm they target intended elements. Validate selector reliability by running extraction queries against live pages and comparing captured data against expected output to catch failures before deployment.

How do I check authentication patterns when analyzing a documentation site?

Checking authentication patterns involves using Chrome DevTools to inspect network requests for auth tokens, headers, and cookie requirements, and examining the HTML source for login forms or OAuth markers. Monitor API endpoints in the Network tab to identify authentication flows and validate whether selectors work before and after authentication.

Why does my web scraper fail to extract data from dynamic content?

Scraper failures on dynamic content typically occur when JavaScript modifies the DOM after page load. Use Chrome DevTools to monitor the Network tab for AJAX requests, inspect Elements after JavaScript execution, and evaluate Console scripts to understand timing and data injection. Identify whether content is server-rendered or client-rendered to adjust extraction logic accordingly.