exploring-web-app

Crawls internal links of a website to build a structured site map with per-page health and feature tags.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/celikgo/webmobai --skill exploring-web-app-celikgo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: exploring-web-app
Source: https://github.com/celikgo/webmobai/tree/main/.claude/skills/exploring-web-app
Command: npx skills add https://github.com/celikgo/webmobai --skill exploring-web-app-celikgo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you inherit an unfamiliar website or start a QA engagement, you don't know what pages exist, what features they contain, or what's already broken. This Skill automates that reconnaissance by crawling the site and producing a structured map plus an HTML report. ## Core Features & Use Cases - Autonomous site crawling: Starts from a URL, follows same-origin internal links up to a configurable depth and page cap, and deduplicates on post-redirect URLs. - Per-page health and feature tagging: Records console errors, broken images, headings, forms, login walls, videos, and modals for every page, then groups results by depth, section, feature, and health. - Safe authenticated crawling: Supports storage_state_path sessions and enforces a hard skip list for destructive URLs like logout, delete, and checkout links. - Use Case: You just inherited a staging site. Ask the AI to explore it, and receive a site map showing 12 pages, which ones have forms, which have console errors, and recommended follow-up audits. ## Quick Start Ask the AI to explore https://example.com and map out all its pages, features, and broken elements.

Frequently Asked Questions about exploring-web-app

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

FAQPage Schema
How do I crawl a website to find all its pages?▼

Provide a starting URL and the crawler follows same-origin internal links up to a configurable depth (default 2) and page cap (default 15). It deduplicates on post-redirect URLs, strips tracking query params, and skips file downloads, anchors, and destructive links.

How to crawl a website that sits behind a login?▼

Capture an authenticated session once as a storageState file, then launch the browser with storage_state_path so every crawled page is already authenticated. Deduplicate on post-redirect URLs so an expired session shows up as repeated /login records instead of fake pages.

Can a web crawler accidentally delete data or log me out?▼

Yes, which is why this crawl enforces a hard skip list covering logout, delete, reset, checkout, and admin action URLs. Skipped destructive links are recorded in the map as skipped rather than navigated, which matters most during authenticated crawls.

Does the crawler respect robots.txt or handle rate limiting?▼

No, the tool does not respect robots.txt, so you must have authorization to crawl the target site. If the site returns 429 responses, lower the page cap rather than adding explicit sleeps, since the network-idle wait usually paces requests.

Why does my site map show the same login page many times?▼

This happens when the session expires mid-crawl or pages redirect to /login. Every remaining URL records as the same login page with zero errors, so check final post-redirect URLs before concluding the site is healthy.

What are the limitations of crawling single-page applications?▼

SPAs that change URLs via the History API may only expose currently-rendered links, so routes revealed only after user interaction can be missed. Infinite-scroll feeds are crawled only in their initial state, not exhaustively.