analyze-website
Analyze Website
Investigate and document site structure and functionality for humans and agents.
This skill produces reusable analysis artifacts that support test planning, coverage decisions, and change impact reviews.
Performance Goals
- Minimize repeated deep scans when analysis already exists.
- Use the lightest evidence path first (HTML/routes/labels), then deepen only as needed.
- Reuse cached analysis for unchanged targets.
When to Use
- You need a structured map of a website before writing or triaging tests.
- You need component inventory and functionality importance levels.
- You need to compare two site versions (or two snapshots) for differences.
When Not to Use
More from klamping/webdriverio-skills
writing-webdriverio-code
Use when implementing, extending, or fixing WebdriverIO tests, including converting pseudo-code scaffolds into clean WDIO commands, selectors, waits, and assertions.
21running-webdriverio-tests
Run WebdriverIO test files from the command line. Use when debugging tests, gathering context about test behavior, or verifying changes resolved an issue.
13creating-test-structure
Use when creating or extending WebdriverIO test structure from a markdown test plan by adding describe/it/hooks and pseudo-code comments without implementing WDIO commands yet.
10gathering-context
Use when investigating a failing WebdriverIO test and you need to understand what the test was doing and where it broke.
10skipped-test-manager
Use when temporarily skipping failing WebdriverIO tests for app bugs or unimplemented functionality, while tracking ownership, ticket linkage, and re-enable status.
9managing-project-customizations
Use when initializing or refreshing project-specific WebdriverIO context so other skills can reuse cached configuration, conventions, and environment details with lower token and execution cost.
9